kernel naming & CREATED FIELD
Dennis Veatch
dennisveatch at bellsouth.net
Tue Jan 10 20:25:21 CET 2012
On Tuesday, January 10, 2012 7:48:52 PM Zbigniew Luszpinski wrote:
> > Alright,
> >
> > just had a talk on IRC with Ratler. Here's how it should be:
> >
> > linux-stable = 3.1.8 (always the latest stable kernel as kernel.org
> > reports)
> > linux = 3.2.0 (mainline kernel)
> > linux-unstable = next-20120106 (linux-next)
> >
> > Which means, that just linux-unstable is wrong. He also said:
> >
> > "Only way we can go with a ultra stable kernel would be IF we decide to
> > actually go with stable/unstable moonbase :)"
>
> I think we should follow kernel.org main page and name modules
> accordingly:
> mainline: 3.2 linux
> stable: 3.1.8 linux-stable
> stable: 3.0.16 linux-stable-old
> stable: 2.6.39.4 linux-2.6
> stable: 2.6.35.14 linux-stable-2.6
> stable: 2.6.33.20 linux-stable-2.6-old
> stable: 2.6.32.53 linux-stable-2.6-deprecated
> Mainline would be always recent using linux module.
>
> linux-next: next-20120110 only on gitweb not tarball. Released daily.
> I do not see any reason to implement this one. It changes too often so no
> use on server/desktop.
>
> have a nice day,
> Zbigniew Luszpinski
>
> _______________________________________________
I would be in favor of that method. Though I don't think we need that many 2.6
versions.
--
Dennis Veatch
Lunar-Linux Developer
http://lunar-linux.org
More information about the Lunar-dev
mailing list