service iptables save, systemctl, and unhelpful error messages

Al Dunsmuir al.dunsmuir at sympatico.ca
Thu Feb 16 00:36:22 UTC 2012


On Wednesday, February 15, 2012, 7:15:13 PM, Reindl wrote:
> Am 16.02.2012 00:48, schrieb Al Dunsmuir:
>> On Wednesday, February 15, 2012, 6:12:44 PM, Reindl wrote:
>>> this will not work since if a systemd-unit is present
>>> systemd no longer is interested in anything from
>>> /etc/init.d/
>> 
>>> so there is no solution except patch systemd if iptables.service is
>>> called which will not happen because it would be unmaintainable
>>> ober the long and doing it for iptables would bring a lot of
>>> of other people complaining "but why not XXX whateverservice" too
>> 
>> Johann  has  spent  some significant time contributing to the last two
>> Fedora releases, specifically a great deal of the actual conversion to
>> systemd init.
>> 
>> I'm  sure  that  he  and  others  can get something functioning rather
>> quickly  by  working  _with_  the  systemd developers. Even better, my
>> experience is that both Johann and Lennart are fully capable of coming
>> up  these  answers without filling everyone's days with bile and crass
>> negativity.
>> 
>> Why  not  let  them have a chance, instead of insisting on using every
>> opportunity to attempt to advance your own twisted viewpoint?

> what is your exactly problem here?

> well, wait their replies that they will not include all
> sorts of exceptions for random services in systemd because
> their target is holding systemd clean and compact to prvent
> the need of the next init-system switch in few years

Q.E.D.



More information about the devel mailing list