From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Use /proc/ide/hdx files from udev [PATCH]
Date: Mon, 05 Jan 2004 22:29:28 +0000 [thread overview]
Message-ID: <20040105222927.GD30464@kroah.com> (raw)
In-Reply-To: <1073154810.6053.15.camel@bigboy>
On Mon, Jan 05, 2004 at 11:13:33PM +0100, Kay Sievers wrote:
> On Sun, Jan 04, 2004 at 12:55:28AM -0800, Greg KH wrote:
> > On Sat, Jan 03, 2004 at 01:33:31PM -0500, Raf D'Halleweyn wrote:
> > >
> > > The attached patch makes it possible to use files in the /proc/ide/hdx
> > > directory in LABEL rules, e.g.:
> > >
> > > LABEL, BUS="ide", SYSFS_media="cdrom", NAME="cdrom"
> >
> > But your patch doesn't do this for only ide devices, does it?
> >
> > > I expect that those proc files are going to be moved into sysfs and at
> > > that time, this patch will not be useful anymore.
>
>
> For now we may simply use a CALLOUT rule:
>
> CALLOUT, BUS="ide", PROGRAM="/bin/cat /proc/ide/%k/media", ID="cdrom", NAME="%k", SYMLINK="cdrom"
Ah, sweet, I like that rule. I think that just about sums up how
flexible udev is right now :)
I'll go add it to the default udev.rules file...
thanks,
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2004-01-05 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 18:33 Use /proc/ide/hdx files from udev [PATCH] Raf D'Halleweyn
2004-01-04 8:55 ` Greg KH
2004-01-05 22:13 ` Kay Sievers
2004-01-05 22:29 ` Greg KH [this message]
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=20040105222927.GD30464@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).