On Sat, Jan 16, 2010 at 03:31:28PM +0100, Wouter Verhelst wrote: > There was no further discussion on this item since the above date.
FWIW, I for one hadn't commented up to now because I find that fundamentally, implementing a compatible commandline interface for ifup/ifdown and not implementing support for /etc/network/interfaces is precisely backwards, and I was waiting to see if anyone else would speak to this point. AFAICS, there are only two places in the system where other packages integrate by calling ifup/ifdown: /etc/init.d/networking, and /lib/udev/net.agent. The former ought to be all but obsoleted by the latter (N.B.: "should", but isn't), and the latter could just as well be moved to the ifupdown package itself and a corresponding agent be provided by any conflicting packages. So the commandline ifup/ifdown interface is of little relevance, whereas the configuration state contained in /etc/network/interfaces is of vital importance to the operation of the system and I would expect anyone trying to replace ifupdown to handle this critical configuration migration issue. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
