From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: WAIT_FOR_SYSFS ignores further conditions
Date: Tue, 31 Jan 2006 14:30:48 +0000 [thread overview]
Message-ID: <20060131143048.GA11369@vrfy.org> (raw)
In-Reply-To: <200601291500.15527.arvidjaar@mail.ru>
On Mon, Jan 30, 2006 at 07:37:00PM +0300, Andrey Borzenkov wrote:
> On Sunday 29 January 2006 15:00, Andrey Borzenkov wrote:
> > Is it intentional? It looks rather like copy'n'paste slip. Patch attached.
>
> This actually fixed a real bug here (every rule having WAIT_FOR_SYSFS was
> executed, not the one with mathing SYSFS value); so if there is something
> wrong with this patch I appreciate if someone explains what.
Correct, it doesn't work the way you use it and it should be fixed. I'll go
look into this later this week.
(WAIT_FOR_SYSFS is a hack, that should be used only in the first rules file
udev finds and better not do any other function than ensuring that all
the later rules can be sure that a file will be there or will not appear
at all. Just don't use it in "real" rules, only in separate fixup rules at
the beginning of the rule processing.)
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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-01-31 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 12:00 WAIT_FOR_SYSFS ignores further conditions Andrey Borzenkov
2006-01-30 16:37 ` Andrey Borzenkov
2006-01-31 14:30 ` Kay Sievers [this message]
2006-02-03 13:05 ` 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=20060131143048.GA11369@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).