From: Greg KH <greg@kroah.com>
To: insecure <insecure@mail.od.ua>
Cc: linux-kernel@vger.kernel.org,
"Måns Rullgård" <mru@users.sourceforge.net>
Subject: Re: devfs and udev
Date: Tue, 7 Oct 2003 13:52:44 -0700 [thread overview]
Message-ID: <20031007205244.GA2978@kroah.com> (raw)
In-Reply-To: <200310072347.41749.insecure@mail.od.ua>
On Tue, Oct 07, 2003 at 11:47:41PM +0300, insecure wrote:
> On Tuesday 07 October 2003 22:41, Greg KH wrote:
> > On Tue, Oct 07, 2003 at 09:28:09PM +0300, insecure wrote:
> > > What am I supposed to do, starting to use mknod again? Uggggh...
> >
> > Provide me with a kernel name to devfs name mapping file so that I can
> > create a "devfs like" udev config file for people who happen to like
> > that naming scheme.
>
> It seems that we have a bit of misunderstanding here.
>
> I just don't want to go back to /dev being actually placed on
> real, on-disk fs.
>
> I won't mind if naming scheme will change as long
> as device names start with '/dev/' and appear
> there (semi-)automagically. That's what I call devfs.
> If udev can do this, I am all for that.
udev can do this. Is there some documentation that you read that has
suggested otherwise?
greg k-h
next prev parent reply other threads:[~2003-10-07 20:53 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
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 [this message]
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=20031007205244.GA2978@kroah.com \
--to=greg@kroah.com \
--cc=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.