From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: CD Symlinks Solution Idea
Date: Sun, 21 May 2006 04:01:51 +0000 [thread overview]
Message-ID: <446FE62F.40408@ums.usu.ru> (raw)
In-Reply-To: <44677DD3.80801@jg555.com>
juuso.alasuutari@tamperelainen.org wrote:
> I'm also working on a symlink naming helper (based on
> Jim Gifford's script),
Please don't. It is a 1:1 reimplementation of the old "%e" idea that was dropped
for a good reason: it doesn't work consistently.
I.e., sometimes you will get /dev/cdrom -> sr0 and /dev/cdrom1 -> sr1, and
sometimes the other way round. That happens because udev processes uevents in
parallel, and thus in random order (and this can't be changed). In order for the
symlinks to be persistent, some on-disk database must be present, and that's
what Marco's script does (but it doesn't work with more than two CD-ROMs due to
an easily-fixable bug - or is that already fixed?).
--
Alexander E. Patrakov
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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-05-21 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 18:58 CD Symlinks Solution Idea Jim Gifford
2006-05-14 19:11 ` Jim Gifford
2006-05-15 0:52 ` Jim Gifford
2006-05-16 8:23 ` juuso.alasuutari
2006-05-16 15:30 ` Marco d'Itri
2006-05-19 16:03 ` Harald Hoyer
2006-05-21 1:00 ` juuso.alasuutari
2006-05-21 4:01 ` Alexander E. Patrakov [this message]
2006-05-22 16:20 ` Jim Gifford
2006-05-22 17:21 ` Darren Salt
2006-06-12 0:13 ` juuso.alasuutari
2006-06-12 0:17 ` juuso.alasuutari
2006-06-12 7:18 ` Marco d'Itri
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=446FE62F.40408@ums.usu.ru \
--to=patrakov@ums.usu.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).