From: Christoph Hellwig <hch@infradead.org>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Ro0tSiEgE LKML <lkml@ro0tsiege.org>,
KML <linux-kernel@vger.kernel.org>
Subject: Re: devfsd
Date: Fri, 18 Jul 2003 08:44:17 +0100 [thread overview]
Message-ID: <20030718084417.B14336@infradead.org> (raw)
In-Reply-To: <1058507844.13515.1579.camel@workshop.saharacpt.lan>; from azarah@gentoo.org on Fri, Jul 18, 2003 at 07:57:24AM +0200
On Fri, Jul 18, 2003 at 07:57:24AM +0200, Martin Schlemmer wrote:
> Apart from obvious/known inefficiencies, it works fine over here :P
>
> Any way, if you are serious, what make you consider it broken (no,
> not talking about personal preferences/phobias 8)
There's unsolvable design issues in the way devfsd communication works
(with the last two patches the holes are closed as much as possible)
and it's fundamentally flawed by putting device name policy into
the kernel. And then there's of course certain implementation quality
issues...
We have udev now which solves what devfs tried to solve without that
issues so people should switch to that ASAP. That doesn't mean we
can simply rip it out because people started to rely on the non-standard
device names, but it's use is pretty much discouraged in 2.6.
next prev parent reply other threads:[~2003-07-18 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 21:46 devfsd Ro0tSiEgE LKML
2003-07-17 15:56 ` devfsd Christoph Hellwig
2003-07-17 16:38 ` devfsd Michael Buesch
2003-07-18 5:57 ` devfsd Martin Schlemmer
2003-07-18 7:44 ` Christoph Hellwig [this message]
2003-07-18 7:52 ` devfsd Oliver Neukum
2003-07-18 8:15 ` devfsd Christoph Hellwig
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=20030718084417.B14336@infradead.org \
--to=hch@infradead.org \
--cc=azarah@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@ro0tsiege.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