From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Fri, 05 Jan 2001 03:50:21 +0000 [thread overview]
Message-ID: <3A55447D.995FB159@goingware.com> (raw)
You might find it interesting to read the section entitled "Monkeywrenching the
Virtual Machine" towards the end of "Why We Should All Test the New Linux
Kernel". It's in my second comment after the main article:
http://advogato.org/article/224.html
I understand Linus' desire to have more widespread testing done on the kernel,
and certainly he can accomplish that by labeling some random build as the new
stable version. But I think a better choice would have been to advocate testing
more widely - don't just announce it to the linux-kernel list, get on National
Public Radio, the Linux Journal and Slashdot and stuff.
Don't just announce the existence of a kernel that people ought to test, but hit
the streets and provide advice and assistance and encouragement to those who
might help out.
That's the kind of thing I was trying to do in my article above.
My concern is that declaring this kernel as production and stable, with patching
still happening by the minute, is that a lot of people who don't know what
they're doing will slap it into machines they depend on for their livelihood,
and a lot of distributions will quickly adopt it in order to be perceived as
competitive. The very first experience many people will ever have with Free
Software will boot off Linux 2.4.0 - not 2.4.1, because some distro will want to
be the first.
You might think this is great because of all the extra testing the new users
will do but I assert that it isn't. The environment for Linux is quite
different these days than when 2.2 or 2.0 were released.
A lot of the people who will be using it are not technically savvy people, and
many of those who do know technology depend on its reliability for the
profitability of large businesses but may not read Linus' message that indicates
this is really just for testing.
It would be really bad if this particular version of the kernel turns out to
have a lot of problems.
I guess you can get more people testing by releasing it yourselves than I can
with my websites saying people should test, but I feel that having the testing
done by people who know what they're getting into and have some guidance is a
wiser course of action.
If you're in the neighborhood, please stop by:
http://linuxquality.sunsite.dk
Mike
--
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-05 7:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 3:50 Michael D. Crawford [this message]
2001-01-05 8:29 ` Change of policy for future 2.2 driver submissions Miles Lane
2001-01-05 17:31 ` Linus Torvalds
2001-01-09 14:49 ` Hubert Mantel
2001-01-09 14:54 ` Alan Cox
2001-01-09 23:49 ` Jakob Østergaard
2001-01-10 0:02 ` Linus Torvalds
2001-01-10 0:33 ` Ingo Molnar
2001-01-10 1:03 ` Andrea Arcangeli
2001-01-10 1:17 ` Ingo Molnar
2001-01-10 1:40 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-08 4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23 ` Christoph.Hellwig.
[not found] ` <hchÀcaldera.de>
2001-01-05 17:31 ` Alan Cox
2001-01-05 2:41 Alan Cox
2001-01-05 3:27 ` Nicholas Knight
2001-01-05 4:23 ` Mark Hahn
2001-01-05 12:52 ` Daniel Phillips
2001-01-05 6:38 ` Tim Riker
2001-01-05 6:57 ` Andre Tomt
2001-01-05 7:30 ` Gerhard Mack
2001-01-05 11:46 ` Rik van Riel
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=3A55447D.995FB159@goingware.com \
--to=crawford@goingware.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