From: viro@parcelfarce.linux.theplanet.co.uk
To: Hua Zhong <hzhong@cisco.com>
Cc: "'Rob Love'" <rml@ximian.com>,
"'Jari Soderholm'" <Jari.Soderholm@edu.stadia.fi>,
linux-kernel@vger.kernel.org
Subject: Re: DEVFS is very good compared to UDEV
Date: Tue, 23 Dec 2003 23:05:55 +0000 [thread overview]
Message-ID: <20031223230555.GF4176@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <008401c3c9a3$0d11abe0$ca41cb3f@amer.cisco.com>
On Tue, Dec 23, 2003 at 02:21:03PM -0800, Hua Zhong wrote:
> But I do have sth fair to say about this "unmaintained" part.
>
> >From my memory, at some point in time, somebody (Al Viro?) reviewed
> devfs code and flamed the author in public (klml), throwing lots of bad
> impolite words to him, which I think was the biggest reason that the
> author stopped maintaining it.
Oh, really? That "flame in public" was after _many_ months of pointing
to the same problems in private - with zero effect.
If maintainer sits on exploitable holes for ~18 months and does not care to do
anything, his code is unmaintained. If same maintainer keeps pretending in
public that everything is fine, he can expect to have the truthfulness of his
statements challenged. Also in public. If the situation persists even after
that, then yes, there will be rather unflattering things to say.
Don't delude yourself - critical parts of devfs had not been maintained for
quite a while before Richard had disappeared. It's not the effect of flames
- it's their cause and it predates them by _far_.
next prev parent reply other threads:[~2003-12-23 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 21:20 DEVFS is very good compared to UDEV Jari Soderholm
2003-12-23 21:50 ` Stan Bubrouski
2003-12-23 22:01 ` Rob Love
2003-12-23 22:21 ` Hua Zhong
2003-12-23 22:30 ` Rob Love
2003-12-23 23:00 ` Hua Zhong
2003-12-23 23:03 ` Rob Love
2003-12-23 23:14 ` Greg KH
2003-12-23 23:26 ` viro
2003-12-24 0:00 ` Mike Fedyk
2003-12-23 23:03 ` grundig
2003-12-23 23:05 ` viro [this message]
2003-12-24 2:24 ` Paul Jackson
2003-12-23 22:24 ` Felipe Alfaro Solana
2003-12-27 11:57 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-12-24 3:33 Albert Cahalan
2003-12-24 18:40 ` Theodore Ts'o
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=20031223230555.GF4176@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=Jari.Soderholm@edu.stadia.fi \
--cc=hzhong@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@ximian.com \
/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