Prev: Re(2): eth0 or eth1
Next: Successful running 3D apps w open driver. Solving Xserver modes switching.
From: peasthope on 23 Feb 2010 20:40 Date: Tue, 23 Feb 2010 19:48:46 -0500, Tom H wrote, > Neither ifconfig nor ip use /e/n/i to configure nics. So the end user need only use ip rather than ifconfig and not be further concerned about the deprecation? > /e/n/i may be > referred to in the "see also" section of man page of ifconfig, but it > is "only" used by ifup and ifdown. We should continue to maintain /e/n/i as always. Thanks, ... P. -- Google "pathology workshop" -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/171056407.71815.434.(a)cantor.invalid
From: Tom H on 23 Feb 2010 21:00
>> Neither ifconfig nor ip use /e/n/i to configure nics. > So the end user need only use ip rather than ifconfig > and not be further concerned about the deprecation? I would worry about its deprecation when it is moved out of main or stops neing maintained. Although, I have read an article where the author was advocating dropping ifconfig because he was able to create virtual interfaces with ip that were not detected by ifconfig. IIRC one of the reasons that ifconfig could not detect/list them was that he named them all eth0 (and it worked) rather than eth0:0, eth0:1, ... >> /e/n/i may be >> referred to in the "see also" section of man page of ifconfig, but it >> is "only" used by ifup and ifdown. > We should continue to maintain /e/n/i as always. Unless you want to write an init script that brings your nics up with ifconfig or ip. (Anyone know how interfaces are brought up if ifupdown is purged?) > Thanks You're welcome. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/6d4219cc1002231752s15bac247p1aecc4edcd0e459(a)mail.gmail.com |