On Thu, Dec 03, 2015 at 03:51:14PM +0100, Michael Biebl wrote: > Just minor nitpick from the peanut gallery: Upstream wants it to be > called systemd, not SystemD.
Oops.
> > No problem. Are there other such services that might require loading
> > before ifupdown? SELinux?
>
> Should we order networking.service after
>
> - systemd-sysctl.service
> applies sysctl settings from /etc/sysctl.{conf,d/}
> - systemd-modules-load.service
> loads kernel modules specified in /etc/modules, /etc/modules-load.d/
That sounds like a good idea. Ifupdown itself and most of the plugins
would normally work fine without those dependencies, but an admin might
intentionally put something in there that is expected to be set/loaded
before networking is brought up. I'll just err on the safe side.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
