Adding custom RPMs to an NFS install setup
Hello everyone. I've set up an NFS install for SLES 8 & SuSE 8.1 according to chapter 6 ofAutoYast2 guide: http://www.suse.de/~nashif/autoinstall/8.1/autoyast2.pdf I am unclear how to modify this setup to install custom RPMs that I have created and need installed on workstations. Anyone done this? Thanks.
Hi, For 8.1 you have to put the rpms in the directory matching the architecture, make sure no duplicates are available and run the script create_package_descr as described in the docs. For SLES8 you can do just the above, or you can do it in a much more advanced way using an additional source especially for custom packages, updates and anything else... I created a skeleton with the directory structure which can be downloaded from http://www.suse.de/~nashif/autoinstall/CustomPackages.tgz untar this file into the root of the NFS export and adapt the files yast/instorder yast/order accordingly. The directory structure should look like this: |-- CustomPackages | |-- Custom | | |-- i386 | | |-- i586 | | |-- i686 | | |-- noarch | | `-- setup | | `-- descr | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 |-- UnitedLinux-i386-1 | |-- CD1 | `-- CD2 |-- boot | `-- loader |-- media.1 `-- yast Using the above names, the order files would have the follwing configuration: # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /CustomPackages /CustomPackages /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 / / # cat yast/order /CustomPackages /CustomPackages /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 / / ---------------- Note: delimiter is <tab> ---------------- Now you can add packages as you wish to the CustomPackages repository. Dont forget to run the create_package_descr script when updating or adding new packages. Regards, Anas Marc Christensen wrote:
Hello everyone.
I've set up an NFS install for SLES 8 & SuSE 8.1 according to chapter 6 ofAutoYast2 guide:
http://www.suse.de/~nashif/autoinstall/8.1/autoyast2.pdf
I am unclear how to modify this setup to install custom RPMs that I have created and need installed on workstations.
Anyone done this? Thanks.
Anas, Thanks for the great info.... [snip]
Using the above names, the order files would have the follwing configuration:
# cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /CustomPackages /CustomPackages /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 / /
I have set up these files before according to the pdf that I mentioned before but it did not mention the / entry. Is it nessasery? [snip]
Now you can add packages as you wish to the CustomPackages repository. Dont forget to run the create_package_descr script when updating or adding new packages.
Now, do these new packages get installed automaticaly? Or does the user need to do something to get them installed? If not, is there a way to get them installed without user intervention? And just for my information, does SuSE 8.2 folow the same method for NFS installs as SLES or SuSE 8.1? Thanks much. -- Marc Christensen http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=9502
Marc Christensen wrote:
Anas,
Thanks for the great info....
[snip]
Using the above names, the order files would have the follwing configuration:
# cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /CustomPackages /CustomPackages /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 / /
I have set up these files before according to the pdf that I mentioned before but it did not mention the / entry. Is it nessasery?
No, not really, if it works for you. "/" is needed in cases one copied a source directly into the root of the export.
[snip]
Now you can add packages as you wish to the CustomPackages repository. Dont forget to run the create_package_descr script when updating or adding new packages.
Now, do these new packages get installed automaticaly? Or does the user need to do something to get them installed? If not, is there a way to get them installed without user intervention?
You have to add them in the software resource. Otherwise yast2 will just not install them, just like any other package. An alternative is to add them to a selection, but one should avoid changing the default selections cause those are tested and work fine.
And just for my information, does SuSE 8.2 folow the same method for NFS installs as SLES or SuSE 8.1?
8.2 actually does not follow this method. 8.2 should follow this, although 8.2 is not a multi-source release. Anas
Thanks much.
-- Marc Christensen http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=9502
Hello all, Anas Nashif wrote: [snip]
Now you can add packages as you wish to the CustomPackages repository. Dont forget to run the create_package_descr script when updating or adding new packages.
I've done this with three packages now and they are available in the package selections. Very cool
Now, do these new packages get installed automaticaly? Or does the user need to do something to get them installed? If not, is there a way to get them installed without user intervention?
You have to add them in the software resource. Otherwise yast2 will just not install them, just like any other package. An alternative is to add them to a selection, but one should avoid changing the default selections cause those are tested and work fine.
So, how do I go about this? What I need is for the three RPMs to _always_ get installed no matter what profile the users select - and witout going in to the "Custom" or Individual package selection screens. Is there a way to make sure these RPMs get installed no matter what, on every network installed mashine? Thanks. -- Marc Christensen http://www.mecworks.com
participants (2)
-
Anas Nashif -
Marc Christensen