[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel compilation

	Unless I am in serious error, if uname -a gives you Kernel Linux 2.0.29,
it really means you still are running that kernel.  What I usually do now, (i
dont' wipe out the headers anymore) is the standard make mrproper, make
menuconfig, make dep, make clean, make zImage, make modules, make
modules_install.  Modify my /etc/lilo.conf, run lilo.  Do an update on
bootsect.lnx since I am quadbooting.  Then... this is new to me, since I am used
to slackware and modifying rc.d/rc.modules..... I copied the zImage to /vmlinuz
(probably better off copying zImage to /boot/vmlinuz-2.0.33 then remaking the
symlink in the "/")  I rebooted, made sure I was running the new kernel via
uname -a.

Then.... instead of modifying /etc/rc.d/rc.modules (slackware), I realized
Debian has this cool "modconf" which lets you "add modules".... you add them all
in.  It saves them into the /etc/modules and you reboot, and it should have
everything working 100%.

I did miss the earlier part of this thread, so sorry if this info is not helpful
or redundent.  

Carroll Kong

On Sun, 8 Mar 1998 shaul@rakefet.debian.org wrote:

> Thank you. 
> mv /lib/modules/2.0.29  /lib/modules/2.0.29.old did it.
> I think it ought to be in the README file, toghther with the other differences 
> between the stable and unstable behaviour of the package.
> BTW: Why does the kernel compilation number don't get updated in the uname 
> command ?
> 	$ uname -a
> 	Linux rakefet 2.0.29 #1 Sat Mar 7 19:54:49 UTC 1998 i586 unknown

E-mail the word "unsubscribe" to debian-user-request@lists.debian.org
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble?  E-mail to listmaster@debian.org .

Reply to: