[SLE] New kernel for SuSE?
I still can't figure out the SuSE policy on updating kernels for their distro. Is it policy to produce a new kernel for each update, or it that a carrot held in reserve to encourage people to upgrade to the next SuSE release? I never saw a 2.2.15 for SuSE-6.x, but 2.2.16 is a security fix, and therefore a priority. Will a 2.2.16 be made available? -- ---------------------------------------------------------- Derek Fountain | "Microsoft have performed an IBM Labs, Hursley, UK | illegal operation and will fountai at hursley.ibm.com | be shut down" ---------------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Derek Fountain wrote:
I still can't figure out the SuSE policy on updating kernels for their distro. Is it policy to produce a new kernel for each update, or it that a carrot held in reserve to encourage people to upgrade to the next SuSE release?
I never saw a 2.2.15 for SuSE-6.x, but 2.2.16 is a security fix, and therefore a priority. Will a 2.2.16 be made available?
IIRC, anything ending in an odd number is a development version - even numbers are release-suitable. If you want to run with the development version, go ahead, but remember, they don't call it the "bleeding edge" for nothing! -- Regards Don Hansford ECKYTECH COMPUTING Surfing the Net (without crashing) With SuSE 6.4 Linux (Thanx Linus!) "Microsoft democratised the computer market and served as a catalyst in making computers available to everybody. Later, however, they did as many revolutionaries do -- they became dictators. History has taught us the inevitable fate of dictators." -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hmm ... Wat had odd/even got to do with it? In x.yz version syntax x is a major realease, y is a minor release and z is a bugfix... it's been like that since I was knee high to a grasshooper... even Noah used it when he was counting those animals.. sheesh!! Chris On Sat, 10 Jun 2000 01:08:14 +1000, Don Hansford wrote:
Derek Fountain wrote:
I still can't figure out the SuSE policy on updating kernels for their distro. Is it policy to produce a new kernel for each update, or it that a carrot held in reserve to encourage people to upgrade to the next SuSE release?
I never saw a 2.2.15 for SuSE-6.x, but 2.2.16 is a security fix, and therefore a priority. Will a 2.2.16 be made available?
IIRC, anything ending in an odd number is a development version - even numbers are release-suitable. If you want to run with the development version, go ahead, but remember, they don't call it the "bleeding edge" for nothing! --
Regards Don Hansford ECKYTECH COMPUTING Surfing the Net (without crashing) With SuSE 6.4 Linux (Thanx Linus!) "Microsoft democratised the computer market and served as a catalyst in making computers available to everybody. Later, however, they did as many revolutionaries do -- they became dictators. History has taught us the inevitable fate of dictators."
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I'm lazy.. I'd rather smile and be happy, than work my face muscles so hard to frown... why not join me!!! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 31 Dec 1969, Brevsville Administrator wrote:
Hmm ...
Wat had odd/even got to do with it?
In x.yz version syntax
x is a major realease, y is a minor release and z is a bugfix... it's been like that since I was knee high to a grasshooper... even Noah used it when he was counting those animals.. sheesh!!
Just because it is common among the stuff you're used to does not mean it works well for all cases. And in fact it doesn't work well for open-source products in general. On most software products, there is a *lot* of stuff going on behind the scenes between versions 2.2.1 and 2.2.2. There may be a dozen or a hundred builds - separate times the system is compiled and linked - between those. Most of them won't fix the problem you're trying to fix. Many of them will introduce other problems. A few just plain won't work. On an open-source product, many, perhaps all, of those dozen or hundred builds will be PUBLIC. Which means that either you need a fourth part to the version, or you need some other means of tracking builds. Further, at the same time that you are working on the bug fix for version 2.2.2, you are also developing the next minor release. The same people are involved in both projects. How do you order the version and build numbers? The rule for Linux is: Even minor versions are stable. They are equivalent to 2.2.1 above. The third part is, more or less, a bugfix number. Linux kernel 2.2 got up to bugfix 14 or 15, maybe a bit higher but not much. Odd minor versions are unstable. They are equivalent to all those builds, and the third part of the version number is the build number. Kernel 2.3 got past build number 900 - how far past I am not sure. Now at some point in 2.3, a feature list for 2.4 (the next stable version) was frozen - meaning that it's extremely unlikely anything will be added to it. But things can be taken off, if the project leaders decide that the feature won't be stable soon enough to be included. Shortly thereafter, the main builders stripped out all the new stuff not on the list and released a new build based on the list. Now the developers and testers know what to emphasize. As soon as 2.4 is released for general use, work on 2.5 will begin. It's another development version, and all the stuff (well, some will probably be dropped as a bad idea, but most...) that was stripped out to make 2.4 will soon be added to it. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Don Hansford wrote:
Derek Fountain wrote:
I still can't figure out the SuSE policy on updating kernels for their distro. Is it policy to produce a new kernel for each update, or it that a carrot held in reserve to encourage people to upgrade to the next SuSE release?
I never saw a 2.2.15 for SuSE-6.x, but 2.2.16 is a security fix, and therefore a priority. Will a 2.2.16 be made available?
IIRC, anything ending in an odd number is a development version - even numbers are release-suitable.
Nope. The *middle* number denotes whether it's development or release thus 2.0.38 is a release kernel 2.1.12 is a development kernel 2.2.15 is a release kernel (as is 2.2.16) 2.3.4 is a development kernel They've now started releasing 2.4.x kernels, but note they're suffixed with a test number. Think of them as release candidates, or betas, for the 2.4 release. -- Rachel -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (5)
-
admin＠brevsville.com.au -
donh＠halenet.com.au -
fountai＠hursley.ibm.com -
rachel.greenham＠enetgroup.co.uk -
warrl＠blarg.net