From: kernel <kernel@crazytrain.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] Wireless Extension v17 (resend)
Date: Tue, 08 Feb 2005 20:21:42 -0500 [thread overview]
Message-ID: <1107912102.3858.11.camel@crazytrain> (raw)
In-Reply-To: <1107911344.3863.9.camel@crazytrain>
Message below meant for Marcelo!
(sorry rest!)
On Tue, 2005-02-08 at 20:09, kernel wrote:
> On Tue, 2005-02-08 at 13:41, Marcelo Tosatti wrote:
> > > There need to be some unique features in 2.6.X to force people
> > > to upgrade, I guess...
> >
> > Faster, cleaner, way more elegant, handles intense loads more gracefully,
> > handles highmem decently, LSM/SELinux, etc, etc...
> >
>
> Please *think* before saying this. It's not always the case. Firewire
> support in 2.6 kernel has been less than stellar, for one example. And
> yes, for many, solid 1394 support is a requirement for business.
>
> (And we've all seen the testing that has shown both sides (2.4, 2.6)
> have been faster)
>
> > IMO everyone should upgrade whenever appropriate.
> >
>
> Not sure....on 13 January 2005 Alan Cox posted "Given that base 2.6
> kernels are shipped by Linus with known unfixed
> security holes anyone trying to use them really should be doing some
> careful thinking. In truth no 2.6 released kernel is suitable for
> anything but beta testing until you add a few patches anyway."
>
> How do you answer this, when telling folks "everyone should upgrade
> whenever appropriate."?
>
>
> Just some random thoughts....from a 2.4 supporter :)
>
> -fd
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2005-02-09 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 18:16 [PATCH 2.4] Wireless Extension v17 (resend) Jean Tourrilhes
2005-02-08 18:01 ` Marcelo Tosatti
2005-02-08 21:51 ` Jean Tourrilhes
2005-02-08 18:41 ` Marcelo Tosatti
2005-02-08 22:45 ` Willy Tarreau
2005-02-08 20:05 ` Marcelo Tosatti
2005-02-09 0:37 ` Jean Tourrilhes
2005-02-09 1:51 ` Chris Wright
2005-02-09 2:07 ` Jean Tourrilhes
2005-02-09 2:17 ` Chris Wright
2005-02-09 1:09 ` kernel
2005-02-08 22:28 ` Marcelo Tosatti
2005-02-09 1:21 ` kernel [this message]
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=1107912102.3858.11.camel@crazytrain \
--to=kernel@crazytrain.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