From: Tupshin Harper <tupshin@tupshin.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: initial udev foray...successes and failures...
Date: Tue, 23 Dec 2003 01:05:15 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107214166019858@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107173885409205@msgid-missing>
Greg KH wrote:
>On Mon, Dec 22, 2003 at 02:41:44PM -0800, Tupshin Harper wrote:
>
>
>>Can't seem to find it in the archives of either list ...maybe I'm just
>>blind...can you point me at it?
>>
>>
>
>ok, will post them over again to lkml and linux-hotplug-devel in a
>minute.
>
>
Thanks.
>>Yup...lots o stuf in /sys/class/tty: tty0-tty63 directories all
>>containing a "dev" file. tty0 (for example) contains dev with contents 4:0
>>
>>
>
>Hm, so if you run the 'test.all' script in the test directory with the
>'add' paramater, does it create the tty nodes? Check to see if debian
>has a initscript that properly catches all of the dev nodes in sysfs
>(look at the one in the udev release, or the test.all script for an
>example of how to do this properly without having to know what kinds of
>devices are in sysfs.)
>
>
>
Bug in debian's version...not present in stock udev-009.
>>Should there be one line for every conceivable IDE device?
>>
>>
>
>If you want to name them something different from the kernel name, yes.
>If not, the default kernel name will be used, which should work just
>like without devfs or udev.
>
>
What are your thoughts on the fact that this naming scheme limits you to
26 devices? 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?
-Tupshin
-------------------------------------------------------
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:05 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 [this message]
2003-12-23 1:09 ` Greg KH
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-107214166019858@msgid-missing \
--to=tupshin@tupshin.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).