From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules.devfs + symlinks & a question
Date: Wed, 10 Dec 2003 12:31:36 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107105984829475@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107105799027697@msgid-missing>
On Wednesday 10 December 2003 13:01, Svetoslav Slavtchev wrote:
> let's start with the question
>
> i'm still missing a number of devices, how should i get them in /udev ?
> these are the raw , pty and pts devices
These, and more, currently lack class device support in the kernel.
As an example, you can look at Greg's tty class in drivers/char/tty_io.c
AFAICS, pty and pts devices need not be created if you use the /dev/pts
file system, although you could register them as tty class devices.
Aside from raw devices, we need at least support for tape and misc devices
(both have been discussed before here) and there are probable others.
> and there is a spelling issue either in devfs or -D :-)
> according to devfs hole disks are named "disc"
> according to -D they are named "disk"
> to me the second is more correct, but as it was added just for devfs
> compatibility it should be probably changed to what devfs use "disc"
When I wrote the patch for %D, I had only dasd devices in mind, which
actually used 'disk', not 'disc' in devfs. Maybe we need both variants,
e.g. %d for disc and %D for disk?
Which drivers are using the disc name, is it only ide or are there others?
Arnd <><
-------------------------------------------------------
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-10 12:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 12:01 udev.rules.devfs + symlinks & a question Svetoslav Slavtchev
2003-12-10 12:31 ` Arnd Bergmann [this message]
2003-12-10 13:17 ` Svetoslav Slavtchev
2003-12-10 17:00 ` Marco d'Itri
2003-12-10 22:07 ` Greg KH
2003-12-10 22:45 ` Svetoslav Slavtchev
2003-12-10 23:14 ` Greg KH
2003-12-10 23:19 ` Svetoslav Slavtchev
2003-12-11 0:17 ` Greg KH
2003-12-11 1:14 ` Svetoslav Slavtchev
2003-12-11 1:31 ` Svetoslav Slavtchev
2003-12-12 22:17 ` Svetoslav Slavtchev
2003-12-12 23:42 ` Greg KH
2003-12-12 23:43 ` Greg KH
2003-12-12 23:45 ` Greg KH
2003-12-13 0:02 ` Svetoslav Slavtchev
2003-12-13 0:06 ` Greg KH
2003-12-13 0:39 ` Svetoslav Slavtchev
2003-12-13 0:57 ` Greg KH
2003-12-13 0:58 ` Svetoslav Slavtchev
2003-12-13 1:17 ` Svetoslav Slavtchev
2003-12-13 15:47 ` Kay Sievers
2003-12-13 21:33 ` Svetoslav Slavtchev
2003-12-14 3:34 ` Kay Sievers
2003-12-15 22:55 ` Greg KH
2003-12-15 22:56 ` Greg KH
2003-12-15 22:57 ` Greg KH
2003-12-17 20:16 ` Svetoslav Slavtchev
2003-12-17 20:39 ` Svetoslav Slavtchev
2003-12-17 21:13 ` Svetoslav Slavtchev
2003-12-17 22:24 ` Greg KH
2003-12-17 22:25 ` Greg KH
2003-12-17 22:27 ` Greg KH
2003-12-17 22:28 ` Greg KH
2003-12-17 22:29 ` Greg KH
2003-12-17 22:30 ` Greg KH
2003-12-17 22:51 ` Marco d'Itri
2003-12-17 22:55 ` Svetoslav Slavtchev
2003-12-17 22:59 ` Svetoslav Slavtchev
2003-12-17 23:04 ` Svetoslav Slavtchev
2003-12-17 23:06 ` Svetoslav Slavtchev
2003-12-17 23:08 ` 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=marc-linux-hotplug-107105984829475@msgid-missing \
--to=arnd@arndb.de \
--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).