From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: initial udev foray...successes and failures...
Date: Tue, 23 Dec 2003 01:09:43 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107214182519986@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107173885409205@msgid-missing>
On Mon, Dec 22, 2003 at 05:05:15PM -0800, Tupshin Harper wrote:
> What are your thoughts on the fact that this naming scheme limits you to
> 26 devices?
Do you have more than 26 ide devices in your system? The scsi names can
handle many more than 26 devices, if you have a lot of disks I suggest
you use scsi instead :)
Anyway, that's not a udev issue, sorry.
> I recall that one reason for the devfs /dev/ide/... approach
> is that it didn't introduce any arbitrary device limitations. The
> structure of /sys/bus/ide doesn't impose this limitation. Where does the
> mapping from /sys/bus/ide/devices to /dev/hd? take place?
In your udev.rules file. The kernel calls the device hd? and then your
udev.rules file tries to map that to a /dev/ide/... mapping.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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:[~2003-12-23 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 9:13 initial udev foray...successes and failures Tupshin Harper
2003-12-22 20:39 ` Greg KH
2003-12-22 22:41 ` Tupshin Harper
2003-12-23 0:16 ` Greg KH
2003-12-23 1:05 ` Tupshin Harper
2003-12-23 1:09 ` Greg KH [this message]
2003-12-23 1:36 ` Tupshin Harper
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=marc-linux-hotplug-107214182519986@msgid-missing \
--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).