According to Mitchell Maltenfort: While burning my CPU.
>
>
> I'm trying to figure out if this command is trivial, vital, dangerous or =
> negligible.
>
> I recompiled my kernel some weeks ago, following the directions for a =
> comparable system (Toshiba 330 CDS) at the Linux for Laptops page and =
> the HOWTO for making the kernel ready to talk to a ZIP drive (which I =
> mean to get real soon now..)
>
> Anyway, I was going back through my RedHat 5.2 manual and I noticed =
> something I somehow skipped over before. The manual claims "an initrd =
> image is needed for loading your SCSI module at boot time." It =
> recommends I run /sbin/mkinitrd to build a 'proper initrd image.' =
> However, it does *not* tell me how to back up the old image if I screw =
> up. As a newbie, I am reluctant to do anything without a list of =
> instructions for undoing it.
I took a look at /sbin/mkinitrd, its a script, they say, "never trust
scripts" they can sometimes fail.
(Of course i am not saying it will fail.)
You can rename your image in /boot and edit /etc/lilo.conf to reflect the
changes and rerun lilo, that will ensure that any thing you do will not
write over the old image.
Your new image be it made by mkinitrd or simply by you, reconfiguring and
recompiling your kernel and then being copied to /boot and giving it a name,
for example vmlinuz-2.0.xx, editing /etc/lilo.conf and adding another entry
for that kernel image, will not have any ill effect on you old kernel.
Dont forget to rerun lilo otherwise the new kernel will not be found.
>
> I plan to be getting the parallel port Zip drive which requires the imm =
> adapter. I double-checked what I did for my kernel vs. the new HOWTO at =
> http://njtcom.com/dansie/zip-drive.html. However, I saw no instruction =
> for running /sbin/initrd in there. =20
In my opinion theres no need to use any script to configure anything, they
are handy tho' i must add, for someone who is dubious about compileing and
coping there new kernel, if you used slackware then you would need to do it
yourself, which in my oppion gives you much more experiance in just "how
linux works".
I rather think redhat is getting to much like Win9x it does things for you
but does it the way redhat wants it, which is not always the way i (and a
lot of others) want it.
>
> When I reboot, SCSI support seems to be initializing happily even though =
> no devices are found.
>
> So is anyone familiar with these issues who can set me straight? Thanks =
> in advance.
>
>
--
Regards Richard.
[EMAIL PROTECTED]
