OpenSUSE 11.2 uses kernel version 2.6.31, doesn't 31 indicate experimental or developmental?

Probably because of an uneven version number ?

The uneven number for a development version, examples:
2.3.xx , 2.5.xx , 2.7.xx , etc. etc.
>>> The "third group" in the version can be both even
or uneven for a stable version.
..

If you look in depth it is even "2.1.31.12-2.0.2-default" where the default may be some other type of kernel, depending from your setup. The above describes the status of patches applied by SuSE/Novell. All is well with 2.6.31...

yes i looked it up on wikipedia.
I didn't fully understand though, you got me with probably because its an odd number? (indicating agreement) then the third number can be stable or unstable if its odd. I was only reassured by all is well with kernel 2.6.31 thanks for answers though fellas.

likewise...

that bit about patching and defaults I don't understand but don't feel compelled to answer, I'm preoccupied with something else. thanks!

you mean this? about the patching...http://en.wikipedia.org/wiki/Ksplice

never would have guessed although I wondered why RPC kept running (and it is possible this doesn't make sense to you because its my attempt at understanding what I saw). RPC may well have nothing to do with the entire mess. I did manage to get an update or two, if either of you read my previous posts and that is around when or when my boot options doubled from 2 to 4.

can you say, why would opensuse boot options menu change to a wintry scene when I removed my CMOS battery? lol
Imagine my surprise!

No, not at all. This is bleeding edge and very much professional technology (statement not meant as demeaning the normal patching process). Better look here: http://en.wikipedia.org/wiki/Patch_%28computing%29.

In short: the original program-files of the kernel are changed by a patch or patches, i.e. some statements in the "c" programming language are changed prior to a new compilation. (Try "man patch" in a console). The distributors keep logs of the changes (patches) they apply and name a reached status arbitrarily like 2.6.31.12-2.0.2 thus documenting that there is a hierarchy even in patching.

Lack of fire under its butt ? I somewhere stumbled upon a function which randomly changes the slpash screen but I don't remember anymore where that resides. Again, don't worry .

alright let me read this entry. I actually scrapped SUSE, it just keeps producing errors and the fact that the bookstores only have 10.3 was a sign to me! haha...but I think I'm going to install LFS and perhaps WUBI.

Specific errors were packagekit id transaction errors, another update error which I don't recall now that I removed it, I was getting PID confusions (which is wierd I've never seen that in any operating system --and this perhaps shows the extent of my knowledge) among others. The one that did it though is that the desktop globe theme open map didn't work! it was so much less intensive that Goog too!

anyhow let me read this article and thanks for the information.
When you say bleeding edge do you mean the entry you gave or ksplice?

Umm. That might rather be a sign for you concerning your choice of book stores . 10.3. is already retired from support, milestone 6 of 11.3 was recently published with a date of finalization sometime next month. If you buy it, look here http://www.godboxslx.com/ or on the novell pages. LFS is a steep going for all I know but three cheers for you if you really tackle that one.

...not posted, so I can't even try to help .

ksplice.