From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Make rule generator switchable
Date: Fri, 27 Jul 2007 18:17:34 +0000 [thread overview]
Message-ID: <1185560254.23818.5.camel@lov.localdomain> (raw)
In-Reply-To: <200707271904.51531.zzam@gentoo.org>
On Fri, 2007-07-27 at 14:05 -0400, Bill Nottingham wrote:
> Kay Sievers (kay.sievers@vrfy.org) said:
> > How should todays boxes work without persistent network names? They
> > are as needed as LABEL, UUID, or /dev/disk/ for block devices. The old
> > way of having luck to get the same kernel device names across reboots,
> > just doesn't work today.
>
> The problem with the persistent net rule generator is when it's run - it
> is never run (at least under Fedora and related distributions) at a time
> when it's actually able to *write* rules.
Not a problem, it writes temporary rules to /dev/.udev, you are
expected to copy over, if you system does not allow to write to /etc at
that time.
Kay
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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:[~2007-07-27 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 17:04 Make rule generator switchable Matthias Schwarzott
2007-07-27 17:55 ` Kay Sievers
2007-07-27 18:05 ` Bill Nottingham
2007-07-27 18:17 ` Kay Sievers [this message]
2007-07-27 18:32 ` Marco d'Itri
2007-07-27 19:10 ` Matthias Schwarzott
2007-07-27 20:04 ` Matthias Schwarzott
2007-08-01 19:31 ` Matthias Schwarzott
2007-08-02 9:06 ` 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=1185560254.23818.5.camel@lov.localdomain \
--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).