On Wed, 28 Mar 2001, Remo Mattei wrote:
> 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
>
If you look at his lilo.conf files, both machines are IDE machines,
running 2.2.x kernels. With the root file system on an IDE drive, you
do not need an initial RAM disk, because the drivers for the root file
system are build in the kernel. (This is not the case with the 2.4.x
kernels, from what I understand...)
The exception to this is if you are using a IDE controller that the
standard IDE driver doesn't work with.
>
> 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 ?
> >
Look in /etc/modules.conf, and see if you loading a module for your IDE
controller. If not, you do not need the initrd line. If you need a
special IDE driver, then you will have to run mkinitrd, or compile a
custom kernel with the driver installed.
As a check, create the entry for the new kernel with out the initrd
line, and see if the system boots. If so, you are done. If it doesn't,
select the old kernel and boot, then run mkinitrd. (Always keep the old
kernel, and a LILO entry for it, untill you are sure the new kernel is
working right!)
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
