Beat you too it. :-) Thanks, though.
-BVG
Robert Ambrose wrote:
>
> It's in the ramdisk that's being loaded during boot. Look at the initrd
> parameter in your lilo.conf file for the exact pathname. For now I'll use
> the pathname on my RH 6.1 system to illustrate.
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> + NOTE: The wise tread carefully doing things like this. You can make +
> + your system unbootable in a heartbeat. The trick is to always have a +
> + fallback plan, i.e. boot disk, boot entries in lilo.conf, etc. +
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> First uncompress the image:
>
> zcat < /boot/initrd-2.2.12-20.img > /tmp/initrd
>
> Next mount the ramdisk:
>
> mount -o loop /tmp/initrd /mnt
>
> There is a script '/mnt/linuxrc', which should be loading your
> modules at boot time. The modules are in /mnt/lib. Add/remove files and
> edit linuxrc to reflect the changes you want to make...
>
> Next unmount and recompress the ramdisk image. Don't forget to save a
> backup of the original ramdisk. I'd create another entry in lilo.conf in
> case you need to boot off of the original ramdisk.
>
> umount /mnt
> gzip < /tmp/initrd > /boot/initrd-2.2.12-20.img
>
> Last thing is to do a lilo so it can do it's mapping thing.
>
> rna
>
(text/plain)