On Fri, Sep 26, 2014 at 01:32:26AM +0200, Matthias Urlichs wrote:
> Hi,
>
> Guido Günther:
> > The overlap between n-m and systemd-networkd saddens me. n-m got
> > support for team/bond interfaces, VLANs, etc a while ago and now we get
> > to see yet another tool from systemd-* to redo this.
>
>
On Fri, 26 Sep 2014 13:25:13 +0200, Wouter Verhelst
wrote:
>On Fri, Sep 26, 2014 at 12:01:27PM +0200, Marc Haber wrote:
>> On Fri, 26 Sep 2014 10:58:22 +0200, Josselin Mouette
>> wrote:
>> >The problem on servers is that you need advanced features such as
>> >bridging, VLANs, bonding… and NM alre
On Fri, Sep 26, 2014 at 12:01:27PM +0200, Marc Haber wrote:
> On Fri, 26 Sep 2014 10:58:22 +0200, Josselin Mouette
> wrote:
> >The problem on servers is that you need advanced features such as
> >bridging, VLANs, bonding… and NM already does all of that.
>
> Is there documentation about that? Doe
Marc Haber wrote:
On Fri, 26 Sep 2014 10:58:22 +0200, Josselin Mouette
wrote:
>The problem on servers is that you need advanced features such as
>bridging, VLANs, bonding… and NM already does all of that.
Is there documentation about that?
On Fri, 26 Sep 2014 10:58:22 +0200, Josselin Mouette
wrote:
>The problem on servers is that you need advanced features such as
>bridging, VLANs, bonding… and NM already does all of that.
Is there documentation about that? Does NM have hooks like wicd used
to have?
Greetings
Marc
--
On Sep 26, Josselin Mouette wrote:
> As Vincent explained, NM works in a similar way.
> The problem on servers is that you need advanced features such as
> bridging, VLANs, bonding… and NM already does all of that.
But it has a significant list of dependencies, which is obviously tuned
for a des
Brian May wrote:
On 26 September 2014 09:32, Matthias Urlichs
wrote:
True, the usecases overlap somewhat, but they're still
different.
I wouldn't want to install n-m (and the 30 libraries it
❦ 26 septembre 2014 10:38 +1000, Brian May :
> True, the usecases overlap somewhat, but they're still different.
>
> I wouldn't want to install n-m (and the 30 libraries it depends
> on)
> in an initramfs, for instance.
>
> Unless I am mistaken, I believe systemd-networkd wo
On 26 September 2014 09:32, Matthias Urlichs wrote:
> True, the usecases overlap somewhat, but they're still different.
>
> I wouldn't want to install n-m (and the 30 libraries it depends on)
> in an initramfs, for instance.
>
Unless I am mistaken, I believe systemd-networkd would be a lot bett
Hi,
Guido Günther:
> The overlap between n-m and systemd-networkd saddens me. n-m got
> support for team/bond interfaces, VLANs, etc a while ago and now we get
> to see yet another tool from systemd-* to redo this.
True, the usecases overlap somewhat, but they're still different.
I wouldn't want
On Thu, 2014-09-25 at 19:07 +0200, Guido Günther wrote:
> On Wed, Sep 24, 2014 at 12:53:51PM +0100, Simon McVittie wrote:
> > My understanding is that they recommend NetworkManager or ConnMan (which
> > are competitors, and fill a similar niche) for dynamic / mobile /
> > wireless situations; where
On Wed, Sep 24, 2014 at 12:53:51PM +0100, Simon McVittie wrote:
> My understanding is that they recommend NetworkManager or ConnMan (which
> are competitors, and fill a similar niche) for dynamic / mobile /
> wireless situations; whereas systemd-networkd is intended to be more
> like a competitor f
On 24/09/14 11:45, Martin Wuertele wrote:
> Last time I used n-m for OpenVPN it could only launch one VPN, not
> multiple ones. Has that changed?
Yes, I've had home and office VPNs up at the same time.
(Obviously if you have more than one VPN that wants to provide the
default route, or more gener
* Philipp Kern [2014-09-11 09:15]:
> Not everyone uses init scripts. There is e.g. also a plugin for
> network-manager, in which case it will just work.
Last time I used n-m for OpenVPN it could only launch one VPN, not
multiple ones. Has that changed? Tough it seems systemd upstream is not
happ
Hi,
Thorsten Glaser:
> The systemd apologetists
If you want a civil dialogue with systemd proponents, please refrain from
using loaded words like this one.
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
Can anyone please just read the rest of this thread before continuing
this flamewar? The original question was asked, answered and the answer
was deemed satisfactory.
Best,
Axel Wagner
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
On Thu, 11 Sep 2014, Gergely Nagy wrote:
> OpenVPN works just fine with systemd. Its init script does not, but for
Yes, but for many installations, its init script is what is
required for the VPN to “work”.
> There is no problem with that, at all.
Right, no problem except that remote machines a
On 11/09/14 18:53, Mirosław Baran wrote:
> Does NetworkManager support multiple VPN connections right now?
Yes.
> (Also,
> what about persistent VPN setups that are independent from the desktop
> session?)
Yes, there's a flag for "automatically connect this VPN when you get
lower-level connectiv
❦ 11 septembre 2014 18:53 +0100, Mirosław Baran :
>> Ultimately, I think this should all be replaced by VPN support in
>> NetworkManager and systemd-networkd.
>
> Does NetworkManager support multiple VPN connections right now? (Also,
> what about persistent VPN setups that are independent from t
On 11/09/2014 03:53, Paul Wise wrote:
Ultimately, I think this should all be replaced by VPN support in
NetworkManager and systemd-networkd.
Does NetworkManager support multiple VPN connections right now? (Also,
what about persistent VPN setups that are independent from the desktop
session?)
Daniel Dickinson writes:
> On 10/09/14 02:52 PM, Noel Torres wrote:
>>
>> Yes. Why to install OpenVPN which might not work? aptitude will tell you
>> that
>> they are not coinstallable and the sysadmin will then have the option of
>> switching init system to a non default one, knowing what th
On Wed, Sep 10, 2014 at 02:01:00PM +0200, Ondřej Surý wrote:
> Alberto,
>
> I think you might be too deep in sysvinit paradigms how we did (hack)
> things before.
> I personally think that mapping the functionality 1:1 is a wrong
> approach because you will end up in some impossible scenario in t
On 2014-09-10 20:52, Noel Torres wrote:
Yes. Why to install OpenVPN which might not work? aptitude will tell
you that
they are not coinstallable and the sysadmin will then have the option
of
switching init system to a non default one, knowing what that means,
and
having a working OpenVPN config
On Wed, Sep 10, 2014 at 8:01 PM, Ondřej Surý wrote:
> I think the better way how to convert openvpn to systemd would be:
>
> to convert all AUTOSTART= VPNs to openvpn@ enabled instances and all
> other to disabled openvpn@ instances at upgrade time. I guess there
> might be a need to some more sub
On 10/09/14 02:52 PM, Noel Torres wrote:
>
> Yes. Why to install OpenVPN which might not work? aptitude will tell you that
> they are not coinstallable and the sysadmin will then have the option of
> switching init system to a non default one, knowing what that means, and
> having a working Ope
On Wednesday, 10 de September de 2014 18:55:06 Adam D. Barratt escribió:
> On Wed, 2014-09-10 at 17:47 +0100, Noel Torres wrote:
> > On Wednesday, 10 de September de 2014 05:25:44 Andrey Rahmatullin
escribió:
> > > On Tue, Sep 09, 2014 at 09:26:28PM +0100, Noel Torres wrote:
> > > > openvpn packag
On Wed, 2014-09-10 at 17:47 +0100, Noel Torres wrote:
> On Wednesday, 10 de September de 2014 05:25:44 Andrey Rahmatullin escribió:
> > On Tue, Sep 09, 2014 at 09:26:28PM +0100, Noel Torres wrote:
> > > openvpn package should Conflitcs systemd in order to avoid systemd being
> > > installed
> >
>
On Wednesday, 10 de September de 2014 05:25:44 Andrey Rahmatullin escribió:
> On Tue, Sep 09, 2014 at 09:26:28PM +0100, Noel Torres wrote:
> > openvpn package should Conflitcs systemd in order to avoid systemd being
> > installed
>
> ITYM "to avoid openvpn being installed".
No, I mean what I wrot
Alberto,
I think you might be too deep in sysvinit paradigms how we did (hack)
things before.
I personally think that mapping the functionality 1:1 is a wrong
approach because you will end up in some impossible scenario in the end
anyway.
I think the better way how to convert openvpn to systemd
On Tue, Sep 09, 2014 at 09:26:28PM +0100, Noel Torres wrote:
> openvpn package should Conflitcs systemd in order to avoid systemd being
> installed
ITYM "to avoid openvpn being installed".
--
WBR, wRAR
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsub
Von meinem iPad gesendet
> Am 09.09.2014 um 22:26 schrieb Noel Torres :
>
> On Tuesday, 9 de September de 2014 16:51:20 Alberto Gonzalez Iniesta escribió:
>> AltSubject: For those who care about OpenVPN
>>
>> Dear fellow developers,
>>
>> This is a cry for help. I've been trying to support sy
On Tuesday, 9 de September de 2014 16:51:20 Alberto Gonzalez Iniesta escribió:
> AltSubject: For those who care about OpenVPN
>
> Dear fellow developers,
>
> This is a cry for help. I've been trying to support systemd in OpenVPN for
> some time, but the results are not satisfactory. I'd like to k
AltSubject: For those who care about OpenVPN
Dear fellow developers,
This is a cry for help. I've been trying to support systemd in OpenVPN for some
time, but the results are not satisfactory. I'd like to keep the current (SysV)
behaviour in systemd but it's becoming quite an annoying task.
I'd
33 matches
Mail list logo
