Oh where is my kernel?

Uname - r brings up the kernel version - desktop. I’m not to sure what’s going on

It looks like the actual kernel is under /lib/modules not lib64 ?

usr/src/linux uses a symbolic link for linux but this takes me to the correct version but not with the - desktop on the end. I would like to correct this. Is it possible to use a symbolic link that includes ‘uname -r’ so that it always links to the correct one?

The boot menu also shows the correct version but doesn’t have - desktop on the end.

I’m assuming uname -r is always correct. :\ I would hope so.

John

On 04/30/2011 05:06 PM, ajohnw wrote:
>
> Uname - r brings up the kernel version - desktop. I’m not to sure
> what’s going on
>
> It looks like the actual kernel is under /lib/modules not
> lib64 ?
>
> usr/src/linux uses a symbolic link for linux but this takes me to the
> correct version but not with the - desktop on the end. I would like to
> correct this. Is it possible to use a symbolic link that includes ‘uname
> -r’ so that it always links to the correct one?
>
> The boot menu also shows the correct version but doesn’t have - desktop
> on the end.
>
> I’m assuming uname -r is always correct. :\ I would hope so.

The actual kernel in in /boot/vmlinuz-<version info>. The files in
/lib/modules/uname -r are the modules for currently running kernel.

The boot menu is just the title line in file /boot/grub/menu.lst. The rest of
the lines in that stanza contain the file name of the kernel, and yes, “uname
-r” knows what kernel is currently running.

Thanks for clearing that up for me.

I was hoping to create a symbolic link …/‘uname -r’/build to replace the linux one in usr/scr/ as the current one points at the wrong directory. 1st attempt, using kde failed but no problems providing an ordinary link to the correct directory.

What I’m not now clear about now is if there is any way of creating a symbolic link that uses ‘uname -r’ so that it will point at the correct directory automatically. Some how from some time ago I had the impression that 'uname -r" is a general relatively low level function so that it is always replaced with the correct text.

On 04/30/2011 06:36 PM, ajohnw wrote:
>
> Thanks for clearing that up for me.
>
> I was hoping to create a symbolic link …/‘uname
> -r’/build to replace the linux one in usr/scr/ as the current one
> points at the wrong directory. 1st attempt, using kde failed but no
> problems providing an ordinary link to the correct directory.
>
> What I’m not now clear about now is if there is any way of creating a
> symbolic link that uses ‘uname -r’ so that it will point at the correct
> directory automatically. Some how from some time ago I had the
> impression that 'uname -r" is a general relatively low level function so
> that it is always replaced with the correct text.

Yes, uname is a command. Those are back ticks around the uname -r, not forward
ticks '. In bash, the shell processor, text inside the ` is replaced by the
results of the command.

For your enjoyment, look at the following commands and output:

finger@larrylap:~>echo uname -r
2.6.37.6-0.5-desktop
finger@larrylap:~> echo ‘uname -r’
uname -r

:\ Thanks I have spent donkey’s years writing software and have never typed a back tick in my life. Even staring at my keyboard failed to find it. I normally don’t even look at it. One lives and learns. Google tells me it’s next to 1.