From: Andries Brouwer <aebr@win.tue.nl>
To: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] /proc/devices for block devices
Date: Tue, 13 May 2003 11:47:33 +0200 [thread overview]
Message-ID: <20030513094733.GA28743@win.tue.nl> (raw)
In-Reply-To: <20030513083959.A20052@lst.de>
Christoph Hellwig wrote [on /proc/devices]:
> We could either
>
> (a) nuke it completly - if you need to find out the dev_t for your
> block driver with dynamic dev_t allocation you can look at
> /proc/partitions (portable to older kernels) or sysfs instead.
> (b) add some cludges
A grep on a random source tree shows:
A number of programs search /proc/devices for their favourite string,
find the device number and do mknod on it. Thus apmd for "apm_bios"
and IMonLinux for "imon" and hwcrypto for "paep" and "cryptonet".
Apart from for finding out dev_t, /proc/devices is used for
just checking that a certain driver exists in a certain kernel.
There are FAQs that tell people to check for "lp" or "sg"
or "sound" or "pcmcia" in /proc/devices.
The program anaconda checks /proc/devices for "fd" and for "pcmcia".
Various initscripts check for "usb", "sound", "sparcaudio".
SANE checks for "sg". Setserial checks for "ttyS".
Lomount and mount check for "loop".
LVM programs go the other way and use /proc/devices to find out
whether the device with given device number is of type "ide", "sd",
"nbd", "loop" etc.
Andries
prev parent reply other threads:[~2003-05-13 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 6:39 [RFC] /proc/devices for block devices Christoph Hellwig
2003-05-13 9:47 ` Andries Brouwer [this message]
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=20030513094733.GA28743@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).