Sort of answers the question but not entirely. I was running SuSE 6.1 with a
2.2.5 kernel but upgraded to a 2.2.12 (trying in vain to get rid of my serial
driver 'problem' and other niggles) but if I do 'uname -r' I get 2.2.5 as the
kernel version not 2.2.12. So where is proc getting it's info on my kernel
version?
Also, in response to the recommendation for my serial driver query that I
removed the file serial.o from /lib/modules/'uname -r'/misc, I went a step
further and renamed my whole /lib/modules/2.2.5 directory to
/lib/modules/old.2.2.5 and then renamed /lib/modules/2.2.12 as
/lib/modules/2.2.5 and got a load of error messages - hardly surprising I
suppose. Although I recently compiled my kernel without any modules it still
wants to load modules. Where does 'insmod' get called from if that's the right
question?
I think I'm getting there but I stil need pointing in the right direction!!
> ---------------------------------------------
> Attachment:�
> MIME Type:�multipart/signed
> ---------------------------------------------
> Hey, Lawson,
>
> I think that this looks like the right answer - I am going to try it right
> now. But this raises another question for me. Where does 'uname' get it's
> information from? It's probably obvious so apologies in advance if I'm being
a
> bit dense :^)
>
uname either makes a kernel call to find out this information, or looks
in /proc/sys/kernel, which has a bunch of files with this kind of info.
proc is a filesystem held in memory that the kernel sets up on boot and
mantains while the system is running
hope this answers your question
greg
--
public key available at www.keyserver.net
> ---------------------------------------------
> Attachment:�application/pgp-signature
> MIME Type:�application/pgp-signature
> ---------------------------------------------
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
