From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - that famouse obsolete %e option
Date: Tue, 01 Aug 2006 16:35:58 +0000 [thread overview]
Message-ID: <200608012035.59026.arvidjaar@mail.ru> (raw)
In-Reply-To: <d5a13c80607310524o73ae4a68ib58f0311176af6ee@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 01 August 2006 20:17, VMiklos wrote:
> 2006/8/1, Kay Sievers <kay.sievers@vrfy.org>:
> > How would you manage the numbers to stick with a particular device
> > across reboots and reconfiguration? I can't imagine a "small tool" doing
> > that job. It is entirely device class specific how to to that, and I
> > don't think it can be solved at a generic level.
>
> i'm thinking of cd/dvd symlinks at the moment. an example: i have a
> cdrw+dvd (hdc) drive and a dvdrw drive (sr0). using cdrom_id, it's
> possible to create the following nodes: cdrom-hdc, cdrw-hdc, dvd-hdc,
> (same for sr0) and dvdrw-sr0. then the "tool" would create
> cdrom->cdrom-hdc, cdrom1->cdrom-sr0, ..., dvdrw->dvdrw-sr0 symlinks.
> and yes, across the reboots hdc would _always_ become cdrom, and sr0
> would _always_ become cdrom1
>
Most distributions already have rules that do something similar - it is just
that having support for this _inside_ of udev core does not make sense.
# udev persistent rules for block subsystem
# Generated by Mandriva udev rules
# See /etc/udev/rules.d/62-create_persistent.rules
SUBSYSTEM="block", ACTION="add",
ENV{ID_PATH}="pci-0000:00:04.0-scsi-1:0:0:0", SYMLINK+="cdrom cdrom0 dvd
dvd0", ENV{MDV_CONFIGURED}="yes"
SUBSYSTEM="block", ACTION="add", ENV{ID_PATH}="pci-0000:00:04.0-ide-1:0",
SYMLINK+="cdrom1 dvd1", ENV{MDV_CONFIGURED}="yes"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD4DBQFEz4LuR6LMutpd94wRArglAJ9XjMNVwL6sL4wqnZGcmJhOcfShFwCYmjma
iXp1lRl2Gufs60lQbiBTBQ=
=O+R5
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2006-08-01 16:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 12:24 udev - that famouse obsolete %e option VMiklos
2006-07-31 12:45 ` Alexander E. Patrakov
2006-07-31 12:51 ` Marco d'Itri
2006-07-31 12:57 ` Alexander E. Patrakov
2006-07-31 14:48 ` Marco d'Itri
2006-07-31 17:40 ` Kay Sievers
2006-07-31 23:45 ` VMiklos
2006-08-01 10:27 ` VMiklos
2006-08-01 12:02 ` Olivier Blin
2006-08-01 12:27 ` Kay Sievers
2006-08-01 16:17 ` VMiklos
2006-08-01 16:35 ` Andrey Borzenkov [this message]
2006-08-01 16:46 ` Bryan Kadzban
2006-08-01 16:47 ` Kay Sievers
2006-08-01 18:16 ` VMiklos
2006-08-01 18:28 ` Kay Sievers
2006-08-01 18:57 ` VMiklos
2006-08-02 12:06 ` VMiklos
2006-08-02 12:54 ` Alexander E. Patrakov
2006-08-02 20:28 ` VMiklos
2006-08-07 10:32 ` VMiklos
2006-08-11 10:18 ` VMiklos
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=200608012035.59026.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).