[systemd-devel] systemd-networkd on by default?

[Reindl Harald]

Am 21.02.2014 16:44, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 21/02/14 08:45 did gyre and gimble:
>> Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
>>> On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
>>>> systemd-networkd seems to get started by default in 209. Why is this?
>>>> What if I don't want to use it to manage my networks? Why does it have
>>>> to be on by default?
>>>
>>> I think the reasoning was that it doesn't do anything by default (when
>>> there are no configuration files)
>>
>> that is a bad reasoning
>>
>> not a single process should be running if it has no job to do
>> for the sake of ressource usage, security and clean systems
> 
> Well I kinda get that using it for containers and such like could be
> useful, but I also suspect it should be bus or socket activated rather
> than statically enabled... like localed, datetimed etc. Any reason to
> enable it statically? (I guess it maybe has to do stuff by itself, but I
> would figure udev should kick it in via the setup link built in in most
> cases - but I guess that wouldn't work inside containers, so perhaps
> this is where things break down and you need it statically enabled)

statically enabled is bad in general, containers are not a good
reason to enable something for everybody, many if not most people
never will use containers for several reasons and if it because
they use full-virtualization and move machines between different
also non-linux hosts

where i would support something new enabled by default is if
could *replace* something else like LSB network.service while
use it's ifcfg-configurations for backward compatibility and
test out if it really can replace all cases

if i can replace that below i start to be one of the first
production users in a complexer setup (one is the MAC of
the physical card, the other is what it becames before
fetch the IP from the ISP because you need to register
your MAC there, that's the same like MAC cloning
in small soho-routers)

DEVICE=eth1
HWADDR=68:05:ca:0d:62:c1
ONBOOT=yes
BOOTPROTO=dhcp
IPV6INIT=no
NM_CONTROLLED=no
USERCTL=no
PEERDNS=no
MACADDR=00:50:8d:b5:cc:de

but something hanging around unconfigured please no


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140221/a06e290e/attachment-0001.pgp>