From: "szonyi calin" <caszonyi@yahoo.com>
To: Paul Jackson <pj@sgi.com>, Adrian Bunk <bunk@fs.tum.de>
Cc: akpm@osdl.org, corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: New dev model (was [PATCH] delete devfs)
Date: Fri, 23 Jul 2004 10:16:37 +0200 (CEST) [thread overview]
Message-ID: <20040723081637.93875.qmail@web52903.mail.yahoo.com> (raw)
In-Reply-To: <20040722152839.019a0ca0.pj@sgi.com>
--- Paul Jackson <pj@sgi.com> a écrit : > > There's much worth
in having a very stable kernel.
>
> There certainly is. But the contribution that having a
> separate 2.7/2.8
> kernel at the head (Linus, et. al.) end has to a user having a
> stable kernel
> is not what you think it is.
>
;-)
> The direction presented to us now is having smaller, more
> continuous,
> steps in the head end, over having fewer larger, more
> disruptive steps.
> Do we do all the incompatible changes in a big chunk, once
> every couple
> of years, or do we do them one a week, ongoing.
>
... and break existing compatibility, and make the system crash
twice a day ...
> Now, I repeat, this is at the head end. End users who want
> stability
> aren't feeding directly off kernel.org anyway.
>
Are you sure ? There are a number of distribution who use the
stable kernel from kernel.org and some of them are much faster
(if you remember, compiling a kernel to suit your needs
sometimes improve performance).
One size _does not_ fit all.
> The affect downstream on real users is this. If the head end
> operates
> in big chunky style, then as this big change flows downstream,
> it makes
> transitions for distros, service providers and middlemen more
> costly and
> difficult, creating expenses that must be passed on to the end
> user.
>
And with new devepment model this expenses will be passed to the
end user when the kernel will not be stable enough and will
crash. Do you you remember the 8k vs 4k stack problem for
Nvidia binary kernel module ?
> Yes - damming up the flow of changes creates stability. But
> if you're a
> middleman, you don't need Linus to choose where to build the
> dam, and
> when to open the flood gates. It's more efficient for you to
> choose for
> yourself when to do that damming, based on your particular
> resources and
> customer needs, rather than have to deal with hundred year
> floods and
> draughts imposed on you by Zeus.
>
So now the world is divided in gods (i.e distributions) and we,
mere mortals who should pray to the gods to give us a stable
kernel ? And if we commit a sin our machine will crash ?
> The end user always gets their stability, if only because they
> won't
> upgrade a system that is "working".
>
They will get the stability through the new discovered
remote security hole because they don't upgrade their system
because "the system is working" and they don't need to upgrade ?
> And every change at the head end is disruptive for some poor
> slob.
> The only perfectly compatible change is no change at all. We
> delude
> ourselves if we think we can separate the "safe" fixes and
> additions
> from the "unsafe" incompatible changes. Better that we should
> expend
> some energy on smoothing out and minimizing the cost of change
> to those
> downstream from us. This needs to be done the old-fashioned
> way, one
> change at a time.
>
> The question is whether we impose, on all those downstream
> from us,
> occasional hundred year floods, or do we provide a steady
> stream, and
> let them build their own little beaver dams, as suits their
> various and
> diverse needs and business cycles.
>
> The great lesson of capitalism over communism is that a
> thousand free
> workers and investors, each optimizing their own little plot
> or
> portfolio, beats a single centrally imposed five year plan,
> even if the
> man pulling the levers is a genius such as Linus or Lenin
> (sorry, Linus,
> couldn't resist ...).
>
You are wrong here. You never saw the two systems working.
In comunism: One size fits all. This size is made to accomodate
80% of the population.
In capitalism: There are two sizes: one for rich and one for
the poor. The one for the poor is almost bullshit but is
cheap and anybody can afford it and the one for the rich
is verry expensive and only few can afford it.
Now do a s/poor/kernel.org kernel/ and s/rich/distribution
kernels/ and you see what your development model is.
=====
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
Vous manquez despace pour stocker vos mails ?
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2004-07-23 8:17 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 14:15 [PATCH] delete devfs Greg KH
2004-07-21 14:26 ` Oliver Neukum
2004-07-21 14:35 ` Lars Marowsky-Bree
2004-07-21 14:52 ` Greg KH
2004-07-21 21:19 ` Jesse Stockall
2004-07-21 21:27 ` Greg KH
2004-07-21 21:53 ` Jesse Stockall
2004-07-21 22:05 ` Greg KH
2004-07-21 22:17 ` Jesse Stockall
2004-07-21 22:47 ` Oliver Neukum
2004-07-22 6:49 ` Greg KH
2004-07-22 9:55 ` Oliver Neukum
2004-07-22 10:08 ` Paolo Ciarrocchi
2004-07-22 16:13 ` Matt Porter
2004-07-23 19:06 ` [RFC]: CONFIG_UNSUPPORTED (was: Re: [PATCH] delete devfs) R. J. Wysocki
2004-07-23 20:04 ` Adrian Bunk
2004-07-23 21:17 ` Russell King
2004-07-23 21:22 ` R. J. Wysocki
2004-07-23 23:35 ` Sam Ravnborg
2004-07-23 22:01 ` [RFC]: CONFIG_UNSUPPORTED Stephen Wille Padnos
2004-07-22 1:08 ` [PATCH] delete devfs Grzegorz Jaśkiewicz
2004-07-22 1:48 ` Mike Snitzer
2004-07-21 22:02 ` Adrian Bunk
2004-07-21 22:07 ` Greg KH
2004-07-21 22:14 ` David Weinehall
2004-07-21 22:31 ` Brian Gerst
2004-07-21 23:11 ` New dev model (was [PATCH] delete devfs) Jonathan Corbet
2004-07-21 23:52 ` Adrian Bunk
2004-07-22 9:55 ` Andrew Morton
2004-07-22 7:04 ` Greg KH
2004-07-22 10:19 ` Andrew Morton
2004-07-22 12:55 ` Josh Boyer
2004-07-22 11:32 ` Giacomo A. Catenazzi
2004-07-22 19:12 ` Greg KH
2004-07-22 19:33 ` Adrian Bunk
2004-07-22 22:28 ` Paul Jackson
2004-07-22 23:25 ` Adrian Bunk
2004-07-23 2:22 ` Tim Wright
2004-07-23 6:31 ` Ville Herva
2004-07-23 21:04 ` Valdis.Kletnieks
2004-07-23 21:08 ` Ville Herva
2004-07-25 11:59 ` Jan Knutar
2004-07-25 18:53 ` Jesper Juhl
2004-07-23 8:16 ` szonyi calin [this message]
2004-07-23 12:21 ` Jonathan Corbet
2004-07-23 19:59 ` Adrian Bunk
2004-07-24 14:24 ` Marcelo Tosatti
2004-07-23 14:54 ` Geert Uytterhoeven
2004-07-23 15:50 ` szonyi calin
2004-07-27 22:18 ` Bill Davidsen
2004-07-28 21:25 ` Krzysztof Halasa
2004-08-02 18:48 ` Bill Davidsen
2004-08-03 22:07 ` Krzysztof Halasa
2004-07-24 16:21 ` Ragnar Hojland Espinosa
2004-07-27 22:12 ` Bill Davidsen
2004-07-28 7:24 ` Paul Jackson
2004-07-22 23:01 ` Andrew Morton
2004-07-22 20:18 ` Adrian Bunk
2004-07-22 20:28 ` Kevin Fox
2004-07-23 20:09 ` Adrian Bunk
2004-07-22 21:01 ` Martin Schlemmer
2004-07-23 0:39 ` Jason Cooper
2004-07-23 20:57 ` Timothy Miller
2004-07-25 13:30 ` Adrian Bunk
2004-07-26 1:38 ` Ben Hoskings
2004-07-26 2:12 ` Bernd Eckenfels
2004-07-28 6:25 ` Ben Hoskings
2004-07-28 21:23 ` Krzysztof Halasa
2004-08-04 21:53 ` Bernd Eckenfels
2004-07-28 21:22 ` Krzysztof Halasa
2004-07-29 12:25 ` Adrian Bunk
2004-07-22 1:33 ` [PATCH] delete devfs Mike Snitzer
2004-07-21 23:26 ` R. J. Wysocki
2004-07-21 22:11 ` Francois Romieu
2004-07-21 22:40 ` Adrian Bunk
2004-07-21 23:15 ` Francois Romieu
2004-07-22 8:23 ` sam
2004-07-22 10:24 ` Gene Heskett
2004-07-22 10:58 ` Nick Piggin
2004-07-22 21:06 ` sam
2004-07-23 0:21 ` Gene Heskett
2004-07-22 22:19 ` Paul Jakma
2004-07-22 19:22 ` Martin Schlemmer
2004-07-22 17:56 ` Deepak Saxena
2004-07-21 14:52 ` Geert Uytterhoeven
2004-07-21 14:41 ` Matthew Garrett
2004-07-21 18:25 ` Greg KH
2004-07-21 19:55 ` Matthew Garrett
2004-07-21 19:34 ` Chris Wedgwood
2004-07-21 21:13 ` Ben Collins
2004-07-21 22:20 ` Wichert Akkerman
2004-07-22 19:44 ` Martin Schlemmer
2004-07-21 15:49 ` Kasper Sandberg
2004-07-22 7:45 New dev model (was [PATCH] delete devfs) Svetoslav Slavtchev
2004-07-22 10:40 ` Han Boetes
2004-07-22 13:17 Svetoslav Slavtchev
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=20040723081637.93875.qmail@web52903.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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®