[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd now appears to be only possible init system in testing

On Wed, Jul 23, 2014 at 12:51:16AM +0200, Svante Signell wrote:
> Forward this to the debian CTTE, please!

Thanks for the suggestion, Svante!  I've just reread
https://www.debian.org/devel/tech-ctte and it does not yet seem
appropriate for the CTTE; there has not yet been any discussion with
the relevant package maintainers.

A bit more searching (reading the relevant changelogs) has shown that
bugs https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752939 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754984 contain a lot
more information about this issue.

It seems that once cgmanager 0.27 is allowed into unstable from NEW, a
new version of systemd-shim will be able to be uploaded, which will
allow libpam-systemd to coexist with sysvinit once again.

It's just a shame that various migrations to testing were allowed
before this had been resolved :-(

Anyway, I would still love to know how to write a systemd script which
pauses to accept input from the keyboard before continuing.


> On Tue, 2014-07-22 at 22:54 +0100, Julian Gilbey wrote:
> > I just tried updating testing on my system.  I currently use
> > sysvinit-core (reasons below), but aptitude is telling me that I
> > should remove this in favour of systemd-sysv.  Hmm, why is that?
> > Well, because the new version of libpam-systemd, 208-6, now depends on
> > systemd-sysv rather than systemd-sysv | systemd-shim.  OK, so I'll
> > remove libpam-systemd.  Ooops - that looks pretty disastrous, as so
> > much depends on it, so that's not an option: gdm3, gnome-bluetooth,
> > network-manager, policykit-1, udisks2.
> > 
> > So I would presume that for many or most Debian systems, systemd is
> > now required, and no other /sbin/init providers will work.  I'm
> > unclear whether this was a deliberate policy decision or an unintended
> > consequence of various package requirements.
> > 
> > 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!
> > 
> >    Julian

Reply to: