From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: scripts for persistent names support
Date: Sun, 03 Sep 2006 03:16:06 +0000 [thread overview]
Message-ID: <20060903031606.GA3399@vrfy.org> (raw)
In-Reply-To: <20060902090653.GA4424@wonderland.linux.it>
On Sat, Sep 02, 2006 at 11:06:53AM +0200, Marco d'Itri wrote:
> I implemented both the "try again later" and "use a temporary file now"
> methods to work around the read-only root problem.
> Removing the part of the code you do not need is trivial, and I expect
> that everybody will only use the scripts as examples anyway.
Very nice. Thanks for doing this.
A few comments:
> RULES_FILE="/etc/udev/rules.d/z25_persistent-cd.rules"
>
> . /lib/udev/hotplug.functions
Can we name that file udev.functions?
> device_description() {
> local bus=$(sysreadlink device/bus)
> bus=${bus##*/}
We should not use the 'device' link. It's only a comment, but it's
a nice information. Can't we read this information with udev rules
and export it as an environment variable or pass it as an argument.
> abort_if_run_early() {
> return # DISABLED
> # copy the rules generated before / was mounted read-write
> for file in /dev/.udev/tmp-rules--*; do
> dest=${file##*tmp-rules--}
Can't we check with the rule writing script itself, if there are
already created temporary rules, and if yes, we just copy them over?
That way, the failed-event-replay would just take care of copying for
systems who use the --retry-failed?
> # ignore interfaces without a driver link
> ENV{DRIVER}!="?*", GOTO="persistent_net_generator_end"
Does this work? A network device event should never have the DRIVER
property set, as it belongs to a parent device.
Thanks again,
Kay
-------------------------------------------------------------------------
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-09-03 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 9:06 scripts for persistent names support Marco d'Itri
2006-09-03 3:16 ` Kay Sievers [this message]
2006-09-03 10:10 ` Marco d'Itri
2006-09-03 12:48 ` 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=20060903031606.GA3399@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).