Well yes and no. Pardon my cluelessness.
rpm -Uvvh kernel-2.2.17mdk-21.i586.rpm
the rpm fails in post-install with some failed attempt at
/sbin/installkernel -- the values for $MAPFILE and $BOOTIMAGE were
wrong. the script failed and my install was left with
/boot/vmlinuz--c
which were results of installkernel having no idea where things were
supposed to go with $1, $2, $3. This was with the /sbin/installkernel
that was in the original 2.2.14mdk system of 18 months ago.
I did try just setting KERNEL-VERSION=2.2.17-21mdk, BOOTIMAGE=/vmlinuz and
MAPFILE=/System.map in /sbin/installkernel and running the rpm -Uvvh
again. That finished the script and all was fine there with bootable
System.map and vmlinuz, but now they were 2.2.16 (my last source compile
from non rpm source and the process still left me with no module support
other than modules that had not changed from 2.2.14, in other words no
remade modules.dep perhaps?
A url to a step by step updation of kernel from rpm to rpm using mandrake
kernel and installkernel which covers modules and /boot requirements would
be useful right about here. Or just how to get a system onto a baseline
update version. A lot of the HOWTOS you see around predate rpm-style
builds.
thanks!
-Dave Dennis
-Seattle, WA
On Tue, 23 Jan 2001, John Wolford wrote:
> Date: Tue, 23 Jan 2001 15:22:52 -0800 (PST)
> From: John Wolford <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] updating modules, initrd.img, module-info
>
> Hi Dave,
>
> After you're done doing
> # make modules modules_install bzdisk
> etc, do
> # make install
>
> and watch the screen fill up with stuff you don't have
> to do manually anymore!
>
> I think this answers your question, pardon me if it
> doesn't.
>
> -John
>
> --- David Dennis <[EMAIL PROTECTED]> wrote:
> > 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
> > >
> > >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - Buy the things you want at great prices.
> http://auctions.yahoo.com/
>
>
