You are not logged in.

#1 2008-11-09 18:25:38

userlander
Member
Registered: 2008-08-23
Posts: 413

Arch kernel designation

How come the full kernel version isn't included in the arch kernel? Like when doing uname -r, it only shows 2.6.27-ARCH, and not what further revision of .27 it is. Would it be too hard to include that, so we could know whether it was 2.6.27.1, or 2.6.27.5, etc?

Offline

#2 2008-11-09 19:24:10

fwojciec
Member
Registered: 2007-05-20
Posts: 1,411

Re: Arch kernel designation

pacman -Qs ^kernel26

Offline

#3 2008-11-09 19:37:31

userlander
Member
Registered: 2008-08-23
Posts: 413

Re: Arch kernel designation

thanks - and that only takes like 13.68x longer than uname-.  tongue

Offline

#4 2008-11-09 20:03:26

finferflu
Forum Fellow
From: Manchester, UK
Registered: 2007-06-21
Posts: 1,899
Website

Re: Arch kernel designation

pacman -Q kernel26

Should take about the same time as uname -a tongue


Have you Syued today?
Free music for free people! | Earthlings

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery

Offline

#5 2008-11-09 20:30:43

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: Arch kernel designation

userlander wrote:

How come the full kernel version isn't included in the arch kernel? Like when doing uname -r, it only shows 2.6.27-ARCH, and not what further revision of .27 it is. Would it be too hard to include that, so we could know whether it was 2.6.27.1, or 2.6.27.5, etc?

So that in kernel 2.6.x.y, modules do not have to be rebuilt for every LOCALVERSION y release, but only for every EXTRAVERSION x release. If I recall, the kernel is supposed to be module compatible across all LOCALVERSION (y) releases, but not necessarily across EXTRAVERSION (x) releases.

It was a conscious decision, and not a 'it is too hard to add the point release so you can get it in the uname'.


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

#6 2008-11-09 20:36:43

shazeal
Member
From: New Zealand
Registered: 2007-06-05
Posts: 341

Re: Arch kernel designation

How come the full kernel version isn't included in the arch kernel?

As far as uname goes, so that /lib/modules/2.6.27-ARCH does not become...

/lib/modules/2.6.27.1-ARCH
/lib/modules/2.6.27.2-ARCH
/lib/modules/2.6.27.3-ARCH
/lib/modules/2.6.27.4-ARCH
/lib/modules/2.6.27.5-ARCH

It means that the NVIDIA, VirtualBox etc modules always stay in the same place so if their bindings arent changed (unusual in a kernel fix update) then the modules just keep on working rather than needing a new version of them for every kernel update.

Just shows pacman > uname tongue

EDIT: DAMN YOU TACO MAN! beat me to it tongue

Last edited by shazeal (2008-11-09 20:37:23)

Offline

#7 2008-11-10 01:26:56

userlander
Member
Registered: 2008-08-23
Posts: 413

Re: Arch kernel designation

cactus wrote:
userlander wrote:

How come the full kernel version isn't included in the arch kernel? Like when doing uname -r, it only shows 2.6.27-ARCH, and not what further revision of .27 it is. Would it be too hard to include that, so we could know whether it was 2.6.27.1, or 2.6.27.5, etc?

So that in kernel 2.6.x.y, modules do not have to be rebuilt for every LOCALVERSION y release, but only for every EXTRAVERSION x release. If I recall, the kernel is supposed to be module compatible across all LOCALVERSION (y) releases, but not necessarily across EXTRAVERSION (x) releases.

It was a conscious decision, and not a 'it is too hard to add the point release so you can get it in the uname'.

I see - thanks for the explanation. I knew there had to be some reason, but I had no idea what it was.

Offline

Board footer

Powered by FluxBB