Well here it is:
if you systems is a scsi machine you need to have initrd to boot
otherwise you will not be able to. Of course you do not need that with
the ide drive that's why is not there. Every time you rebuild your
kernel, usually upgrading only you need to recompile your initrd as well
otherwise you will get an error at boot time..........which is kernel
panic .... In redhat there is a file that allows you to make your initrd
instead of doing it manually which is a little more time consuming. In
RH the script is called mkinitrd you may want to man that to get all the
info needed to recompile the new initrd.

Hopefully this will help you.
Remo


**************************
I don't think I saw an answer to this, so I'll attempt to fashion one
with
my
limited knowlege:

I *think* that the image files are related to sczi devices.  From the RH

7.0
Reference Guide:

"An initrf image is needed for loading your SCSI module at boot time."

This said, I would suspect that one system has sczi device(s) - HDs? -
and
the
other doesn't.

-Jacob

On Tue, 27 Mar 2001, you wrote:
> Two machines, both updated using up2date today.  The lilo.conf files
are
> different in a way that I've not noticed before:
>
> Machine A:  (dual boot machine)
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> linear
> default=linux
>
> image=/boot/vmlinuz-2.2.17-14
>          label=linux
>          read-only
>          root=/dev/hda6
>
> other=/dev/hda1
>          label=dos
>
>
> Machine B:
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> default=linux
>
> image=/boot/vmlinuz-2.2.16-22
>          label=linux
>          initrd=/boot/initrd-2.2.16-22.img
>          read-only
>          root=/dev/hda6
>
>
> Where I'm confused is WHY does Machine B have the line
> 'initrd=/boot/initrd-2.2.16-22.img' and Machine A does not.
>
> Since I've upgraded the kernel on Machine B, then I need to change the

> 'image=/boot/vm.....' line on Machine B.  Question is, what do I do
with
> the 'initrd=/boot/init......' line ?
>



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to