On Thursday 22 December 2005 20:36, aquajtk-suse@yahoo.com wrote:
How can i use several update disks if they all should be named 'driverupdate'?
AFAIK only one driverupdate is possible. You can use the little scripts on http://www.suse.de/~ug to pack and unpack the driverupdate. So, unpack the existing driverupdates and copy them into one directory tree. Then pack that directory tree again into a new driverupdate (look into the scripts. Only very few commands are needed for that. The scripts are more an example than a tool).
2. Say I have an http repository which contains the installation sources for SLES9 SP2. One day Novell releases a critical security patch and I'd like to integrate this patch in my repository so i don't need to install these patches after installing a server. Is there a way to do this (besides doing this with post-install scripts that just run rpm-commands)? Replacing the package in the repository won't work i think, cuz (if i'm not wrong) there is a list of packages on the install sources.
take a look at the "create_update_source" script on http://www.suse.de/~ug It creates an update tree besides your official suse tree.
3. Currently i'm using a file in pxelinux.cfg which contains references to the kernel- and initrdimage and also the linuxrc command line parameters. AutoYasts documentation mentiones an info file that contains these parameters. Where do i place such an info file?
the info file must be accessable for linuxrc. That means, the info file must be either in the initrd or on a floppy disk. Pulling the info file over the network is not possible at the moment.
Can i combine the info file and the command line parameters?
yes -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de