5 May
2017
5 May
'17
11:22 a.m.
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, May 5, 2017 at 9:56 AM, deloptes <deloptes(a)gmail.com> wrote:
Felix Miata wrote:
Thank you Felix for the explanation
because something may go wrong with the login manager. filesystem
corruption could result, meaning that the login manager completely
fails and will not permit a login of any kind (i have actually
genuinely had this happen: it turned out to be that /home was not
writeable), and you would otherwise need to take the drastic action of
rebooting into "init 1" to recover...
BUT...
let's assume that there are mission-critical files still being served
up from the machine: other users (over a network) are connected to
something on the machine (its printers, whatever doesn't matter) so
you CAN'T just reboot it...
i would expect under these circumstances to just be able to press
"Ctrl-Alt-F1" and to log in at a text console as root.
if that's *not possible* then it's a severe bug.
l.
So, the subject question is whether this absence
of difference between
multi-user.target and graphical.target using TDE on Stretch is expected
and normal?
If it does something that is not expected, it is obviously not normal.
Someone log a bug, add a patch and it is done.
Perhaps no one tested multi user aka no graphical.target ... For example if
I install TDE, I expect it to come up with login manager ... why would I
still expect a console login, when I have installed TDE?