My Favorites


Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

Creating an Installation Source to Add Packages During SLE 10 Install

This document (3097654) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Desktop 10


Packages that were not included in the distribution CDs should be added to a network installation source.


The solution in SLE 10 is to create an Add-on installation source to be referenced during installation. To do this, use the following steps:

Adding Additional Packages to Install Source



Before beginning, create an install source with YaST if one doesn't exist.This only needs to be performed if no network install source is available.

In the following example it is assumed that the installation source is available at /export/install/sles10_xx/CD1/

Adding Packages to Network Install Source

1. Create an update install source directory.

Type the following at a terminal prompt. /export/install/sles10_xx/CD1/

2. Copy update or 3rdparty rpm to the appropriate directory.

Type the following at a terminal prompt.

cp updated.rpm /export/install/sles10_xx/CD1/updates/suse/x86

3. Change directories to the new update source directory.

cd /export/install/sles10_xx/CD1/updates/suse

4. Create package description file for updated rpm.

Type the following at a terminal prompt.

create_package_descr -x setup/descr/EXTRA_PROV

5. create directory.yast file in the setup/descr directory.

Type the following in at a terminal prompt.

cd setup/descr

create_directory.yast .                   #(note the '.' at the end of the command)

6. create a add_on_products file in the sles10_64 install source directory.

Type the following in at a terminal prompt.

cd /export/install/sles10_xx/CD1/

Type the following in all on one line.

echo nfs://inst.src.ip.addr/export/install/sles10_xx/CD1/updates>add_on_products

7. Add the following lines to the appropriate AutoYaST control file or templates.

Allow the installation of unsigned installation sources in the
general section of the autoyast xml file:

       <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum>
       <accept_non_trusted_gpg_key config:type="boolean">false</accept_non_trusted_gpg_key>
       <accept_unknown_gpg_key config:type="boolean">false</accept_unknown_gpg_key>
       <accept_unsigned_file config:type="boolean">true</accept_unsigned_file>
       <accept_verification_failed config:type="boolean">false</accept_verification_failed>
       <import_gpg_key config:type="boolean">false</import_gpg_key>

8. Perform AutoYaST install on system using new control file.

If the updated package is a updated package replacing one that is installed based on the packages listed in the autoyast.xml then nothing more needs to be done. Begin install of new system. If you are adding a package that is not an update to an existing package, you will need to add it to the list of packages to be installed. For example if I am installing an updated package called clamav-0.90.1-1.2.i586.rpm I would add the following to the Software section of the autoyast.xml file:


Once this is completed, start a network install, and when you reach the package selection portion of the install, do a search for the custom package to make sure it appears.

Change Log

2010-April-13 - Franz Hassels - Changes:
create_update_source                                  ->         
/export/install/sles10_xx                              ->                   /export/install/sles10_xx/CD1/
/export/install/sles10_xx/CD1/update/         ->                   /export/install/sles10_xx/CD1/updates/
cd setup/sescr                                              ->                   cd setup/descr
ls -A1>directory.yast                                  ->                    create_directory.yast .
Further I added an autoyast snippet.
Further I changed the situation section. Removed the word "customers".
clamav                                                         ->                   <package>clamav</package>


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3097654
  • Creation Date:08-JAN-08
  • Modified Date:27-APR-12
    • SUSESUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center