All, I've been trying to setup a network install (over NFS) for SLES 8 with service pack 3 integrated. I've updated the boot directory with the SP3 files in the root of the install source, and also put the linux directory from SP3 CD1 into an 02/linux directory in the root of the install source. The driverupdates file is there as well. The driver that I need is megaide.o, for an LSI IDE RAID adapter. I've taken the package that LSI provides for SP2a, recompiled the drivers against SP3, repackaged the update.tar.gz file, and then placed it under the 01/linux directory (the BootGRUB.ycp and inst_finish.ycp files were included in the megaide driver update media package, so I thought I should install the SP3 linux directory updates after, so its BootGRUB.ycp and inst_finish.ycp files would overwrite the older ones from the megaide package). The install goes OK, the megaide.o driver is loaded, and the RAID device is seen and installed to, and the SP3 files are installed as well, however, when the system reboots, the megaide module is not on the initrd, so it fails to mount root. I checked the output from mk_initrd during the install, and it reports "Cannot determine dependencies of module megaide\Is modules.dep up to date?". I checked into this further, and it looks like the mk_initrd from SP3 looks at /lib/modules/<kernel-version>/modules.dep, which is not setup by the update.pre script (which is basically just a copy from the example given in the driver update howto), or the update.post script. It is setup in the /etc/modules.dep file though. I modified the update.post script to append the right dependency line in the /lib/modules/<kernel-version>/modules.dep file, and then the install completed OK. However, my question is, does the driver update howto need to be updated to explain how to do this for SP3, or is this a mk_initrd bug? It seems that the way I've set this up, just outputting to the specific kernel that I know will wind up on the system, post-install, is not very portable either--it would fail if a different kernel was installed (on a different system perhaps). Thanks, Andy Wray