From: Tom Horsley <tom.horsley@att.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: What does last_rule really mean?
Date: Sun, 25 Oct 2009 19:05:31 +0000 [thread overview]
Message-ID: <20091025150531.65b407b3@zooty> (raw)
In-Reply-To: <102520090145.1929.4AE3ADC2000828BF0000078922243322829B0A02D29B9B0EBF970A049C9D0108D203019B@att.net>
On Mon, 26 Oct 2009 02:51:03 +0900
Kay Sievers wrote:
> On Sun, Oct 25, 2009 at 11:20, David Zeuthen <david@fubar.dk> wrote:
>
> > (For the record, the last_rule directive in udev is really dangerous as
> > it may have unintended consequences hiding devices like this from
> > system-level software depending on it - last time I talked to Kay he
> > mentioned that it might be nice to remove it since there's really no
> > reason to hand out rope like that.)
>
> Yeah, let's remove that thing. It causes too much trouble and is just
> an indication that something needs to be fixed differently.
Or re-define it sensibly. One of the potential definitions I thought
about when trying to decide what it might actually mean was: "Save this
rule up and process it at the end of all the other rules". Then it
just becomes a way to get your rule to the end without having to
worry about some distro coming along and trumping your 99-zzz.rules
file with a 99-~~~.rules file :-).
next prev parent reply other threads:[~2009-10-25 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 1:45 What does last_rule really mean? Tom Horsley
2009-10-25 2:20 ` David Zeuthen
2009-10-25 14:08 ` Tom Horsley
2009-10-25 17:51 ` Kay Sievers
2009-10-25 19:05 ` Tom Horsley [this message]
2009-10-28 10:52 ` 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=20091025150531.65b407b3@zooty \
--to=tom.horsley@att.net \
--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).