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

all modern desktops need systemd, either send patches or life with it (Re: systemd now appears to be only possible init system in testing)


(as this thread has already attracted two "interesting replies", I'll try 
again to convey the message which has not been heard yet... I don't have high 
hopes this thread won't become a flamefest, but I want to at least try to kill 
the flames before they explode...)

(And if you know systemd, please scroll down and help Julian with his actual 

On Dienstag, 22. Juli 2014, 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?

Because all modern desktops now need systemd so all features work. blame 
upstream^w^wsend patches to upstream and Debian will have those...

Really, get over it or do something. Ranting on -devel will not change 

And this is actually pretty old news too: see 

Thank you.

> So I would presume that for many or most Debian systems, systemd is
> now required

s#most Debian systems#most Debian desktop systems#

> 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 hope someone will be able to help Julian with this question...


Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: