On Mon, Sep 20, 2010 at 4:42 PM, Michael Biebl <mbi...@gmail.com> wrote:
> 2010/9/20 Kay Sievers <kay.siev...@vrfy.org>: > > On Mon, Sep 20, 2010 at 14:16, Gustavo Sverzut Barbieri > > <barbi...@profusion.mobi> wrote: > >> - systemd-modules-load.service: why do we need this as a separated > >> service? > > > > What else would it be? > > > >> Anyway, shouldn't it be in > >> /lib/systemd/system/sysinit.target.wants by default? > > > > It should, yes. > > > >> - systemd-vconsole-setup.service: shouldn't it be in > >> /lib/systemd/system/sysinit.target.wants? Or maybe > >> /etc/systemd/system/sysinit.target.wants? > > > > Should be in /lib by default. > > > >> - systemd-random-seed-load.service: why do we need this as a > >> separated service? Anyway, shouldn't it be in > >> /lib/systemd/system/sysinit.target.wants by default? > > > > Same here. Enabled by default > > > >> - systemd-random-seed-save.service: why do we need this as a > >> separated service? Anyway, shouldn't it be in > >> /lib/systemd/system/shutdown.target.wants by default? > > > > Same. > > This clashes with our existing sysv init scripts on Debian. > > Could those services only be enabled by default if you make a > native/non-sysv build? > > That would be awesome. Something like --with-init and that gives you all the native systemd stuff, like poweroff/reboot/fsck (not implemented yet) and so forth. Jens
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
