On 2015-03-17 22:39:56 -0500, David Wright wrote: > Quoting Vincent Lefevre (vinc...@vinc17.net): > > I would like to know why is eth0 up by default? > > > > IIRC, this wasn't the case in the past, but I'm not sure. > > Not knowing what you mean by the past, nor what you're running, I can > but hazard a guess. And I mean guess.
IIRC, several years ago, it wasn't up. Three months ago, I used my laptop with wifi only for 1 - 2 weeks, and there wasn't any problem, so that it is quite recent I think. > I can't remember ever having modified /etc/init.d/networking but I > find I also have /etc/init.d/networking.dpkg-old. Comparing them, > there is a paragraph which was: [...] Perhaps I could do some tests to see whether eth0 was up before entering this script and after... > I haven't tried to trace whether /etc/init.d/networking is calling > ifup_hotplug () on eth0 or any other interface. It's perfectly > possible that my eth0 is up because I (wicd) am watching for the wired > interface to appear (because it should prefer it to wlan). I also use wicd, but I don't track the wired interface (in the config, the device field is blank instead of containing "eth0") because I use it for wifi only. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150318080318.ga4...@xvii.vinc17.org
