linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tabris <tabris@tabris.net>
To: coderman <coderman@charter.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 vs 2.6
Date: Sun, 14 Dec 2003 15:23:14 -0500	[thread overview]
Message-ID: <200312141523.15209.tabris@tabris.net> (raw)
In-Reply-To: <3FDBC466.3060304@charter.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 13 December 2003 9:01 pm, coderman wrote:
> Jan Rychter wrote:
> >So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever
> > in running it, it caused me nothing but pain, and there is no
> > improvement that I could see that would justify the upgrade.
> >
> >So please be careful when making statements like that. 2.6 is *NOT*
> >stable enough nor ready enough for people to use it, unless those
> > people have a narrow range of hardware on which the 2.6 kernel has
> > actually been tested (translation: they have the same hardware as the
> > main developers do).
>
> For every person who has problems with 2.6, there are probably 2 others
> who have none, and enjoy the benefits of the new features.  2.6 works
> great for me, and one a number of hardware configurations including:
	Somehow, working for 2/3, or even 75% of cases is less than encouraging 
to me.

	Especially if I must not only set up boxes that I may not touch 
physically for days, weeks, etc. Or I suggest which kernel for other 
people to use, due to security fixes (which, iirc, not all 2.4 fixes have 
been forward ported yet), features, etc.

	2.6 is... getting there. and I DO much appreciate the work of the 
developers. But with devfs deprecated, udev still coming into its own 
(Nice work GregKG btw); with the myriad of (user visible) input layer 
changes; the change in focus on initrds (it used to be a nice thing that 
only serious people use. Now, although still optional, it is now becoming 
much more important). Or mebbe consider that the last time I tried to 
install the new modutils (I'm blaming my distro vendor for this), it 
broke my 2.4 modutils, requiring me to boot with init=/bin/sh and fix it 
up.

Sure. little things, but altogether, they add up to a lot more work to 
learn.

<snip>
>
> 2.6 may not be usable for you, but this has no bearing on the utility
> of the branch for others.  I have noticed benefits (mainly prempt,
> IPSEC, and the IDE device handling) which make it very worthwhile.
>
- --
tabris
- -
When asked by an anthropologist what the Indians called America before
the white men came, an Indian said simply "Ours."
		-- Vine Deloria, Jr.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3May1U5ZaPMbKQcRApmfAJ9IQexnFORYTaOEpTiyPQnHt3qCMgCeJimh
8hR+oaEqXhBXbVB9tRg9g5M=
=/Cnp
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-12-14 20:35 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  6:20 XFS for 2.4 Nathan Scott
2003-12-01  9:24 ` Jens Axboe
2003-12-01  9:44   ` Stefan Smietanowski
2003-12-01  9:45     ` Jens Axboe
2003-12-01 14:06 ` Marcelo Tosatti
2003-12-01 22:10   ` Nathan Scott
2003-12-01 22:20     ` Larry McVoy
2003-12-02  0:23       ` Nathan Scott
2003-12-02 11:22         ` Marcelo Tosatti
2003-12-02 18:05           ` Austin Gonyou
2003-12-02 19:55           ` Stephan von Krawczynski
2003-12-02 20:05             ` Marcelo Tosatti
2003-12-02 20:16             ` Lawrence Walton
2003-12-03 19:01           ` bill davidsen
2003-12-03 20:45             ` Willy Tarreau
2003-12-03 21:17               ` bill davidsen
2003-12-03 21:48                 ` Joel Becker
2003-12-03 22:17                   ` bill davidsen
2003-12-03 22:08                 ` Ed Sweetman
2003-12-04  5:21                   ` Willy Tarreau
2003-12-04  0:34               ` Clemens Schwaighofer
2003-12-04  5:33                 ` Willy Tarreau
2003-12-04 10:13                   ` Clemens Schwaighofer
2003-12-02 11:18     ` Marcelo Tosatti
2003-12-02 11:48       ` Marcelo Tosatti
2003-12-02 15:34       ` Russell Cattelan
2003-12-02 15:50         ` Marcelo Tosatti
2003-12-02 16:10           ` Darrell Michaud
2003-12-02 16:21             ` Austin Gonyou
2003-12-02 16:28             ` Jeff Garzik
2003-12-02 16:57               ` venom
2003-12-02 17:41               ` Stefan Smietanowski
2003-12-02 18:01           ` Russell Cattelan
2003-12-02 16:13         ` Jeremy Jackson
2003-12-02  0:51   ` Clemens Schwaighofer
2003-12-02  1:26     ` Marcos D. Marado Torres
2003-12-14  1:08   ` 2.4 vs 2.6 Jan Rychter
2003-12-14  1:01     ` Roberto Sanchez
2003-12-14 11:23       ` Måns Rullgård
2003-12-14 18:09         ` Daniel Gryniewicz
2003-12-14  1:53     ` Daniel Gryniewicz
2003-12-14  2:01     ` coderman
2003-12-14 20:23       ` tabris [this message]
2003-12-14  7:05     ` Voicu Liviu
2003-12-14 16:01       ` Roberto Sanchez
2003-12-14 17:32         ` Voicu Liviu
2003-12-15  7:23           ` Harry McGregor
2003-12-15  7:51             ` Voicu Liviu
2003-12-14 11:24     ` Frederik Deweerdt
2003-12-01 21:00 ` XFS for 2.4 Dan Yocum
2003-12-01 21:50   ` Bryan Whitehead
2003-12-01 22:01     ` Jeffrey E. Hundstad
2003-12-01 22:13     ` Gerardo Exequiel Pozzi
2003-12-02  2:54     ` Joshua Schmidlkofer
2003-12-02 11:02   ` Maciej Soltysiak
     [not found] <fa.iaibikf.1l5injd@ifi.uio.no>
     [not found] ` <fa.m5245vp.h0ukb5@ifi.uio.no>
2003-12-15 10:56   ` 2.4 vs 2.6 Anssi Saari
2003-12-15 17:25     ` David Ford

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=200312141523.15209.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=coderman@charter.net \
    --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;
as well as URLs for NNTP newsgroup(s).