Bug#803356: cryptdisks conflicts with documentation, and is cryptic to use

[Ian Kelling]

Package: systemd
Version: 215-17+deb8u2

https://www.debian.org/releases/stable/amd64/install.txt.en says

"you will have to mount them manually after the boot" 
...
"/etc/init.d/cryptdisks start"

In reality, this exits with success but does nothing.  Looking
through the code, I find that the init.d does exit 0 and nothing
else if parent pid != 1, unless the command is
"reload."

It should actually do something, and it should not report success
when doing nothing, and if you are somehow blind to that truth,
the documentation should not claim otherwise.

I'm curious how this got added. It just feels like such a basic
debian thing to do: update a config file, and run stop or start
or restart on an init.d file that ran during startup. It's even
written the installation guide. I'm imagining some sadistic
maintainer thinking "I'll make it so if they rerun this command
after startup, it will succeed and do NOTHING. *evil laughter*."

A second bug: Before I figured that out, I heard we use systemd
now, so I run systemctl, see some related services, named after
specific disks or partitions if I remember right, but
starting/restarting them doesn't do anything, and nothing else I
could identify relating to /etc/crypttab that would be equivalent
to the init.d/cryptdisks.

Are we using systemctl or /etc/init.d? Apparently some things
with one, some things with the other. which for what? I have no
idea.