On Fri, 24 Nov 2006, Frank Steiner wrote:
Frank Steiner wrote
Any change to activate a driverupdate before mounting the install source? I guess if I have to get all that into the initrd, it becomes complicated (all libraries needed for lvm tools etc., hacking the init script... :-()
I tried to put the driverupdate on a floppy and use driverupdate=1 on the boot prompt. My driverupdate file contains a file /linux/suse/i386-sles10/install/update.tar.gz which is just a tar.gz of all files and directories in the lvm2.rpm, plus a update.pre script, calling vgscan and vgchange.
The driverupdate is indeed loaded from the floppy, but it doesn't unpack the update.tar.gz (I don't see any of the files when using the prompt at ALT+F9), nor does it execute the pre script.
update.tar.gz is unpacked only when the installation is about to start, which is too late for you.
But you can slightly abuse the update process and do this:
- add an UpdatePriority to dud.config, say:
- this ensures the local copy of the update files is created below
- add a script, say 'install/foo' to your update
- add an entry
This will run your 'foo'-script the moment the update is read (and not later, when the installation is started). You can then use this script to create the environment you need, like copying lvm files and doing the lvm setup.
BTW, if you can live with putting the driver update on CD, you can replace/add files to the initrd directly.