Do this on a *copy* of the floppy disk ONLY!! If it doesen't work or breaks something you have all the pieces. I started writing this as I'd done it for initrd files on the hard disk... part way through I realised it was different (for RH6.2 boot disk at least), I have therefore *not* tested this procedure but it may help to unravel the mystery, literally. 1) mount the install floppy somewhere mount -t vfat /dev/fd0 /mnt/floppy 2) The initrd file is actually a filesystem of it's own, you'll need to uncompress it and mount it using the loopback interface. gunzip -c /mnt/floppy/initrd.img >/tmp/initrd.img mkdir /mnt/img mount -t ext2 -o loop /tmp/initrd.img /mnt/img 3) Go to the modules directory on the floppy and notice the modules.cgz file. It's a gzipped CPIO archive so unarchive it to somewhere nice. cd /tmp gunzip -S .cgz -c /mnt/img/modules/modules.cgz | cpio -i -d cd 2.2.14-5.0BOOT (or whatever the kernel version is). 4) add/delete module files as needed. Remember not to go overboard adding stuff, it's gotta fit on the floppy somewhere! Check/adjust the modules.dep and module-info file in the /mnt/img/modules directory. *THIS* is the hard bit. 5) Recompress the modules directory ls 2.2.14-5.0BOOT/* | cpio -o | gzip -9 >/mnt/img/modules/modules.cgz 6) Write the dummy filesystem and unmount it sync; cd /tmp; umount /mnt/img 7) write the compressed image back to the floppy cat initrd.img | gzip -9 >/mnt/floppy/initrd.img There you have it, give it a go! For the initrd file used in lilo configs the headache is slightly less. The modules aren't inside a gzipped CPIO container. You have to edit the linuxrc file which loads the modules though. ---<GRiP>--- Grant Parnell [EMAIL PROTECTED] ([EMAIL PROTECTED]) Ph: 02-8701-4564 Mob: 0408-686-201 Web: http://linuxfreak.com/~gripz No Microsoft products were used in the production of this message. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
