From: Mike Bell <kernel@mikebell.org>
To: Greg KH <greg@kroah.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Tue, 28 Jun 2005 02:08:53 -0700 [thread overview]
Message-ID: <20050628090852.GA966@mikebell.org> (raw)
In-Reply-To: <20050628074015.GA3577@kroah.com>
On Tue, Jun 28, 2005 at 12:40:15AM -0700, Greg KH wrote:
> > 1) Predictable, canonical device names are a Good Thing.
>
> And impossible for the kernel to generate given hotpluggable devices.
Bull. It's clear I'm talking about per-subsystem, not having individual
devices show up with the same name each time. Or are you suggesting that
hotplug might somehow turn my keyboard into a hard drive?
> I don't accept it, and neither does anyone else.
So then explain this to me, I've got a GUI sound player, on first
invocation it displays a list of sound cards installed on the system,
allows the user to select one, and then plays the sound file. How is it
supposed to do that if the device nodes for sound card 0 could be named
anything? I can get a list of sound cards from /proc/asound or
/sys/class/sound, but unless the sound card device nodes are predictably
named there's no way to find them short of searching every node in /dev.
next prev parent reply other threads:[~2005-06-28 9:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 8:18 [ANNOUNCE] ndevfs - a "nano" devfs Greg KH
2005-06-24 12:23 ` Michael Tokarev
2005-06-24 15:16 ` Greg KH
2005-06-24 15:40 ` Michael Tokarev
2005-06-24 16:26 ` Greg KH
2005-06-24 14:32 ` Bill Gatliff
2005-06-24 15:17 ` Steven Rostedt
2005-06-24 15:20 ` Greg KH
2005-06-24 17:10 ` Michael Tokarev
2005-06-24 17:10 ` Bill Gatliff
2005-06-28 7:40 ` Greg KH
2005-06-24 19:05 ` Mike Bell
2005-06-24 21:55 ` J.A. Magallon
2005-06-24 19:22 ` Alexey Dobriyan
2005-06-25 0:57 ` Kyle Moffett
2005-06-25 7:37 ` Denis Vlasenko
2005-06-28 7:41 ` Greg KH
2005-06-28 19:56 ` Tom Rini
2005-06-28 21:08 ` Olaf Hering
2005-06-28 21:25 ` Tom Rini
2005-06-28 22:08 ` Michael Tokarev
2005-06-28 22:23 ` Tom Rini
2005-06-25 22:15 ` Matt Mackall
2005-06-25 23:43 ` Greg KH
2005-06-26 8:23 ` Russell King
2005-06-28 3:36 ` Greg KH
2005-06-27 7:19 ` Mike Bell
2005-06-27 22:35 ` Dmitry Torokhov
2005-06-27 23:26 ` Mike Bell
2005-06-28 7:40 ` Greg KH
2005-06-28 9:08 ` Mike Bell [this message]
2005-06-28 9:21 ` Arjan van de Ven
2005-06-28 9:40 ` Mike Bell
2005-06-28 21:49 ` Jim Crilly
2005-06-28 22:23 ` Mike Bell
2005-06-28 23:43 ` Jim Crilly
2005-06-29 0:12 ` Mike Bell
2005-06-29 0:39 ` David Lang
2005-06-29 0:53 ` Mike Bell
2005-06-28 12:00 ` Oliver Neukum
2005-06-28 20:08 ` Greg KH
2005-06-29 6:41 ` Oliver Neukum
2005-06-29 16:06 ` Greg KH
2005-06-29 16:22 ` Oliver Neukum
[not found] ` <200506270819.20108.arnd@arndb.de>
2005-06-28 3:46 ` Greg KH
[not found] <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
2005-06-24 15:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 15:32 tvrtko.ursulin
2005-06-24 16:27 ` Greg KH
2005-06-27 15:21 Adam J. Richter
2005-06-27 23:27 ` J.A. Magallon
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=20050628090852.GA966@mikebell.org \
--to=kernel@mikebell.org \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--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