From: Greg KH <greg@kroah.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
linux-kernel@vger.kernel.org,
Andreas Jellinghaus <aj@dungeon.inka.de>
Subject: Re: devfs vs. udev
Date: Tue, 7 Oct 2003 11:10:41 -0700 [thread overview]
Message-ID: <20031007181041.GI1956@kroah.com> (raw)
In-Reply-To: <20031007175817.GB1125@carfax.org.uk>
On Tue, Oct 07, 2003 at 06:58:17PM +0100, Hugo Mills wrote:
> On Tue, Oct 07, 2003 at 10:49:28AM -0700, Greg KH wrote:
> > On Tue, Oct 07, 2003 at 05:54:04PM +0100, Hugo Mills wrote:
> > >
> > > Surely udev needs the ability to make more than one device node or
> > > symlink when a device is plugged in anyway, so I just see this as an
> > > issue of writing the appropriate default configuration files.
> >
> > More than one device node per device? Why would you want that?
>
> OK, more than one actual node per device (i.e. per major:minor
> pair) may not necessarily be required, but in devfs there are, for
> example device nodes created in /dev/scsi/host0/bus0/device0/lun0/...
> etc, and links to those device nodes created in /dev/discs/disc0/...
> It can occasionally be useful to have the two distinct namespaces
> available.
Yes, symlinks are on the TODO list, as lots of people want them
/dev/cdrom, /dev/pilot, etc.
thanks,
greg k-h
next prev parent reply other threads:[~2003-10-07 18:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 12:38 devfs vs. udev Måns Rullgård
2003-10-07 13:41 ` Andreas Jellinghaus
2003-10-07 14:07 ` Måns Rullgård
2003-10-07 14:23 ` Robert L. Harris
2003-10-07 14:29 ` Måns Rullgård
2003-10-07 16:06 ` Andreas Jellinghaus
2003-10-07 16:11 ` Måns Rullgård
2003-10-07 16:14 ` Robert L. Harris
2003-10-07 16:54 ` Hugo Mills
2003-10-07 17:19 ` Måns Rullgård
2003-10-07 17:47 ` Greg KH
2003-10-07 17:49 ` Greg KH
2003-10-07 17:58 ` Hugo Mills
2003-10-07 18:10 ` Greg KH [this message]
2003-10-09 13:43 ` Ian Kent
2003-10-09 20:54 ` Greg KH
2003-10-07 17:55 ` Greg KH
2003-10-14 13:51 ` Ian Kent
2003-10-17 4:34 ` Greg KH
2003-10-07 17:54 ` Greg KH
2003-10-07 14:01 ` tabris
2003-10-07 17:53 ` Greg KH
2003-10-07 18:24 ` viro
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 11:51 DevFS " Bradley W. Allen
2003-12-23 12:06 ` Duncan Sands
2003-12-23 12:12 ` Xavier Bestel
2003-12-23 12:37 ` Marcelo Bezerra
2003-12-23 13:02 ` Ed Tomlinson
2003-12-25 12:11 ` Kai Henningsen
2003-12-23 14:30 ` Paul Dickson
2003-12-23 23:23 ` Bradley W. Allen
2003-12-23 23:46 ` Brett
2003-12-24 4:01 ` alex.g.goddard.1
2003-12-23 16:19 ` Ian Kent
2003-12-23 17:34 ` Mark Mielke
2003-12-23 22:02 ` Greg KH
2003-12-23 22:13 ` Tomasz Torcz
2003-12-24 0:45 ` Martin Schlemmer
2003-12-24 1:07 ` Greg KH
2003-12-24 1:28 ` Martin Schlemmer
2003-12-23 21:59 ` Greg KH
2003-12-24 1:52 ` Ian Kent
2003-12-24 2:03 ` Rob Love
2003-12-24 2:21 ` Ian Kent
2003-12-24 2:22 ` Rob Love
2003-12-24 2:32 ` Stan Bubrouski
2003-12-24 2:39 ` Rob Love
2003-12-24 2:38 ` Andrew Morton
2003-12-24 3:41 ` viro
2003-12-24 11:33 ` Witukind
2003-12-24 4:13 ` Rusty Russell
2003-12-24 4:38 ` Stan Bubrouski
2003-12-24 11:15 ` Xavier Bestel
2003-12-24 13:44 ` Ian Soboroff
2003-12-24 14:17 ` Xavier Bestel
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=20031007181041.GI1956@kroah.com \
--to=greg@kroah.com \
--cc=aj@dungeon.inka.de \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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