Le 28/03/2014 08:23, Matt Grant a écrit :
One thing that put me off ifupdown quite some time ago was finding that
configured bridges made NFS client mounts on the host wait... who would
implement a bridge with interface listen/wait/STP functionality on a
pure work station or server? Sounds
Stéphane Glondu glo...@debian.org writes:
Le 28/03/2014 08:23, Matt Grant a écrit :
One thing that put me off ifupdown quite some time ago was finding that
configured bridges made NFS client mounts on the host wait... who would
implement a bridge with interface listen/wait/STP functionality
On Sat, 29 Mar 2014 01:34:27 -0400 (EDT), Andrei POPESCU wrote:
Or connman.
Frankly, I think that the claim that ifupdown is dysfunctional is an
exaggeration at
best and untrue at worst. I am not claiming that it is bug free; but in
my experience, it works just fine; and I see no compelling
* Stephen Powell (zlinux...@wowway.com) [140329 15:05]:
On Sat, 29 Mar 2014 01:34:27 -0400 (EDT), Andrei POPESCU wrote:
Or connman.
Frankly, I think that the claim that ifupdown is dysfunctional is an
exaggeration at
best and untrue at worst. I am not claiming that it is bug free; but
On Sat, 29 Mar 2014 15:37:28 +0100, Andreas Barth a...@ayous.org
wrote:
* Stephen Powell (zlinux...@wowway.com) [140329 15:05]:
On Sat, 29 Mar 2014 01:34:27 -0400 (EDT), Andrei POPESCU wrote:
Or connman.
Frankly, I think that the claim that ifupdown is dysfunctional is an
exaggeration
El Fri, 28 de Mar 2014 a las 2:28 AM, Josselin Mouette
j...@debian.org escribió:
Le vendredi 28 mars 2014 à 20:23 +1300, Matt Grant a écrit :
I sincerely would like to work with the ifupdown maintainer and
systemd/udev crew to work all this out. A basic level/interface of
functionality for
Hi!
I am the developer of netscript-2.4, an alternative network
configuration system for Debian written in /bin/bash - quite old.
First of all, though, my stuff is not the glorious gloopiest best. I
have split the iptables stuff out to netscript-ipfilter, better than
iptables-persistent I must
Hello,
On Fri, 28 Mar 2014 20:23:15 +1300
Matt Grant m...@mattgrant.net.nz wrote:
I KNOW MY STUFF COULD/SHOULD BE BETTER! Maybe I should reimplement a
lot of it using only what is provided by perl-base and /bin/sh, but
lets get some sense here please.
Thanks for the rant, it's been
Le vendredi 28 mars 2014 à 20:23 +1300, Matt Grant a écrit :
I sincerely would like to work with the ifupdown maintainer and
systemd/udev crew to work all this out. A basic level/interface of
functionality for replaceable network configuration packages would be
nice.
Alternatively, we could
On Fri, Mar 28, 2014 at 5:28 PM, Josselin Mouette wrote:
Alternatively, we could make NetworkManager the default.
It is already here, it works, and it doesn’t have such problems.
Or systemd-networkd.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to
Hi Andrew,
I am willing to co-maintain it with you and evolve it. Previously I have
worked professionally as a router programmer, and have contributed to
Quagga/Zebra OSPF.
Please also note that's there's no point in rewriting ifupdown from
scratch to provide the same interface; the existing
Paul Wise pabs at debian.org writes:
On Fri, Mar 28, 2014 at 5:28 PM, Josselin Mouette wrote:
Alternatively, we could make NetworkManager the default.
It is already here, it works, and it doesn’t have such problems.
Or systemd-networkd.
I surely hope the both of you are kidding.
bye,
Le vendredi 28 mars 2014 à 11:45 +, Thorsten Glaser a écrit :
Paul Wise pabs at debian.org writes:
On Fri, Mar 28, 2014 at 5:28 PM, Josselin Mouette wrote:
Alternatively, we could make NetworkManager the default.
It is already here, it works, and it doesn’t have such problems.
Paul Wise p...@debian.org writes:
On Fri, Mar 28, 2014 at 5:28 PM, Josselin Mouette wrote:
Alternatively, we could make NetworkManager the default.
It is already here, it works, and it doesn’t have such problems.
Or systemd-networkd.
systemd-networkd is not even close to mature yet.
If
Le vendredi 28 mars 2014 à 11:55 -0700, Russ Allbery a écrit :
I realize that doing that well is not horribly challenging, but that is
the most common server use case (and even desktop), and ifupdown does it
quite well.
Come on. We all use ifupdown on our servers just because it is the
default
Josselin Mouette j...@debian.org writes:
Le vendredi 28 mars 2014 à 11:55 -0700, Russ Allbery a écrit :
I realize that doing that well is not horribly challenging, but that is
the most common server use case (and even desktop), and ifupdown does
it quite well.
Come on. We all use ifupdown
Hi!
Actually, I would love to cleanly modify ifupdown with a lot of the
experience I have gained from netscript, and working on actual routers.
Making it not so onerous would not be that much work, and it would have
far better behaviour once improvements are made.
I am putting myself forward for
On Vi, 28 mar 14, 17:39:39, Paul Wise wrote:
On Fri, Mar 28, 2014 at 5:28 PM, Josselin Mouette wrote:
Alternatively, we could make NetworkManager the default.
It is already here, it works, and it doesn’t have such problems.
Or systemd-networkd.
Or connman.
Kind regards,
Andrei
--
18 matches
Mail list logo
