From: "Zoltán HUBERT" <zoltan.hubert@zzaero.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Please release a stable kernel Linux 3.0
Date: Wed, 27 Jun 2007 11:18:36 +0200 [thread overview]
Message-ID: <200706271118.36985.zoltan.hubert@zzaero.com> (raw)
In-Reply-To: <6FD45914-1793-45D5-B0A1-F5D32ED38017@e18.physik.tu-muenchen.de>
Thanks Roland,
On Tuesday 26 June 2007 21:03, Roland Kuhn wrote:
> On 26 Jun 2007, at 16:37, Zoltán HUBERT wrote:
> > Whatever "stable" means.
>
> What you mean by "stable" pretty much excludes any
> serious development, without which the Linux kernel would
> very soon be obsolete. If you want a stable system, then
> don't change it.
This is a problem. Do you remember that kernel vulnerability
in 2.4 that made the Debian servers be attacked ? And
mplayerhq.hu too if I remember right ? So what are we
supposed to do with a perfect and optimised system, running
smoothly, with an older kernel where some nasty bug is
discovered ?
In MacOS X, you click "System Update" and you're done.
In Linux, I expect "download the newest stable kernel,
configure, compile, install, reboot".
If I have to rely on the distribution to help me it spoils
the whole benefit of open source. I don't trust Novell or
RedHat or Google more than Microsoft or Apple. You "kernel
developpers" are the keepers of the flame.
> If you update to a kernel which is 2.5
> years newer, you simply cannot have stability, because
> that would mean stagnation, aka "death".
PostScript is a very old language yet we all still use it
every day. HTML is a very old "thing" and we use it
every-day, and it's still compatible with newer and older
stuff.
I'm a system engineer, and a "stable" system is one where
the interfaces are stable. Individual components can
change, and do change, but if you change fundamental
interfaces it is not the same system. Of course I
understand that "sometimes" fundamental things have to
change, but here "sometimes" is the keyword. If its
"anytime" it simply is no stable system. And yes, designing
and maintaining interfaces is a very difficult job.
I don't remember how it was during 2.4 and before, but I
find it very suspicious that SuSE and RedHat only provide
2.6.10 and 2.6.9 for their OS. It looks as if THEY didn't
trust 2.6.x to be a replacement to 2.6.y
And as I understand it, this is (was ?) the whole point of
stable/development kernels. "We" can trust a newer stable
kernel to be a drop-in replacement for an older stable
kernel (from the same series), while development kernels
need time to stabilise with the new whizz-bang-pfouit stuff
that you all so nicely add.
Are the good ol' days lost in nostalgia ?
bye
Zoltán
--
________________________
Zoltan
________________________
next prev parent reply other threads:[~2007-06-27 9:15 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
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 [this message]
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=200706271118.36985.zoltan.hubert@zzaero.com \
--to=zoltan.hubert@zzaero.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome