From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - that famouse obsolete %e option
Date: Mon, 31 Jul 2006 17:40:44 +0000 [thread overview]
Message-ID: <1154367644.7116.21.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <d5a13c80607310524o73ae4a68ib58f0311176af6ee@mail.gmail.com>
On Mon, 2006-07-31 at 14:24 +0200, VMiklos wrote:
> hi,
>
> %e option in udev is obsolete for a long time since, it's broken -
> correct me if i'm wrong. that sounds a bit weird to me: if something
> is broken then why not fixing it instead of marking it obsolete with
> the comment "don't use it"?
>
> so, my question is that if one should not use it, what are the
> alternatives? except the trivial "writing external an shell script
> that would do exactly the same as the current %e code does" one -
> which sounds a bit hackish to me, not a real solution.
It just conceptually can't work, and only creates silly and useless
random numbers without any useful meaning. Udev will not provide the
infrastructure for such a silly thing. The days where hardware didn't
change during runtime, when you used this simple type of enumeration, is
long over. And these days will never come back.
Also see here:
http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;fúQ#l48
Kay
-------------------------------------------------------------------------
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-07-31 17:40 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 [this message]
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
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=1154367644.7116.21.camel@pim.off.vrfy.org \
--to=kay.sievers@vrfy.org \
--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).