From: Patrick Mansfield <patmans@us.ibm.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-hotplug-devel@lists.sourceforge.net, dm-devel@redhat.com
Subject: Re: udev user specified or human readable /dev names
Date: Wed, 02 Nov 2005 15:30:18 +0000 [thread overview]
Message-ID: <20051102153018.GA30686@us.ibm.com> (raw)
In-Reply-To: <20051102025345.GA19174@vrfy.org>
On Wed, Nov 02, 2005 at 03:53:45AM +0100, Kay Sievers wrote:
> Sure, that may be easier.
> But such a tool is only useful if the devices are already present on the
> system, right? Then you can read all current available ID_* variables from
> the udev database and compose a nice rule from it. :)
Yes looks like that can work (again I *was* thinking symlinks, and not
env variables) .
> > And is there a way to rename or add /dev entries without removing and
> > adding back a device?
>
> You can run udevstart again, if its not configured to do some weird
> stuff.
That is rather slow, and didn't removing links (like a rename would want).
> The current devel kernel has a "uevent" file, which triggers the
> hotplug event again, this could be used to create additional configured
> links.
>
> Also:
> ACTIONd DEVPATH=/block/sdm /sbin/udev block
> would do it.
Those don't remove links either.
> Or do you mean adding a link temporarily, so that it get tracked and
> removed when the device goes away?
No.
Thanks,
-- Patrick Mansfield
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.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:[~2005-11-02 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 22:53 udev user specified or human readable /dev names Patrick Mansfield
2005-11-02 0:05 ` Kay Sievers
2005-11-02 0:35 ` Patrick Mansfield
2005-11-02 1:06 ` Kay Sievers
2005-11-02 2:01 ` Patrick Mansfield
2005-11-02 2:53 ` Kay Sievers
2005-11-02 15:30 ` Patrick Mansfield [this message]
2005-11-02 23:49 ` Kay Sievers
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=20051102153018.GA30686@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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).