Ubuntu
ifupdown package

Branches for Jaunty

Name		Status	Last Modified	Last Commit
lp:ubuntu/jaunty/ifupdown		2 Mature	2009-08-08 11:23:13 UTC 2009-08-08	29. * debian/ifupdown.udev: In fact, ther... Author: Scott James Remnant (Canonical) Revision Date: 2009-03-05 14:13:53 UTC * debian/ifupdown.udev: In fact, there's no reason not to call the ifup unconditionally either; if it doesn't have a driver, but is listed in /etc/network/interfaces with "auto" we can still have a crack at bringing it up. We may as well make the /var/run/network directory in this rule too. * debian/loopback.init: Then this init script can go away.
lp:~ubuntu-branches/ubuntu/jaunty/ifupdown/jaunty-201308281004		1 Development	2013-08-28 10:04:58 UTC 2013-08-28	29. * debian/ifupdown.udev: In fact, ther... Author: Scott James Remnant (Canonical) Revision Date: 2009-03-05 14:13:53 UTC * debian/ifupdown.udev: In fact, there's no reason not to call the ifup unconditionally either; if it doesn't have a driver, but is listed in /etc/network/interfaces with "auto" we can still have a crack at bringing it up. We may as well make the /var/run/network directory in this rule too. * debian/loopback.init: Then this init script can go away.
lp:~ubuntu-branches/ubuntu/jaunty/ifupdown/jaunty-201309120846		1 Development	2013-09-12 08:46:31 UTC 2013-09-12	29. * debian/ifupdown.udev: In fact, ther... Author: Scott James Remnant (Canonical) Revision Date: 2009-03-05 14:13:53 UTC * debian/ifupdown.udev: In fact, there's no reason not to call the ifup unconditionally either; if it doesn't have a driver, but is listed in /etc/network/interfaces with "auto" we can still have a crack at bringing it up. We may as well make the /var/run/network directory in this rule too. * debian/loopback.init: Then this init script can go away.