On Mon, Sep 20, 2010 at 4:42 PM, Michael Biebl <span dir="ltr"><<a href="mailto:mbiebl@gmail.com">mbiebl@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2010/9/20 Kay Sievers <<a href="mailto:kay.sievers@vrfy.org">kay.sievers@vrfy.org</a>>:<br>
<div class="im">> On Mon, Sep 20, 2010 at 14:16, Gustavo Sverzut Barbieri<br>
> <<a href="mailto:barbieri@profusion.mobi">barbieri@profusion.mobi</a>> wrote:<br>
>> - systemd-modules-load.service: why do we need this as a separated<br>
>> service?<br>
><br>
> What else would it be?<br>
><br>
>> Anyway, shouldn't it be in<br>
>> /lib/systemd/system/sysinit.target.wants by default?<br>
><br>
> It should, yes.<br>
><br>
>> - systemd-vconsole-setup.service: shouldn't it be in<br>
>> /lib/systemd/system/sysinit.target.wants? Or maybe<br>
>> /etc/systemd/system/sysinit.target.wants?<br>
><br>
> Should be in /lib by default.<br>
><br>
>> - systemd-random-seed-load.service: why do we need this as a<br>
>> separated service? Anyway, shouldn't it be in<br>
>> /lib/systemd/system/sysinit.target.wants by default?<br>
><br>
> Same here. Enabled by default<br>
><br>
>> - systemd-random-seed-save.service: why do we need this as a<br>
>> separated service? Anyway, shouldn't it be in<br>
>> /lib/systemd/system/shutdown.target.wants by default?<br>
><br>
> Same.<br>
<br>
</div>This clashes with our existing sysv init scripts on Debian.<br>
<br>
Could those services only be enabled by default if you make a<br>
native/non-sysv build?<br>
<div class="im"><br></div></blockquote><div><br>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.<br><br>Jens<br>
<br></div></div>