uname -r

Matt Harrington narse at underachiever.2y.net
Fri Oct 5 06:15:00 PDT 2001


    have you considered rebuilding your 2.4.8 kernel and seeing if the
problem persists?  it would take substantially less time than the other
options.  you should also check what version linux/version.h has.

on 10/5/01 9:03, Paul Abraham at Paul.Abraham at consultjoa.com wrote:

> I have just completed a compile of LFS 3.0, which seemed
> to go OK.  However, when I booted into it (i.e. not through
> chroot), I got a number of messages saying that modprobe
> couldn't find /lib/modules/2.4.7/modules.dep.
> 
> Having followed the book, I am pretty sure that I used version
> 2.4.8 of the kernel, not 2.4.7.  However, uname -r suggests
> that my version is 2.4.7.  I am convinced that I used 2.4.8
> in chroot.
> 
> The code in uname.c uses a function uname(), so I am assuming
> that my installation of glibc is broken.
> 
> I guess I have 4 options:
> a)  Rebuild the whole of LFS from the start.
> b)  Rebuild LFS from the start of the chroot environment.
> c)  Rebuild glibc and hope that I don't need to compile too
> many other things.
> d)  Find out the file that glibc uses to get the kernel version,
> change this to 2.4.8 and everything should then be OK.
> 
> I am assuming that d) can be done, because whenever I've updated
> my kernel in the past, uname -r gives the correct answer as soon
> as the machine is rebooted.
> 
> What should I do next?
> 
> Paul Abraham.
> --
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-support' in the subject header of the message
> 
> 

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message



More information about the lfs-support mailing list