Re: support for merged /usr in Debian
On Sat, 16 Jan 2016 17:12:02 +0100, Vincent Bernat <firstname.lastname@example.org>
> ? 16 janvier 2016 16:38 +0100, Marc Haber <email@example.com> :
>> It's simply unproductive to first having to argue with upstream if one
>> needs one certain IPv6 /proc/sys/net option in systemd-networkd _and_
>> to wait for the next Debian stable release for this possibility to
>> become available, if I need to set this option for my network to work
>You seem to always take vague examples to avoid being contradicted. You
>can execute any unit before and after network is setup through the
Show me how to set a certain option to a VLAN interface that is
created by /etc/systemd/network/foo.netdev and needs to be set before
the interface is taken "up" by /etc/systemd/network/foo.network. Both
unit files are processed by the same systemd-networkd.service with no
hook in between.
>If you need to set some sysctl after an interface has
>been configured, just do it:
Yes. Easy in theory.
>> And it's quite arrogant to not implement things that ease starting
>> daeons that don't have their own configuration files, saying the
>> daemons should have configuration files and not rely on their command
>> line, hence systemd should not have features to make building daemon
>> command lines easier. Heck, some of those daemons have been around
>> since before systemd upsteam was born.
>And they seem to work fine with systemd. Upstream is pushing for people
>to just write an override. But we are free to use EnvironmentFile=.
People in the systemd community are asking us to not use
EnvironmentFile or otherwise Lennart might feel forced to remove it
since we're all using it wrong.
This is what gets me absolutely furious.
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834