public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gábor Lénárt" <lgb@lgb.hu>
To: linux-kernel@vger.kernel.org
Subject: Re: Development tree, PLEASE?
Date: Fri, 20 Jan 2006 18:08:52 +0100	[thread overview]
Message-ID: <20060120170851.GA11489@lgb.hu> (raw)
In-Reply-To: <D1A7010C56BB90C4FA73E6DD@dhcp-2-206.wgops.com>

Though I'm not a kernel developer let me allow to comment this based on
my experiences as well.

On Fri, Jan 20, 2006 at 08:17:40AM -0700, Michael Loftis wrote:
> OK, I don't know abotu others, but I'm starting to get sick of this 
> unstable stable kernel.  Either change the statements allover that were 

What kind of instability have you got? I haven't had any instability since
at least a year or so, or if there was it was some kind of hardware fault.
In fact, many machines (like an Armada E500 notebook and some servers as well)
seems to be stable which was NOT in case of 2.4 kernels! So for our experience
at our workplace, 2.6 seems to be much more usable than 2.4.x kernels (ok,
it may be caused by "newer" hardwares, on quite old machines I can't show
major difference in stability between 2.4 and 2.6)

> made that even-numbered kernels were going to be stable or open 2.7. 
> Removing devfs has profound effects on userland.  It's one thing to screw 
> with all of the embedded developers, nearly all kernel module developers, 
> etc, by changing internal APIs but this is completely out of hand.

It was marked as obsoleted for some time ... I guess marking something
'osboleted' means that _NO_ new project should depends on it, and also
existing projects should be ported to the newer solutions. The purpose of
this process is to leave enough time for developers to react. I can't see
any problem here. You would be right if devfs would have been removed some
day without any notice before.
 
> Normally I wouldn't care, and I'd just stay away from 'stable' until 
> someone finally figured out that a dev tree really is needed, but I can't 
> stay quiet anymore.  2.6.x is anything but stable right now.  It might be 
> stable in the sense that most any development kernel is stable in that it 
> runs without crashing, but it's not at all stable in the sense that 
> everything is changing as if it were an odd numbered dev tree.

Ah, I see your point. But is it really a BIG problem? I mean please mention
some *real* issue/story confirm your opinion. Sure, you can find, but also
compare it with the advantages of new development model, since there is nothing
in the world which is only have advantages neither something which only has
disadvantages ... The would is not black or white, but a great spectrum of
gray shades.

> Yes, I'm venting some frustrations here, but I can't be the only one.  I 
> know now I'm going to be called a troll or a naysayer but whatever.  The 
> fact is it needs saying.  I shouldn't have to do major changes to 
> accomodate sysfs in a *STABLE* kernel when going between point revs.  This 
> is just not how it's been done in the past.

sysfs should not used by an average application, I guess, so it's not a major
point

