mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Zoltán HUBERT" <zoltan.hubert@zzaero.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please release a stable kernel Linux 3.0
Date: Fri, 22 Jun 2007 00:29:20 +0200	[thread overview]
Message-ID: <9a8748490706211529yca0588dgd1f7e0b86f7e4a62@mail.gmail.com> (raw)
In-Reply-To: <200706212349.54983.zoltan.hubert@zzaero.com>

On 21/06/07, Zoltán HUBERT <zoltan.hubert@zzaero.com> wrote:
[snip]
> All people who might read this know that traditionally
> stable releases are even numbered and development branches
> are odd numbered. This changed during late develoment of
> 2.6, according to my analysis because of the "invention" of
> GIT which was itself necessary because of BitKeeper (insert
> ooooooooold flame-wars here) and which allowed very dynamic
> develoment.

Git itself, nor bitkeeper was not the main reason behind the desition
to maintain 2.6.x as the stable kernel going forward.

> While this has been effective, alternative
> voices (Mr Morton complaining that more bugs were added
> than repaired, semi-stable semi-supported 2.6.x.y branches
> where invented...) come more and more into the front.

I myself have argued that we should be focusing more on stability and
regression fixing, but I'm not so sure that a 2.6.7 devel branch would
solve this. In general the 2.6.x.y -stable kernels seem to be doing
the job pretty good.

>The
> upcoming GPL v3 versus v2 debate will make things worse,

How is the GPLv2 vs GPLv3 debate relevant to kernel stability, ABI
stability or anything else of the sort?

> and we all know this. The un-ending stable ABI argument
> goes into this same direction.

