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 ?
> 
> Thanks,
> Mike
> -- 
>  
>   Multitasking:  Screwing up several things at once...
>   1:55am  up 49 min,  6 users,  load average: 1.04, 1.08, 1.06
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
-- 
Jacob Killian
PGTC System Administrator

<mailto: [EMAIL PROTECTED]>
<http://www.pgtc.net>

501-846-7245

"Long may we walk" --my mom



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

Reply via email to