[ please keep me in CC, I'm not subscribed to this list]
Sam Hartman wrote:
> My understanding is that systemd's implementation of tmpfiles and
> sysusers works even while systemd is not pid 1.
> Why do we need multiple implementations for Debian ports where systemd
> runs?
> I understand why we
The problem I see with alternatives is: what happens when I have init X
set as the current alternative and I boot into init Y with a kernel command
line
or with a Grub-init-Y line?
Will I end up with init Y but with all links pointing to init X commands?
Il giorno dom 23 dic 2018 alle ore 15:58 Dm
Josh Triplett ha scritto:
> sysvinit works similarly, with /lib/sysvinit/init
This was in Jessie, but I don't see any /lib/sysvinit/init in Stretch nor
in Sid,
it's /sbin/init now, am I wrong?
Dmitry Bogatov wrote:
>I propose to replace current approach with update-alternatives(1)
>approach. By
Hi,
sorry for the extended quote, it's for reference in the debian-runit
mailing list (i'm subscribed there and you drop the CC)
Ansgar Burchardt:
>We generally try to avoid tiny packages in the archive; having 1000+
>automatically generated source and binary packages in the archive seems
>like a
4 matches
Mail list logo
