All of lore.kernel.org
 help / color / mirror / Atom feed
From: insecure <insecure@mail.od.ua>
To: mru@users.sourceforge.net (Måns Rullgård), linux-kernel@vger.kernel.org
Subject: Re: devfs and udev
Date: Tue, 7 Oct 2003 21:28:09 +0300	[thread overview]
Message-ID: <200310072128.09666.insecure@mail.od.ua> (raw)
In-Reply-To: <yw1xllrxdvhh.fsf@users.sourceforge.net>

On Tuesday 07 October 2003 16:32, Måns Rullgård wrote:
> Bradley Chapman <kakadu_croc@yahoo.com> writes:
> > I think the two things which really prevented devfs from working were:
>
> It's always worked just fine for me.
>
> > 1. The namespace was too different from the original and required
> > additional configuration to maintain compatibility (devfsd and changes to
> > core /etc files.)
>
> Since when do Linux developers resist changes?
>
> > 2. Devfs was not immediately picked up my the major distros, which meant
> > that any moderate end-user who wanted to use it would have to be careful
> > when setting it up or risk massive core breakage due to the changed
> > device nodes (initscripts failing and the like).
>
> Had it been pushed harder, they probably would have done it.
>
> > I used it for a very long time, personally; it was a good idea, and it
> > had potential. If the namespace that had been used was the same flat
> > namespace as the original /dev, it would have probably taken off. As it
> > is, I think udev is the new way of doing this (I haven't used it yet).
>
> The different naming was one thing i liked about devfs.  Go read the
> archives from a couple of years ago, and see that the exact same
> arguments that were used to promote devfs, are now said to be bad
> things.  This sudden change is what I don't understand, and how the
> not-working udev is supposed to be able to replace devfs.

I am pro-devfs guy too.
If its internals are bad in some way or other, internals
may be fixed. But devfs userspace-visible interface was
not flawed (IMO).

What am I supposed to do, starting to use mknod again? Uggggh...
--
vda

  reply	other threads:[~2003-10-07 18:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 13:17 devfs and udev Bradley Chapman
2003-10-07 13:32 ` Måns Rullgård
2003-10-07 18:28   ` insecure [this message]
2003-10-07 18:44     ` viro
2003-10-07 19:41     ` Greg KH
2003-10-07 20:47       ` insecure
2003-10-07 20:52         ` Greg KH
2003-10-07 21:17           ` Chris Meadors
2003-10-07 21:48             ` Greg KH
2003-10-08  7:30               ` Andreas Jellinghaus
2003-10-08 12:07                 ` [2.6 patch] document that udev isn't yet ready Adrian Bunk
2003-10-07 21:27           ` devfs and udev Måns Rullgård
2003-10-07 21:37             ` Greg KH
2003-10-07 22:01               ` Måns Rullgård
2003-10-07 22:12                 ` Bryan O'Sullivan
2003-10-07 22:49                   ` Måns Rullgård
2003-10-07 23:27                     ` Greg KH
2003-10-08  0:03                       ` Måns Rullgård
2003-10-09 22:09               ` bill davidsen
2003-10-13 20:15                 ` Tom Rini
2003-10-07 20:57 ` David Lang
2003-10-08 22:34   ` H. Peter Anvin

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=200310072128.09666.insecure@mail.od.ua \
    --to=insecure@mail.od.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.