mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rando Christensen <rando@babblica.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: spyro@f2s.com, viro@math.psu.edu, xavier.bestel@free.fr,
	linux-kernel@vger.kernel.org
Subject: Re: devfs
Date: Tue, 12 Nov 2002 04:24:08 -0700	[thread overview]
Message-ID: <20021112042408.02d2e3e3.rando@babblica.net> (raw)
In-Reply-To: <20021112104650.GA322@suse.de>

Tue, 12 Nov 2002 10:46:50 +0000: Dave Jones (Dave Jones
<davej@codemonkey.org.uk>):

> On Tue, Nov 12, 2002 at 10:25:35AM +0000, Ian Molton wrote:
>  > > 	Again, WE ARE IN FEATURE FREEZE.
>  > And since when did feature freeze affect, as the guy said, *purely*
>  > userspace implementations?
>  Since it would a *feature* to move it out of kernel space.
>  To reiterate : _FEATURE_ _FREEZE_. Nothing[1] new[2]
>  should be going into mainline at this point.

Well, it does make sense to start planning out what might be done to
devfs in the /next/ devel kernel, then. If one were so inclined, they
could have a stable enough system for it ready for inclusion next time
around, depending on who they get to test it.

Clean up the devfs API for now, and start working on what might
eventually replace it- Whether that's devfs2 or a purely userspace
implementation or something new and wacky is up to whoever writes it.

Rather than saying "Devfs sucks, and we can't do anything about it other
than fix it's more minor problems because we're in feature freeze", we
should be saying "devfs sucks; we're a little late for feature freeze,
so let's clean up what we can and work on something much better for the
next time around."

Devfs as it is now is a nice idea, to me. It's an extremely organized
/dev which is also an accurate portrayal of what's available to use on a
particular machine. I'd hate to see it just ripped out entirely, and
while they've never affected me, I've heard of many issues with it. I'd
like to hear what ideas people may have /for/ a future replacement.

-- 
< There is a light that shines on the frontier >
<   And maybe someday, We're gonna be there.   >
<    Rando Christensen / rando@babblica.net    >

  parent reply	other threads:[~2002-11-12 11:17 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   ` devfs Alexander Viro
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         ` Rando Christensen [this message]
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=20021112042408.02d2e3e3.rando@babblica.net \
    --to=rando@babblica.net \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spyro@f2s.com \
    --cc=viro@math.psu.edu \
    --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

all inboxes | Powered by JetHome®