In the future, consider add another step.
I like to build my kernels in my own directories, as an
unprivileged user, so I know I won't mess anything up.
make mrproper # you had mk, not mr
make oldconfig config dep clean bzImage modules
su root -c 'make modules_install'
If you run one iteration of make, it'll exit if any of the targets
don't go through clean. If you do something like "make oldconfig; make
config; make dep; make clean . . ." then you run the risk of make plowing
through your source tree, working from really screwy trees.
Just a suggestion.
On Thu, 10 Feb 2000, Eddie Strohmier wrote:
> Ric:
> Ya I corrected myself in a mail that came about 30 minutes later. My problem
> was that for some reason my new kernel was not finding its module
> dependancies on boot up as the rc.sysinit file should instruct it to do so
> it would just hang at that spot. After e-mailing the list I got the idea
> from Kim Hidong to run depmod after running make modules_install and that
> worked. But the question remains why did the modules dependancies not build
> on boot up. Oh well it is built now thanks to Kim who had this same problem.
>
> Eddie Strohmier
>
> ----- Original Message -----
> From: Ric Moore <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, February 10, 2000 10:31 AM
> Subject: Re: Kernel Build Question...
>
>
> > On Wed, 9 Feb 2000, Eddie Strohmier wrote:
> >
> > > I am rebuilding my kernel on a RH 6.0 2.2.5-15 system. I have 3 devices
> that
> > > needed adding after doing the folloing:
> > >
> > > make mkproper
> > > make config >> here I set all my options the way they should be set<<<
> > > make bzImage
> > > make dep
> > > make clean
> > > make modules
> > > make modules_install
> > >
> > Yeow, here's the way to do it...
> > > backing up my old kernel
> > > make mkproper
> > > make config >> here I set all my options the way they should be set<<<
> > > make dep <---
> > > make clean <--- this is the correct order of events
> > > make bzImage <---
> > > make modules
> > > make modules_install
> >
> > cp bzImage to /boot <--do not rename it!
> > edit lilo.conf using the name bzImage instead of vmlinuz
> > type lilo
> > type it again for luck
> > reboot
> >
> > bzImage is telling lilo to bunzip it first.
> > you had make bzImage in the wrong order.
> >
> > : Ric "Wayward" Moore : [EMAIL PROTECTED] :
> > : "If you can afford it, you don't want it" :
> > :--------------: New motto for Y2k : -----------:
> > : owned and trained by Calamity & Satin :
> > :-----------------------------------------------:
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
>
>
--
- Isaiah
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
