From: Bill Nottingham <notting@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and the kernel's idea of a device
Date: Tue, 06 Apr 2004 21:14:33 +0000 [thread overview]
Message-ID: <20040406211432.GA15620@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040406192223.GA4853@nostromo.devel.redhat.com>
Greg KH (greg@kroah.com) said:
> > Off the top of my head, iostat, cdrom capability checkers, fbset
> > and friends, etc. But, in the long run, see below.
>
> But those apps want to know the /dev node, right?
Well, they want to know the dev node, and they use the device
as a key to get auxillary information. For example, the framebuffer
stuff has some limited auxillary information in /proc/fb, there's
random CD-ROM info in /proc/sys/dev/cdrom/info, etc.
> back from the kernel with the kernel device name (well, I don't know
> what iostat uses, but I think the later version use sysfs...).
The version I have here still reads /proc/diskstats. Perhaps
there is a newer one.
Bill
-------------------------------------------------------
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 21:14 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
2004-04-06 20:49 ` Bill Nottingham
2004-04-06 21:06 ` Greg KH
2004-04-06 21:14 ` Bill Nottingham [this message]
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=20040406211432.GA15620@devserv.devel.redhat.com \
--to=notting@redhat.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).