where does uname get its info from ...etc
I got an unofficial snapshot .iso for Sarge, burned it to a CD
and installed from the CD. The installaton was very basic, and
I've been gradually and laboriously building it up by hand -
this has been very educational and has taught me a great deal.
Now as I was considering recompiling the kernel to my own
requirements, I find the following:-
---------------
a. 'uname -a' shows:-
Linux Leary..co.uk 2.4.21 #2 Tue Aug 26 14:43:43 BST 2003 i686 GNU/Linux
b. an extract from '/boot' shows:-
518609 Sep 5 19:25 System.map-2.4.22-1-386
512 Oct 28 20:33 boot.0340
42220 Sep 5 11:54 config-2.4.22-1-386
3383296 Oct 28 20:32 initrd.img-2.4.22-1-386
825011 Sep 5 19:25 vmlinuz-2.4.22-1-386
c. messages when booting include:-
Sun Nov 9 15:46:05 2003: modprobe: Can't open dependencies file
/lib/modules/2.4.21/modules.dep (No such file or directory)
Sun Nov 9 15:46:06 2003: modprobe: Can't open dependencies file
/lib/modules/2.4.21/modules.dep (No such file or directory)
d. '/lib/modules' is:-
drwxr-xr-x 4 root root 4096 Oct 28 20:32 2.4.22-1-386
-rw-r--r-- 1 root root 5883 Oct 28 20:32 modprobe.conf
-------------
The kernel I selected for install was 2.4.22-1, so why does uname
think it is 2.4.21? And, why is modprobe looking for modules for
2.4.21?
I have done nothing to bring the above about - and didn't notice
it before as I was concerned with other matters. Can anyone
offer an explanation please.
Regards, John.
Reply to: