Re: systemd now appears to be only possible init system in testing
Am Dienstag, 22. Juli 2014, 22:54:55 schrieb Julian Gilbey:
> For me, this is a killer, as I still do not know how to solve the
> problem I asked a while back on debian-user
> (https://lists.debian.org/debian-user/2014/04/msg01286.html): in
> summary, I need to unlock an encrypted filesystem during boot time by
> asking for a password to feed into encfs. But I cannot figure out how
> to do this under systemd.
> Answers to this question would also be much appreciated!
I really hope systemd will soon be able to be co-installed with sysvinit-core
Here is another reason why:
Re: Bug#755989: cfdisk: german help page strangely formatted
(In addition to NFS mounts broken with systemd currently.)
Sure I can go through setting up chroot for that, yet I really think if my
work requires changes in other packages and the recent systemd changes do
require this kind of work, I *help* with these changes, instead of uploading
my changes to unstable *before* the other packages have been fixed.
Especially if its such an disruptive change with all kind of side effects.
I only package some quite easy packages so far and I know its a lot of work to
do good debian packaging, a lot more so with complex stuff like systemd. I know
upload has been announced five month ago or so. But still…
I know I will hold back systemd until this is resolved. I am not yet going
systemd only. By trust in systemd is not deep enough to do this on production
systems. Yes, unstable is unstable, but… but putting in onto selected
production systems for testing allows me to test stuff without investing a lot
of extra time for setting up and using test systems.
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7