From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problems with udev > 106 and multiple network cards
Date: Wed, 11 Apr 2007 02:59:04 +0000 [thread overview]
Message-ID: <200704110703.40946.arvidjaar@mail.ru> (raw)
In-Reply-To: <461BFFDD.2040401@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
On Wednesday 11 April 2007, Gabriel C wrote:
[...]
> I figured the 'cards names' looks weird , random they are called now
> ethX_rename (
> http://frugalware.org/~crazy/other/udev/sys_class_net.txt |
> http://frugalware.org/~crazy/other/udev/ifconfig-a.txt )
> as well I get for each card an long timeout ( 5 to 15 seconds for each
> wrong named card ) on boot because the 70-persistent-net.rules.
>
> Deleting the rules before udev starts make the timout be human again (
> like 2 - 3 seconds ) but the rules are still wrong because I get as
> NAME ethX_rename.
>
well it is possible that your rules are now confused by this commit. At least,
it is the only one that has something to do with network interfaces:
commit eb5b86405b14ca2ac2508f9dec9862cc57110131
Author: Kay Sievers <kay.sievers@vrfy.org>
Date: Mon Mar 19 09:56:53 2007 +0100
update %n on netif name change
:100644 100644 24f65ca... 03514e1... M udev_device.c
:100644 100644 ea02b8e... f8844a8... M udev_rules.c
:100644 100644 7431dd6... 1846a42... M udev_sysfs.c
You could try to revert it as quick check.
> I noticed one more strange thing with the db , while in <= 106 the db
> was like foo\@bar -> something , >106 looks here like %2fbar%2fbaz ->
> something
> ( http://frugalware.org/~crazy/other/udev/udev_db.txt )
>
Yes it is this one:
commit 9c6ad9fbbac82e517f5e748ddbe166f96f120afe
Author: Kay Sievers <kay.sievers@vrfy.org>
Date: Wed Mar 14 21:41:33 2007 +0100
encode db-file names, instead of just replacing '/'
:100644 100644 849de96... 200d7e8... M udev.h
:100644 100644 b1217d8... 9032eef... M udev_db.c
:100644 100644 8cda472... b0641f0... M udev_utils_string.c
:100644 100644 961ceb5... 07f1c48... M udevd.c
:100644 100644 c809d2d... 2bdd0c8... M udevtrigger.c
-andrey
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
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=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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-04-11 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 21:21 Problems with udev > 106 and multiple network cards Gabriel C
2007-04-11 2:59 ` Andrey Borzenkov [this message]
2007-04-11 6:41 ` Matthias Schwarzott
2007-04-11 11:14 ` Gabriel C
2007-04-11 13:27 ` Gabriel C
2007-04-11 17:51 ` Gabriel C
2007-04-12 9:12 ` Matthias Schwarzott
2007-04-12 17:43 ` Gabriel C
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=200704110703.40946.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).