From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and the kernel's idea of a device
Date: Tue, 06 Apr 2004 20:30:22 +0000 [thread overview]
Message-ID: <20040406203022.GB8373@kroah.com> (raw)
In-Reply-To: <20040406192223.GA4853@nostromo.devel.redhat.com>
On Tue, Apr 06, 2004 at 04:10:24PM -0400, Bill Nottingham wrote:
> Greg KH (greg@kroah.com) said:
> > > - it can print out the major/minor
> >
> > Ick. That just doesn't make much sense.
>
> And yet, there are drivers that do that.
Which ones? I'd be glad to go fix that up.
> > As it is very simple
> > to translate from the kernel device name to the real /dev name at any
> > point in time using udevinfo, why is that not sufficient?
>
> Requires integrating udevinfo into various random userland apps...
> it's certainly doable, but it just doesn't seem very clean.
I agree, but what random userland apps are you talking about? Can you
think of a cleaner suggestion?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-04-06 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 19:22 udev and the kernel's idea of a device Bill Nottingham
2004-04-06 19:59 ` Greg KH
2004-04-06 20:10 ` Bill Nottingham
2004-04-06 20:30 ` Greg KH [this message]
2004-04-06 20:49 ` Bill Nottingham
2004-04-06 21:06 ` Greg KH
2004-04-06 21:14 ` Bill Nottingham
2004-04-06 21:43 ` Daniel Stekloff
2004-04-08 21:03 ` Greg KH
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=20040406203022.GB8373@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).