hi alan,
So lets say I was to rebuild this system and make a new initrd.img and new
module-info -- what would i be doing to duplicate what was done with
mandrake when it was installed?
whats annoying is the old linux way of just installing modules with make
modules_install and such, then running lilo, still isnt updating the stuff
i need to have updated in /boot. i've read over some redhat documents
(mandrake sprang up from redhat) and haven't lucked out into finding the
answer yet.
so the question was what needs to occur when one is recompiling ones' own
kernel to rebuild the contents of the /boot directory. Can you point me
towards more than just 'man mkinitrd' because that doesn't seem like it is
all of it yet.
thanks!
-Dave D
-Seattle, WA
On Tue, 23 Jan 2001, Alan Shoemaker wrote:
> Date: Tue, 23 Jan 2001 11:36:38 -0800
> From: Alan Shoemaker <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] updating modules, initrd.img, module-info
>
> David Dennis wrote:
> > Problem:
> >
> > initrd.img and module-info point at the original mandrake
> > install version files in /boot from a year ago (initrd.img
> > -> initrd-2.2.14-15mdk.img and module-info ->
> > module-info-2.2.14-15mdk even after a make bzImage in
> > /usr/src/linux, a make modules and make modules_install,
> > and a make bzlilo. running lilo didn't fix things either.
> > So what happens now is my System.map and vmlinuz in /boot
> > point at 2.2.17 files but initrd.img and module-info point
> > at original install (2.2.14) files. I am not sure but this
> > is probably leading to a host of module errors received
> > upon bootup, and several important modules (sound card,
> > scsi support) are now failing to load.
> >
> > Forgive this post if it belongs on newbie, I am a old style
> > kernel compile person with limited experience with rpm.
> > The problem is now that I have a system with 2.2.17 (the
> > kernel version I compiled successfully using linus' tools)
> > but in /boot there is still the initrd.img and module-info
> > from when the system was installed.
> >
> > I don't want to have to reinstall to fix this, what must be
> > done instead? (note I do not have an install CD, this was a
> > from-the-net install.
> >
> >
> > -Dave Dennis
> > -Seattle WA
> > [EMAIL PROTECTED]
>
> Dave....check out 'man mkinitrd'.
> --
> Alan
>
>
