mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudmer van Dijk <rudmer@legolas.dynup.net>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] devfs API
Date: Tue, 12 Nov 2002 09:44:52 +0100	[thread overview]
Message-ID: <20021112083811Z266406-32598+5165@vger.kernel.org> (raw)
In-Reply-To: <20021112080417.GA11660@think.thunk.org>

On Tuesday 12 November 2002 09:04, Theodore Ts'o wrote:
> On Mon, Nov 11, 2002 at 08:49:22PM -0500, Alexander Viro wrote:
> > The only way I'll use devfs is
> > 	* on a separate testbox devoid of network interfaces
> > 	* with no users
> > 	* with no data - disk periodically populated from image on CD.
> > 
> > And that's regardless of that cleanup - fixing the interface doesn't solve
> > the internal races, so...
> 
> Hi Al,
> 
> It's good that you're trying to clean up the devfs code, but...
> 
> How many people are actually using devfs these days?  I don't like it
> myself, and I've had to add a fair amount of hair to fsck's
> mount-by-label/uuid code to deal with interesting cases such as
> kernels where devfs is configured, but not actually mounted (it
> changes what /proc/partitions exports).  So I'm one of those who have
> never looked all that kindly on devfs, which shouldn't come as a
> surprise to most folks.

well I like devfs, in the sense that it is really easy to see what you can 
use in /dev. Before i used devfs it could be quite difficult since there were 
so much nodes and symlinks in /dev and many have cryptic names... and 
sometimes the entries i needed simply were not there so i had to find the 
right major/minor numbers to create them...

from a user point of view it is better to keep it because it could really 
simplify a users life except ide should be just in discs as hdX and not as 
/dev/ide/hostN/busX/targetY/lunZ/disc ...

> 
> In any case, if there aren't all that many people using devfs, I can
> think of a really easy way in which we could simplify and clean up its
> API by slimming it down by 100%......

if the code is really that horrible, then maybe that is the best solution but 
again i like the concept.

	Rudmer

  reply	other threads:[~2002-11-12  8:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10 22:19 Alexander Viro
2002-11-10 23:52 ` oops when adding bridge interface, using v2.5.45 Bart De Schuymer
2002-11-10 23:08   ` romieu
2002-11-11  0:49     ` Bart De Schuymer
2002-11-12  1:32 ` [RFC] devfs API Ryan Anderson
2002-11-12  1:49   ` Alexander Viro
2002-11-12  8:04     ` Theodore Ts'o
2002-11-12  8:44       ` Rudmer van Dijk [this message]
2002-11-12  9:50         ` Miles Bader
2002-11-12 10:57         ` Helge Hafting
2002-11-12  9:43       ` Alexander Viro
2002-11-12 10:47       ` Helge Hafting
2002-11-12 21:57       ` Jon Portnoy
2002-11-13 15:15       ` Denis Vlasenko
2002-11-12  1:50   ` Robert Love
2002-11-12 11:44 ` William Lee Irwin III
2002-11-14 17:51 ` Richard Gooch
2002-11-14 18:04   ` Alexander Viro

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=20021112083811Z266406-32598+5165@vger.kernel.org \
    --to=rudmer@legolas.dynup.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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®