From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] compatibility symlinks for udev
Date: Mon, 06 Sep 2004 15:45:50 +0000 [thread overview]
Message-ID: <1094485551.3319.42.camel@localhost.localdomain> (raw)
In-Reply-To: <1094481997.4727.14.camel@localhost.localdomain>
On Mon, 2004-09-06 at 16:46 +0200, David Zeuthen wrote:
Nice, I like it. It's a easy way to group device nodes of the same type,
but coming from different kernel subsystems.
> Here's a patch against udev-030 that can help create compatibility
> symlinks like /dev/cdrom, /dev/cdrom1 etc. The patch introduces a new
> substitution type %C (for Compatibility) that can be used as follows
I suggest using %e for enumeration here, cause "compatibility" can
easily be misunderstood.
> Together with a simple helper script (that can be removed as soon as IDE
> exports the type in sysfs; alternatively this is trivial to write in C
> for e.g. early boot)
>
> #!/bin/sh
> TYPE=`cat /proc/ide/$1/media`
> if test "$TYPE" = "cdrom"; then
> echo -n cdrom
> exit 0
> elif test "$TYPE" = "floppy"; then
> echo -n floppy
> exit 0
> fi
> exit 1
I will look into it, if it's easy to add to sysfs.
And we need a few lines added to the man page at udev.8.in :)
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&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:[~2004-09-06 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 14:46 [patch] compatibility symlinks for udev David Zeuthen
2004-09-06 15:45 ` Kay Sievers [this message]
2004-09-07 11:19 ` David Zeuthen
2004-09-10 20:09 ` Greg KH
2004-09-14 17:50 ` Kay Sievers
2004-09-14 20:50 ` 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=1094485551.3319.42.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).