-- 
- Gábor

  parent reply	other threads:[~2006-01-20 17:08 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 15:17 Development tree, PLEASE? Michael Loftis
2006-01-20 15:31 ` Michael Loftis
2006-01-20 15:59 ` Marc Koschewski
2006-01-20 16:07   ` Michael Loftis
2006-01-20 16:34     ` Marc Koschewski
2006-01-20 17:04       ` Michael Loftis
2006-01-20 16:35     ` Marc Koschewski
2006-01-20 17:06       ` Michael Loftis
2006-01-20 17:31         ` Diego Calleja
2006-01-20 20:43         ` Kyle Moffett
2006-01-20 16:41     ` Jan Engelhardt
2006-01-20 17:14       ` Michael Loftis
2006-01-20 19:43         ` Greg KH
2006-01-20 20:56           ` Michael Loftis
2006-01-20 21:06             ` Christopher Friesen
2006-01-20 23:00             ` Horst von Brand
2006-01-20 23:17             ` Russell King
2006-01-20 23:33               ` Michael Loftis
2006-01-20 23:55                 ` Russell King
2006-01-21  0:05                   ` Michael Loftis
2006-01-21  0:26                     ` Lars Marowsky-Bree
2006-01-20 23:27             ` Greg KH
2006-01-20 23:52               ` Michael Loftis
2006-01-21  0:03                 ` Russell King
2006-01-21  1:38             ` Alan Cox
2006-01-20 20:25         ` Russell King
2006-01-20 22:05           ` Michael Loftis
2006-01-20 22:54     ` Horst von Brand
2006-01-20 16:40   ` Dmitry Torokhov
2006-01-20 16:48     ` Marc Koschewski
2006-01-20 16:55       ` Dmitry Torokhov
     [not found]         ` <20060120172431.GE5873@stiffy.osknowledge.org>
2006-01-20 17:43           ` Dmitry Torokhov
2006-01-20 17:53             ` Marc Koschewski
2006-01-20 18:00               ` Dmitry Torokhov
2006-01-20 18:06                 ` Marc Koschewski
2006-02-13 17:17               ` Dmitry Torokhov
2006-01-20 16:29 ` James Courtier-Dutton
2006-01-20 16:36   ` Michael Loftis
2006-01-20 16:50     ` Dmitry Torokhov
2006-01-20 17:31       ` Michael Loftis
2006-01-20 19:03         ` Valdis.Kletnieks
2006-01-20 19:10           ` Michael Loftis
2006-01-20 23:20             ` Bernd Petrovitsch
2006-01-20 23:54               ` Michael Loftis
2006-01-20 19:21           ` Michael Loftis
2006-01-20 19:24             ` Valdis.Kletnieks
2006-01-20 20:00             ` Russell King
2006-01-20 21:21               ` Michael Loftis
2006-01-20 21:40                 ` Doug McNaught
2006-01-20 22:09                   ` Michael Loftis
2006-02-02 12:16                     ` David Weinehall
2006-02-02 18:25                       ` Michael Loftis
2006-02-02 20:10                         ` Dave Jones
2006-02-02 22:05                           ` Sam Ravnborg
2006-02-02 22:10                             ` Dave Jones
2006-02-02 22:19                               ` Sam Ravnborg
2006-02-02 22:31                                 ` Dave Jones
2006-02-02 22:42                                   ` Sam Ravnborg
2006-02-03  1:29                                 ` Roman Zippel
2006-02-03  4:45                                 ` Theodore Ts'o
2006-02-03 12:28                               ` Roman Zippel
2006-02-03 16:04                                 ` Dave Jones
2006-02-02 22:01                         ` Willy Tarreau
2006-02-02 22:31                           ` Christopher Friesen
2006-02-03  5:08                             ` Willy Tarreau
2006-02-02 22:15                         ` David Weinehall
2006-02-02 22:47                           ` Michael Loftis
2006-01-20 20:10             ` James Courtier-Dutton
2006-01-20 20:20         ` Jesper Juhl
2006-01-20 21:48           ` Michael Loftis
2006-01-20 22:00             ` Dmitry Torokhov
2006-01-20 22:14               ` Michael Loftis
2006-01-21  9:22             ` Jan Engelhardt
2006-01-21 14:52               ` Alistair John Strachan
2006-01-21 17:03                 ` Jan Engelhardt
2006-01-20 21:50           ` Michael Loftis
2006-01-21  9:13         ` Jan Engelhardt
2006-01-20 16:53     ` Joe George
2006-01-20 17:03       ` Randy.Dunlap
2006-01-20 17:33         ` Joe George
     [not found]     ` <20060120121116.62a8f0a6.seanlkml@sympatico.ca>
2006-01-20 17:11       ` sean
2006-01-20 17:56         ` Development tree, please? Michael Loftis
     [not found]           ` <20060120131120.338ebf17.seanlkml@sympatico.ca>
2006-01-20 18:11             ` sean
2006-01-20 18:43               ` Michael Loftis
2006-01-20 17:11     ` Development tree, PLEASE? Diego Calleja
2006-01-21  1:56     ` Matthew Frost
2006-01-21  3:19       ` Matthew Frost
2006-01-21  7:22         ` Michael Loftis
2006-01-21  7:38           ` Lee Revell
2006-01-21 21:56             ` Sven-Haegar Koch
2006-01-21 22:18               ` Lee Revell
2006-01-21 22:40                 ` Michael Loftis
2006-01-21 22:47                   ` Lee Revell
2006-01-21 22:51                     ` Bernd Petrovitsch
2006-01-22  8:57                       ` Michael Loftis
2006-01-22  9:41                         ` Theodore Ts'o
2006-01-22 16:09                         ` Bernd Petrovitsch
2006-01-22 22:59                         ` Daniel Barkalow
2006-01-21 22:49                   ` Bernd Petrovitsch
2006-01-21 23:03                   ` Lee Revell
2006-01-22  9:03                     ` Michael Loftis
2006-01-22 17:03                       ` Bernd Petrovitsch
2006-01-25 21:30                         ` Nix
2006-01-25 21:36                           ` Lee Revell
2006-01-25 22:12                             ` Nix
2006-01-26  8:44                               ` Bernd Petrovitsch
2006-01-26 21:12                                 ` Jan Engelhardt
2006-01-26 21:44                                   ` Bernd Petrovitsch
2006-01-22 17:14                       ` Arjan van de Ven
2006-01-22 17:24                       ` Lee Revell
2006-01-21 11:28           ` Jesper Juhl
2006-01-21 18:09           ` Horst von Brand
2006-01-20 17:08 ` Gábor Lénárt [this message]
2006-01-21  0:36   ` Michael Loftis
2006-01-20 19:16 ` Greg KH
2006-01-20 19:27 ` Ben Collins
2006-01-20 22:04   ` Vincent Hanquez
2006-01-21 18:29     ` Johan Kullstam
2006-01-23 13:45       ` Vincent Hanquez
2006-01-24 15:35       ` Bob Copeland
2006-01-21 11:41 ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2006-01-21  6:58 Michael Loftis
2006-03-14 13:57 Chuck Ebbert
2006-03-14 14:09 ` Arjan van de Ven
2006-03-16 20:17   ` Jan Engelhardt
2006-03-16 20:21     ` Jan Engelhardt

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=20060120170851.GA11489@lgb.hu \
    --to=lgb@lgb.hu \
    --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