mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: John Bradford <john@grabjohn.com>,
	Krzysztof Halasa <khc@pm.waw.pl>, <linux-kernel@vger.kernel.org>
Subject: Re: Some thoughts about stable kernel development
Date: Sun, 9 Nov 2003 17:54:21 -0600	[thread overview]
Message-ID: <200311091754.21619.rob@landley.net> (raw)
In-Reply-To: <200311091950.hA9Jo01d002041@81-2-122-30.bradfords.org.uk>

On Sunday 09 November 2003 13:50, John Bradford wrote:
> Hi Linus,
>
> [Off-list]
>
> Quote from Krzysztof Halasa <khc@pm.waw.pl>:
> > Such a scenario is real and that way we might
> > end up with official kernel being unusable for any Internet-connected
> > tasks for weeks.
>
> This does highlight a real issue - I am concerned by the number of
> posts on sites like lwn.net saying things like, "Oh, I'm using 2.6 as
> my standard kernel now", when it is clear that a lot of those users
> simply do not understand the issues.

At the same time, you _want_ as many testers as you can get finding the 
strange bugs where burning cd's on an ACPI-powered laptop interacts strangely 
with 3D acceleration.  And now that we're in the -test series, we want _more_ 
of them.

We know it's not safe.  There's a very real risk of a data-eating bug that 
could take out our filesystem (especially if we're using things like software 
suspend).  Of course those of us dragging laptops around have a very real 
risk of getting the suckers rained on, dropped, stolen, etc.  Very few 
non-laptop computers get run over by one's own car.  There's a larger than 
average chance of unintentional beverage interaction too, since the vital 
components are right under the keyboard in the beverage equivalent of ground 
zero.  (And don't tell me the hard drive enjoys being right under the 
keyboard, either.  Thump, thump, thump...)

So we have to back up a lot anyway. :)

99% of computer users don't understand the "issues" of connecting Windows XP 
to the internet, yet they do it anyway.  (Well, about 20% of them do.  More 
than that use W2k, and more than _that_ still use 98!)  I'd say there are a 
lot more issues with XP than 2.6.  (For one thing, 2.6 doesn't dial home to 
Linus and tell him what software packages you've installed. :)

I don't see what point is served by warning people away from a beta, pre-.0 
release.  I think we know.  Security considerations are just one more element 
of the party mix, and most of these are local (they've got to have broken 
into the box ANYWAY, it just potentially lets 'em crack root once they're 
in).

I'm still a lot more worried about what the kernel's doing to my filesystem 
than what some malicious twit on the internet is likely to do.  That's the 
main reason it's still -test...

Rob

  parent reply	other threads:[~2003-11-09 23:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:41 Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05   ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski
2003-11-12 15:07   ` Krzysztof Halasa
2003-11-12 16:04     ` Stefan Smietanowski
2003-11-12 16:51       ` Krzysztof Halasa
2003-11-13  7:33         ` Stefan Smietanowski
2003-11-13 19:55           ` Krzysztof Halasa
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34   ` Alan Cox
2003-11-09 20:41   ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01   ` Krzysztof Halasa
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49   ` Valdis.Kletnieks
2003-11-10  8:53     ` John Bradford
2003-11-09 23:54   ` Rob Landley [this message]
2003-11-10  8:50     ` John Bradford
2003-11-11  7:47       ` Ryan Anderson
2003-11-11  8:19       ` Valdis.Kletnieks
2003-11-11  8:53         ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48   ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance
2003-11-12 14:43   ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40   ` Krzysztof Halasa
2003-11-09 21:53 Matt

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=200311091754.21619.rob@landley.net \
    --to=rob@landley.net \
    --cc=john@grabjohn.com \
    --cc=khc@pm.waw.pl \
    --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®