Dear Maintainer,

  my first exposure to systemd, systemd concepts, and
a failing boot was yesterday.  so i'm seeing things with
a fresh view of things and seeing it from the view of a
normal user.

  regarding bug 757072 and many other similar issues as
i read through the bug reports relating to information
collection, shell access during fatalities, and hoping to help
cut down in many future bug reports on similar topics.

  - when failing start the terminal mentioned by:

http://www.freedesktop.org/wiki/Software/systemd/Debugging/

"If You Get No Shell
....
Tip: If you find yourself in a situation where you cannot use systemctl (e.g.
when setting this up from a different booted system), you can enable the
service manually:

cd $PATH_TO_YOUR_ROOT_FS/etc/systemd/system
mkdir -p sysinit.target.wants
ln -s /usr/lib/systemd/system/debug-shell.service sysinit.target.wants/

Once enabled, the next time you boot you will be able to switch to tty9 using
CTRL+ALT+F9 and have a root shell there available from an early point in the
booting process. You can use the shell for checking the status of services,
reading logs, looking for stuck jobs with systemctl list-jobs, etc.
"
  such a thing should be possible to do on the fly and for the current failing
boot only and thus avoid interfering with the CTR-ALT-F1 - Fn terminals.
saying why such a thing happens is nice for the user.  using such a
terminal to interact with the user before ultimately failing is much more
preferable to failing, especially when failing ends up with the system
unbootable and the Debian rescue mode also is broken.

  turning on such things as persistent logs, non-quiet boots, etc. only for
the current or next boot should also be possible.  again, ask and then
do.

  thus providing some idea of what is going on and more information.

  actually the above link contains basic information that should be in a
prominent section of the systemd man pages.  online documents are
useful only to people who can get to the internet...  it took me some
time to figure out how to boot and get more info (altering the grub
boot line is not something a normal user is going to understand right
away.

  best to add to the grub menu itself to add the more noisy options
and the step-by-step ask/response for booting or the option to boot
to a non-secure shell (to avoid colliding with the Debian Rescue mode
prompts or the CTL-ALT_Fn terminals.

  the other point is to scan fstab upon installation and to mention
or suggest potential items to change.

thanks, cheers