linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Viro <viro@math.psu.edu>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Ian Molton <spyro@f2s.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: devfs
Date: Tue, 12 Nov 2002 05:04:41 -0500 (EST)	[thread overview]
Message-ID: <Pine.GSO.4.21.0211120445570.29617-100000@steklov.math.psu.edu> (raw)
In-Reply-To: <1037094221.16831.21.camel@bip>



On 12 Nov 2002, Xavier Bestel wrote:

> I'm wondering if a totally userspace solution could replace devs ?
> Something using hotplug + sysfs and creating directories/nodes as they
> appear on the system. This way, the policy (how do I name what) could be
> moved out of the kernel.

	Guys, may I remind you that Oct 31 had been more than a week ago?
Devfs *is* a race-ridden pile of crap, but we are in a goddamn feature
freeze, so let's get real.

	Interfaces can and should be cleaned up.  Ditto for semantics of
registering/unregistering - that allows to make glue in drivers more
straightforward.  Majestic flamewars about removing the thing completely/
moving it to userland/etc. are exercises in masturbation by that point.

	Again, WE ARE IN FEATURE FREEZE.

	Now, does somebody have technical comments on the proposed changes?


  parent reply	other threads:[~2002-11-12  9:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  9:32 devfs Ian Molton
2002-11-12  9:43 ` devfs Xavier Bestel
2002-11-12  9:49   ` devfs john slee
2002-11-12 10:01     ` devfs Sean Neakums
2002-11-12 12:51       ` devfs Oliver Neukum
2002-11-13 10:48         ` hotplug (was devfs) Nick Craig-Wood
2002-11-13 17:02           ` Greg KH
2002-11-13 18:06             ` Nick Craig-Wood
2002-11-13 18:04               ` Greg KH
2002-11-14 11:46             ` Oliver Neukum
2002-11-12 10:05     ` devfs Xavier Bestel
2002-11-12 10:04   ` Alexander Viro [this message]
2002-11-12 10:25     ` devfs Ian Molton
2002-11-12 10:46       ` devfs Dave Jones
2002-11-12 11:08         ` devfs Ian Molton
2002-11-12 11:24         ` devfs Rando Christensen
2002-11-12 13:30           ` devfs Alexander Viro
2002-11-12 14:53         ` devfs Alan Cox
2002-11-12 15:37           ` devfs Ian Molton
2002-11-12 11:29     ` devfs Helge Hafting
2002-11-12 15:40   ` devfs Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2002-08-18  9:10 cerberus errors on 2.4.19 (ide dma related) Alexander Viro
2002-08-18  9:16 ` Ed Sweetman
2002-08-18 18:10   ` Ed Sweetman
2002-08-18 18:20     ` Sean Neakums
2002-08-18 18:29       ` Ed Sweetman
2002-08-18 18:36         ` Sean Neakums
2002-08-18 21:53           ` Barry K. Nathan
2002-08-18 22:26             ` devfs Ed Sweetman
2002-08-18 22:47               ` devfs Sean Neakums
2002-08-18 23:03               ` devfs Alexander Viro
2002-08-18 23:15                 ` devfs Ed Sweetman
2002-08-21  4:49                   ` devfs Richard Gooch
2002-08-21  5:03                     ` devfs Ed Sweetman
2002-08-19  1:06                 ` devfs Olivier Galibert
2002-08-19  2:01                   ` devfs Greg KH
2002-08-18 23:18               ` devfs Barry K. Nathan

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=Pine.GSO.4.21.0211120445570.29617-100000@steklov.math.psu.edu \
    --to=viro@math.psu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spyro@f2s.com \
    --cc=xavier.bestel@free.fr \
    /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;
as well as URLs for NNTP newsgroup(s).