Arch Linux

Ibex

Member

Registered: 2006-03-02

Posts: 135

Bad udev-rule slowing startup down

Hi all,

My problem was already discussed in another thread a little bit, but I don't have a solution yet, so I decided to give the problem its own thread.

The problem is that one udev-rule is slowing down my udev events. With the rule it takes about 59 seconds, without the rule, the udev-events take only a few seconds. The script is making sure my wireless nic is named "wlan0" and my wired nic is named "lan0". But I dont know how to fix the rule, or how to name the nic's on another way.

The bad rule:

SUBSYSTEM=="net", ATTRS{address}=="00:1c:23:2f:d5:28", NAME="lan0"
SUBSYSTEM=="net", ATTRS{address}=="00:1d:e0:36:a6:21", NAME="wlan0

Anybody?

bangkok_manouel

Member

From: indicates a starting point

Registered: 2005-02-07

Posts: 1,556

Re: Bad udev-rule slowing startup down

I guess it's typo but you have one " missing after "wlan0

FTR, I removed this rule once I switched to iwlwifi driver as it would name the NIC as wlan0 so there would not be any confusion anymore... You may be in the same case (or maybe not).

iphitus

Forum Fellow

From: Melbourne, Australia

Registered: 2004-10-09

Posts: 4,927

Re: Bad udev-rule slowing startup down

there's an easier way to do it anyway, install netcfg and have a look at the example /etc/iftab.

Modify it, and add net-rename to DAEMONS=()

Instant, and a much easier solution to work with.

Ibex

Member

Registered: 2006-03-02

Posts: 135

Re: Bad udev-rule slowing startup down

The " was in the rule, but I accidently removed it while posting. I'll try the netcfg-solution.

Ibex

Member

Registered: 2006-03-02

Posts: 135

Re: Bad udev-rule slowing startup down

About netcfg, when placing SCAN="yes" in every profile, the system tries to connect to the networks, and if it is succesfully connected, stops. But can I also add SCAN="yes" to the wired profile, so that if I boot with the eternetcable, it doesn't start trying connection to various wireless networks?

bangkok_manouel

Member

From: indicates a starting point

Registered: 2005-02-07

Posts: 1,556

Re: Bad udev-rule slowing startup down

'EXCLUSIVE' profiles
A new option that allows easy network switching as requested in the last thread. Forces all other profiles to be shut down before an 'exclusive' profile is started (ie, runs on it's own no others active).

rc.conf, NETWORKS_EXCLUSIVE: Set all profiles to operate exclusively (no others active)
network.d/$profile, EXCLUSIVE: Set this profile only to operate exclusively (no others active)
   
Useful for switching networks and such. Can be set globally to only ever have one profile active, or in each individual profile.
     
Known bug: netcfg2 does nothing if the exclusive profile fails, thus leaving no profiles running.