encfs systemd startup script - how to ask for a password?

[Ralf Mardorf]

On Wed, 2014-04-23 at 21:09 +0200, Ralf Mardorf wrote:
> On Wed, 2014-04-23 at 19:14 +0100, Julian Gilbey wrote:
> > What am I doing wrong, and what can I do about it?
> 
> Your mistake is to switch to systemd, while there's no need to do this.
> 
> My "main" distro is Arch Linux, so I have to use systemd for this
> distro, but for my Debian install, a mix of stable, testing and
> unstable, I stay with SysV.
> 
> I need the (for my needs) advantages of Arch Linux, but I dislike its
> disadvantage being based on systemd.
> 
> If you want to reply, please neither reply to Debian user, nor to me
> privately, join
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic .
> 
> Regards,
> Ralf

PS: Btw. on the Arch general mailing list there are no flame wars about
systemd anymore, all users, at least the users who are not banned from
the list, stay relaxed when there's an issue regarding to systemd. I'm
not banned, neither a "moderation flag is set" for me, but I'm one of
those who nearly were banned when the transition started and all people
of the list needed to pass moderation for a long, long time during and
after the transition. Around 2 years since the transition to systemd was
finished, there are still issues for, lets say "exotic" needs. IOW IMO
systemd isn't ready for the show until today, it's still beta. AFAIK
systemd isn't able to provide everything that inst scrips provided
completely stable since more than a decade. I might be mistaken, but I
don't think that I'm mistaken.

An not that exotic example, what would you do, if there's would be no
chance to boot broken install? Likely you would take a look at the
kernel's ring buffer log file, using e.g. a live CD. You can do that
assumed the log file isn't binary, but ASCII, but the systemd journal is
binary.