[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: Re: initrd-[kernal#].img ???
Thanks for the help Steve ...
--- Steven Pritchard <steve@silug.org> wrote:
> From: Steven Pritchard <steve@silug.org>
> Subject: Re: initrd-[kernal#].img ???
> To: jburke@burkepoirier.com
> Date: Tue, 3 Apr 2001 22:34:41 -0500 (CDT)
>
> James L. Burke said:
> > Truth is i don't think I have the spare brain power left to absorb
> the
> > dark are of kernal hacking ... all I want to do is update to the
> latest
> > RedHat kernal/errata for 7.0.
>
> This should do it:
>
> rpm -ivh kernel-2.2.17-14.i386.rpm # or i586 or i686
> cd /boot
> for file in vmlinuz System.map ; do
> ln -sf $file-2.2.17-14 $file
> done
> mkinitrd /boot/initrd-2.2.17-14.img 2.2.17-14
>
> Then just edit /etc/lilo.conf appropriately to add the new kernel,
> run
> lilo, and reboot.
>
> > i then went to /etc/lilo.conf to add a section for my updated
> kernal
> > and I notice the following line in the section relating to my "old"
> > kernal:
> >
> > initrd=/boot/initrd-2.2.16-22.img
> >
> > what is the initrd-2.2.16-22.img file?
>
> "initrd" is short for "initial ramdisk". Basically, the trick to not
> needing every driver necessary to boot actually compiled into the
> kernel is to boot with an initrd which contains the necessary modules
> and enough of a filesystem to boot. The initrd boot script loads the
> modules, then switches to the real root filesystem.
>
> > do I need an initrd-2.2.17-14.img?
>
> Only if you are booting off of something other than IDE.
>
> I hope that helps...
>
> Steve
> --
> steve@silug.org | Southern Illinois Linux Users Group
> (618)398-7320 | See web site for meeting details.
> Steven Pritchard | http://www.silug.org/
>
>
=====
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.