From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules.devfs + symlinks & a question
Date: Wed, 10 Dec 2003 22:45:24 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107109637413756@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107105799027697@msgid-missing>
> On Wed, Dec 10, 2003 at 01:01:37PM +0100, Svetoslav Slavtchev wrote:
> > Hi,
> >
> > udev_bk is looking really great :-)
> > great work , isn't it time for a 0.009 or 0.1 release?
>
> What's with the '.'? 009 will be the next release, hopefully soon, I'm
> waiting on some stuff from the libsysfs authors...
oops, sorry
> > 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
>
> pty and pts are handled by the devpts filesystem.
ok
> For raw devices I have a patch floating around in my kernel tree that
> needs to be looked at a bunch. Care to test it out?
yep, not that i use them much,but i'll at least make some progress on the
udev.rules
and i may try to push them to the mandrake kernel package, which will
probably
return more responce :-)
> > also does anyone have links to the patches that add sound support ?
>
> Again, I have patches, but don't think they are ready for prime time.
same as previous comment, but i do listen music all the time :-)
>I want to get these out soon, need to stop answering dumb devfs vs udev
> questions on lkml...
right, why not just upload all the patches you know of or have handy,
to kernel.org/.../hotplug/ and add a big fat note they are experimental
/* may be experimental at what level too, (applies, boots, runs, oopses) */
and add a small coment in the FAQ
this will probably spare you some time answering dumb question
/* and would spare some time google-ing for others too :-) */
> > attached is my udev.rules,
> > which brings me directory structure almost(completely?) equivelent
> > to the devfs one, except that some devices are still missing
> > ( tree /udev = tree-udev.txt, missing entries from /dev = tree-dev.txt
> )
> >
> > and i'm not sure how can i distinguish a cd drive from a hard drive
>
> For scsi cdroms it's easy, look at the type file in sysfs. For ide
> cdroms, code needs to be added to the kernel to export that information
> for you to determine this.
hm, i was browsing the thread a while ago, but didnt get it fully
there were some issues with using 2 rules for one device,
do hard disks/ tapes/... also has such a type file ?
do only scsi ones have it ?
i was thinking of
[address] type="hd" .... name1
[address] type="cd" ....name2
> > 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"
>
> Good point, I'll go change that.
wait a bit :-)
it seems that some special devices do use "disk",
while scsi/ide hard's use "disc"
/* devfs has THE naming policy, doesn't it?:) */
I think Arnd is looking into the issue
best,
svetljo
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
-------------------------------------------------------
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 22:45 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
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 [this message]
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-107109637413756@msgid-missing \
--to=svetljo@gmx.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).