Bugzilla Bug 186156

On Sat, 2007-07-21 at 17:22 -0400, Mike Frysinger wrote:
On Saturday 21 July 2007, Roy Marples wrote:
> > On Sat, 2007-07-21 at 21:28 +0100, Roy Marples wrote:
> > > On Sat, 2007-07-21 at 22:22 +0200, Tobias Klausmann wrote:
> > > > Is there a common bug to report snags to? I've hit one:
> > > > /etc/init.d/net.eth0 used to be a symlink to net.lo. After
> > > > installing, it was gone (I figure it went with baselayout-1).
> > > > Luckily, I have direct console access, otherwise the machine
> > > > would have been gone after the reboot. Definitely something to
> > > > yell about during merging.
> > >
> > > We don't ship with net.eth0 because there is no guarantee an interface
> > > called eth0 exists. net.lo (net.lo0 in *BSDs) always exists so we just
> > > ship that.
> >
> > One very good idea would be to get udev to create any net links that do
> > not exist to net.lo
> >
> > Then we truly have plug and play :)
> 
> indeed, that'd be sleeky and sexy ... go file a bug ;)
> -mike 

Best make it configurable though :)

by definition, files in /etc/udev/ are configurable since they're
CONFIG_PROTECT-ed

This might not be such a good idea for some WLAN drivers (such as rt2500),
besides wlanX it would also create a bogus wmasterX symlink to net.lo which
should not exist, it's not a real interface.

Which is why I said there should be a configure option to turn it on/off. Or
maybe a masking based on name.

BTW, the rt2500 driver only makes the ra0 interface. It's the rt2x00 driver
that makes these, and you only have upstream to blame for that crappy idea.

Isn't this issue hit only when upgrading baselayout?

If so, just preserving any existing symlinks to net.lo* should be sufficient.

The current behavior of baselayout-1 is bug on its own (of owning net.eth0).

So staying focused on the initial report (changing the subject of this bug)
will be easier and quicker, IMHO.

For madwifi (and hopefully the others), `ip a` shows link/ieee802.11 for the
controlling interface wifi0. So udev can take this into account and skip the
creation of the link.

Perhaps someone can attach either working code (using sysfs) or at least
udevinfo -a -p /sys/class/net/DEVICE where DEVICE is one we should not create a
link to.

I don't know if it's related, but I have a problem with the inits scripts. I
remove from boot and default net.eth0 and net.wlan0 but both are still load and
configured. I also remove net.lo but the problem still present. This is a
problem because I ran in a laptop and when both interface are up, for some
reason, the wired one have sort of "preference", and until I shoot down
net.eth0 manually I don't have any connection. This is a VERY big problem if
you have users that don't have permission (or you don't want to have) as they
can't shoot down net.eth0.

I run baselayout-2rc2_r1 in a ~x86 machine.

(In reply to comment #6)
> Perhaps someone can attach either working code (using sysfs) or at least
> udevinfo -a -p /sys/class/net/DEVICE where DEVICE is one we should not create a
> link to.
> 

My madwifi created wifi0 interface has these values, which are different from
the real interface
ATTR{type}=="801"
ATTR{features}=="0x0"

(In reply to comment #8)
> 
> My madwifi created wifi0 interface has these values, which are different from
> the real interface
> ATTR{type}=="801"
> ATTR{features}=="0x0"
> 
First idea: Only auto-create the net.* link if ATTR{type} is "1".