From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] compatibility symlinks for udev
Date: Fri, 10 Sep 2004 20:09:07 +0000 [thread overview]
Message-ID: <20040910200907.GA19503@kroah.com> (raw)
In-Reply-To: <1094481997.4727.14.camel@localhost.localdomain>
On Tue, Sep 07, 2004 at 01:19:34PM +0200, David Zeuthen wrote:
> On Mon, 2004-09-06 at 17:45 +0200, Kay Sievers wrote:
> > 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.
> >
>
> That's a good way of putting it, yeah.
>
> > > 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.
> >
>
> Good point, I've changed that.
>
> > And we need a few lines added to the man page at udev.8.in :)
> >
>
> Done. I've also added an example.
>
> Also, Kay pointed out offlist that the rules can be written to not
> require a shell script; this actually works
>
> KERNEL="sr*", NAME="%k", SYMLINK="cdrom%e"
> KERNEL="scd*", NAME="%k", SYMLINK="cdrom%e"
> KERNEL="pcd*", NAME="%k", SYMLINK="cdrom%e"
> KERNEL="hd[a-z]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom", NAME="\%k", SYMLINK="cdrom%e"
> KERNEL="fd[0-9]", NAME="%k", SYMLINK="floppy%e"
> KERNEL="hd[a-z]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="floppy", NAME=\"%k", SYMLINK="floppy%e"
>
> New patch is attached.
Nice, I've applied this.
How about sending a patch for the test/udev-test.pl script that adds a
test for this new paramater, so we make sure to not break it in the
future.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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-10 20:09 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
2004-09-07 11:19 ` David Zeuthen
2004-09-10 20:09 ` Greg KH [this message]
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=20040910200907.GA19503@kroah.com \
--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).