On 2015-04-22 14:20:00 +0200, Michael Biebl wrote:
Am 22.04.2015 um 10:21 schrieb Vincent Lefevre:
On 2015-04-21 17:27:46 +0200, Michael Biebl wrote:
The ifup@.service is triggered by a udev rule and responsible to handle
allow-hotplug interfaces.
I hope that this will remain always
Am 22.04.2015 um 10:21 schrieb Vincent Lefevre:
On 2015-04-21 17:27:46 +0200, Michael Biebl wrote:
The ifup@.service is triggered by a udev rule and responsible to handle
allow-hotplug interfaces.
I hope that this will remain always optional. For a laptop at least,
that's not the correct
On 2015-04-21 17:27:46 +0200, Michael Biebl wrote:
The ifup@.service is triggered by a udev rule and responsible to handle
allow-hotplug interfaces.
I hope that this will remain always optional. For a laptop at least,
that's not the correct way to do.
--
Vincent Lefèvre vinc...@vinc17.net -
Am 21.04.2015 um 14:08 schrieb Mihamina Rakotomandimby:
Hi all,
I used to manage network through /etc/network/interfaces.
Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3)
My context in headless VMs (no DE, no Xorg, no GUI)
With Jessie and systemd: is it still managed
Hi there,
Am 2015-04-21 16:06, schrieb Michael Biebl:
Am 21.04.2015 um 15:42 schrieb Christian Seiler:
There is something called systemd-networkd, which is not
part of Jessie's systemd version, but will (probably) be
part of future Debian versions. This offers an alternative
way to configure
Am 21.04.2015 um 15:42 schrieb Christian Seiler:
There is something called systemd-networkd, which is not
part of Jessie's systemd version, but will (probably) be
part of future Debian versions. This offers an alternative
way to configure networking.
Note, however, that systemd-networkd by
On 04/21/2015 04:42 PM, Christian Seiler wrote:
Hi,
Am 2015-04-21 14:08, schrieb Mihamina Rakotomandimby:
I used to manage network through /etc/network/interfaces.
Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3)
My context in headless VMs (no DE, no Xorg, no GUI)
With
Hi,
Am 2015-04-21 14:08, schrieb Mihamina Rakotomandimby:
I used to manage network through /etc/network/interfaces.
Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3)
My context in headless VMs (no DE, no Xorg, no GUI)
With Jessie and systemd: is it still managed with
Am 21.04.2015 um 16:06 schrieb Michael Biebl:
If you want to use networkd, you'd have to run
systemctl enable systemd-network.service
Thats systemctl enable systemd-networkd.service. Note the missing 'd'
--
Why is it that all of the instruments seeking intelligent life in the
universe are
Hi all,
I used to manage network through /etc/network/interfaces.
Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3)
My context in headless VMs (no DE, no Xorg, no GUI)
With Jessie and systemd: is it still managed with /etc/network/interfaces?
For the mount component, I found
Am 21.04.2015 um 16:20 schrieb Mihamina Rakotomandimby:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521
https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service
If my reading and deduction is correct, systemd will call ifup that will
read /etc/network/interface.
Am 2015-04-21 16:20, schrieb Mihamina Rakotomandimby:
Thank you Christian,
Just to be sure, I saw that:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521
https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service
I think that's Ubuntu-specific; even though
Am 21.04.2015 um 17:15 schrieb Christian Seiler:
Am 2015-04-21 16:20, schrieb Mihamina Rakotomandimby:
Thank you Christian,
Just to be sure, I saw that:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521
https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service
I
13 matches
Mail list logo
