Mathias Gug <[EMAIL PROTECTED]> writes:
> Waiting until S40networking is run brings up an issue with iscsi
> devices. The current way of handling iscsi devices is to treat them as
> local devices by making sure that all iscsi devices are created before
> local filesystems are mounted (S35mountall.sh and S30checkfs.sh). That
> requires ifupdown scripts to be run as soon as network interfaces are
> discovered instead of S40networking.
ah, I see. This means that you've decided that booting from iscsi
devices (feature A) is "more important" than booting with having wpa
statically configured (feature B) in /etc/network/interfaces.
This particular bug is about B. I don't agree that A warrants breaking
B. What you have done is to deliberatly break B in order to allow A to
work.
How about this: ifupdown needs to somehow know that a statically
configured wpa device cannot be upped early in the boot process, but
allow other devices to be configured. So the delayed starting of the
interface is made conditionally on that fact. The question is who
detects this. I see two possibilites
- ifupdown
- the wpasupplicant ifupdown hook.
I'd suggest looking in the 2nd first.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
** Changed in: wpasupplicant (Ubuntu)
Importance: Medium => High
Assignee: (unassigned) => Mathias Gug (mathiaz)
** Changed in: wpasupplicant (Ubuntu)
Target: None => jaunty-alpha-2
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
