On 12/10/16 01:31, Craig Sanders via luv-main wrote: ...
it's really annoying to have to wait and watch those damn stars when you just wnat to get a shell and start investigating & fixing whatever's gone wrong.
There should be an easy and obvious way to display those binary logs from the system when it's not running systemd or from another system (IE logs copied from another system).
On my todo list. It happens when I boot after failing to alter fstab to match the actual disks connected.
yep. can you even access journald logs if you're booted up with a rescue disk? (genuine question, i don't know the answer but figure it's one of the things i need to know)
Good question - went and looked: systemctl -b -1 will pull up the log from the boot before the rescue boot. --list-boots will give you the history in the database.