mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: caszonyi@rdslink.ro
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: Edgar Hucek <hostmaster@ed-soft.at>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New Linux Development Model
Date: Wed, 9 Nov 2005 16:03:06 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.62.0511091547080.15950@grinch.ro> (raw)
In-Reply-To: <5a2cf1f60511090430y63db5473we40f077070ecb43a@mail.gmail.com>

On Wed, 9 Nov 2005, jerome lacoste wrote:

> On 11/9/05, caszonyi@rdslink.ro <caszonyi@rdslink.ro> wrote:
> [...]
>>
>> There are other reasons for using a new kernel. One of them is
>> interactivity. In the days of 2.4 one could achieve decent interactivity
>> for the desktop using preempt and low latency patches. For 2.6
>> interactivity was a real issue (possibly because of the new development
>> model).
>
> I don't get it. You say that with 2.4 + patches you had good
> interactivity and with 2.6 you don't? Why did you switch then?
>

Because i like to test new kernels. On 2.4 I run the vanila kernel and a 
test kernel. When something went wrong on a test kernel was always a 
stable kernel to use.
2.6 looks a lot like 2.5. New features are added very quickly without much 
testing. Of course there is Andrew's -mm tree but this one sometimes 
is too broken.
For me linux looks now like it has one unstable tree (2.6) which is 
something like -ac was in days of 2.4 and  -mm was in the days of 2.4 
-2.5 and -mm which looks like it became very unstable.
This is what i saw ok lkml (maybe my view is distorted).
I'll stop ranting and try both of them because i have some bugs to report.

>>>> And why should dirstribution makers always backport new security fixes ?
>>>
>>> Because they want to ensure maximum stability. That's what users are
>>> (sometimes) paying for.
>>>
>>
>> Maximum stability of what ? If the distribution kernels are based on
>> vanila kernel (i.e. are based on unstable kernel) how stable will they be
>> ?
>
> Maximum stability of the kernel they deliver. When you fix a
> vulnerability, you fix a vulnerability. You don't just happen to add a
> new bunch of features, and a new bunch of bugs. Otherwise you are
> going to piss off your users a lot.
>

That's what's happening on 2.6. Every 2.6.x release is different.
The 2.6.x.y kernels sometimes are almost no different from 2.6.x


--



  reply	other threads:[~2005-11-09 14:03 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05  9:42 hostmaster
2005-11-05 10:29 ` Francois Romieu
2005-11-05 11:29 ` Jean Delvare
2005-11-05 13:19   ` Edgar Hucek
2005-11-05 13:44     ` Adrian Bunk
2005-11-05 13:47     ` Alistair John Strachan
2005-11-05 22:23       ` Mark Lord
2005-11-06  0:28         ` Alistair John Strachan
2005-11-05 14:34     ` Jesper Juhl
2005-11-05 14:48       ` Oliver Neukum
2005-11-05 14:56         ` Fawad Lateef
2005-11-05 15:28         ` Adrian Bunk
2005-11-06 10:52     ` jerome lacoste
2005-11-06 11:55       ` Edgar Hucek
2005-11-06 12:39         ` Adrian Bunk
2005-11-06 12:57         ` Bernd Petrovitsch
2005-11-06 17:38         ` Jean Delvare
     [not found]       ` <436DEEFC.4020301@ed-soft.at>
2005-11-06 13:43         ` jerome lacoste
2005-11-09  0:11           ` caszonyi
2005-11-09  0:23             ` Con Kolivas
2005-11-09  7:00               ` Diego Calleja
2005-11-09 12:30             ` jerome lacoste
2005-11-09 14:03               ` caszonyi [this message]
2005-11-09 15:45                 ` Marcos Marado
2005-11-06 16:50       ` John Carlson
2005-11-06 18:17     ` Bernd Petrovitsch
2005-11-09  0:16       ` caszonyi
2005-11-06 15:22 ` Jim Nance
2005-11-06 16:55   ` John Carlson
2005-11-09  1:47 Ian Kumlien
2005-11-09 11:08 ` Marcos Marado
2005-11-09 11:30   ` Ian Kumlien
2005-11-09 12:03     ` Wed, 9 Nov 2005 13:03:07 +0100
2005-11-09 15:49       ` Ian Kumlien
2005-11-09 15:58         ` Al Viro
2005-11-09 16:32           ` Ian Kumlien
2005-11-09 12:37     ` Marcos Marado
2005-11-09 16:01       ` Ian Kumlien
2005-11-10  0:55         ` Alistair John Strachan
2005-11-10 15:10           ` Mark Lord
2005-11-10 19:29             ` Alistair John Strachan
2005-11-10 19:47               ` Ian Kumlien
2005-11-09 19:05   ` Bill Davidsen
2005-11-09 20:10     ` Marcos Marado
2005-11-10  0:57       ` Alistair John Strachan
2005-11-10 20:08         ` Bill Davidsen
2005-11-10 20:21           ` Alistair John Strachan
2005-11-12 13:45       ` Bill Davidsen

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=Pine.LNX.4.62.0511091547080.15950@grinch.ro \
    --to=caszonyi@rdslink.ro \
    --cc=hostmaster@ed-soft.at \
    --cc=jerome.lacoste@gmail.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

all inboxes | Powered by JetHome®