What I think you are wishing for is a stable API - which is not going
to happen; please read Documentation/stable_api_nonsense.txt
(http://lxr.linux.no/source/Documentation/stable_api_nonsense.txt).
A stable ABI we already have.

[snip]
> You might think it's easy for me to simply "use" Linux and
> complain while you're doing the hard stuff. As it happens,
> the current development/stable model makes our life as
> "users" more and more difficult.

In what way?

Most users should be using distribution kernels anyway, not vanilla
kernel.org kernels. Those distribution kernels should provide you with
all the stability you require.

>I'm using Linux since 1997
> on a Mac thanks to LinuxPPC-1997, and I'm a hard pusher of
> Linux whenever possible, sometimes against the common
> sense, for example when I favor using National Instrument
> cards with Linux drivers and custom written TCP/IP server
> against easy LabView on Windows. While some of you dislike
> closed source drivers, the choices "we users" face are:
> - closed source drivers with closed source OS
> - closed source drivers with open source OS
> Please consider that we are living in a REAL world, and not
> Disney-Land.
>

As far as I am aware, both nVidia and ATI have closed drivers
available for you to use if you please. And they should work just fine
with most distribution kernels as well as vanilla.


> So I've demonstrated that from a "users" perspective a new
> stable Linux would be of advantage. I'll now list what I
> suggest for this new stable branch:
>
I don't think you have demonstrated that.
How specifically is the current development model hurting you?
What exactely would we gain by switching back to the old
stable/unstable branch model?

[snip]
> Why on earth
> call "kernel object" things that are "kernel modules" ? And
> that every person calls "modules" and not "objects" ? I
> know I know, in UNIX dynamic libraries are .so "shared
> objects", so what ? A "module" is a "module" and NOT an
> "object", call a cat a cat.
>
It sure is an object, it's even called object code. I think the name
suits just fine. In any case, it's just a name.

> Third, while a stable ABI in a dynamically developed kernel
> is a difficult/impossible/unwanted feature,

A stable ABI is very much a wanted feature and one that a lot of work
goes into maintaining.
Note; ABI != API.

> it should be
> possible to implement in a stable branch. This could even
> be a distinction between "stable" and "development"
> branches. And it would certainly help vendors of
> closed-source drivers.
>
If they want to keep their drivers closed they get to do all the hard
work of tracking kernel API changes. Their choice, their problem. I
don't think you'll find very many people on this list who gives a damn
about the troubles of closed source driver developers.

[snip]


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2007-06-21 22:29 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 21:49 Zoltán HUBERT
2007-06-21 21:54 ` Chuck Ebbert
2007-06-21 22:08 ` Alan Cox
2007-06-21 22:21   ` Zoltán HUBERT
2007-06-22 20:54     ` Willy Tarreau
2007-06-21 22:29 ` Jesper Juhl [this message]
2007-06-21 22:34   ` Chuck Ebbert
2007-06-21 23:01     ` Lennart Sorensen
2007-06-21 23:08       ` Chuck Ebbert
2007-06-21 23:36         ` Måns Rullgård
2007-06-21 23:45         ` Arjan van de Ven
2007-06-28 21:15           ` Pavel Machek
2007-06-29 13:41             ` Rafael J. Wysocki
2007-06-29 22:33               ` Pavel Machek
2007-06-22 15:00     ` Rafael J. Wysocki
2007-06-22 17:11       ` Chuck Ebbert
2007-06-22 22:10         ` Rafael J. Wysocki
2007-06-24 20:54         ` Rafael J. Wysocki
2007-06-25 16:38           ` Chuck Ebbert
2007-06-25 23:20             ` Rafael J. Wysocki
2007-06-25 23:23               ` Chuck Ebbert
2007-06-21 22:57   ` Zoltán HUBERT
2007-06-21 23:07     ` Jesper Juhl
2007-06-21 23:23     ` Lennart Sorensen
2007-06-22  8:34     ` Bernd Petrovitsch
2007-06-26 11:59     ` Helge Hafting
2007-06-26 14:37       ` Zoltán HUBERT
2007-06-26 15:04         ` Renato S. Yamane
2007-06-26 19:03         ` Roland Kuhn
2007-06-27  9:18           ` Zoltán HUBERT
2007-06-27  9:54             ` Alan McKinnon
2007-06-27  9:55             ` Al Viro
2007-06-27 14:44             ` Helge Hafting
2007-06-27 16:13             ` Chuck Ebbert
2007-06-29 16:37             ` Gerhard Mack
2007-06-21 23:30   ` Jan Engelhardt
2007-06-21 23:32     ` david
2007-06-22  8:41       ` Jan Engelhardt
2007-06-21 22:52 ` Stefan Richter
2007-06-21 22:59   ` Zoltán HUBERT
2007-06-21 22:58 ` Rene Herman
2007-06-22  3:51 ` Rik van Riel
2007-06-22  9:19 ` Xavier Bestel
2007-06-22  9:45   ` Bernd Petrovitsch
2007-06-23  7:25 ` Chris Snook
2007-06-27 13:53 Al Boldi
2007-06-27 15:52 ` Adrian Bunk
2007-06-27 16:08   ` Chuck Ebbert
2007-06-27 16:26     ` Dmitry Torokhov
2007-06-27 16:26     ` Adrian Bunk
2007-06-27 22:32   ` Al Boldi
2007-06-27 17:11 ` Al Viro
2007-06-27 22:32   ` Al Boldi
2007-06-27 23:12     ` Al Viro
2007-06-28 15:37       ` Al Boldi
     [not found] <fa.ZV8hYZHQHqzfx1dgOFeEVFRogSg@ifi.uio.no>
2007-06-27 14:15 ` Bill Waddington
2007-06-28 11:15   ` Helge Hafting
2007-06-28 15:28     ` William D Waddington
2007-06-28 16:30       ` Alan Cox
2007-06-28 16:39         ` William D Waddington
2007-06-29  0:00           ` Alan Cox
2007-06-28 21:39         ` Al Viro
2007-06-28 22:00         ` Rene Herman
2007-06-28 22:48           ` Alan Cox
2007-06-28 22:45             ` Rene Herman
     [not found] <8AH0j-3Qc-11@gated-at.bofh.it>
     [not found] ` <8AH0j-3Qc-9@gated-at.bofh.it>
     [not found]   ` <8B0vZ-r6-5@gated-at.bofh.it>
     [not found]     ` <8B46G-69z-15@gated-at.bofh.it>
     [not found]       ` <8B52G-7C9-5@gated-at.bofh.it>
     [not found]         ` <8BalK-7Ic-39@gated-at.bofh.it>
     [not found]           ` <8BaYr-8tJ-17@gated-at.bofh.it>
2007-06-29 21:05             ` Bodo Eggert
2007-06-29 21:27               ` Rene Herman
2007-06-30  2:11                 ` Daniel Hazelton
2007-06-30 10:50                   ` Rene Herman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a8748490706211529yca0588dgd1f7e0b86f7e4a62@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zoltan.hubert@zzaero.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®