'Back in the good old days' when logging was to text files. When a
disk drive failed to boot, I could attach that disk drive to another
computer as a secondary drive, and then mount and read the logs to
see why it could no longer boot. As well as to inspect other
things.
(apologies that ' offline boot disk drive' might not be the best way
to describe a normally bootable disk drive that is now attached as a
secondary disk drive to a different computer. Maybe "secondary
bootable drive", or "Non-Primary Boot Drive")
Now with Journalctl, is it still possible to connect the
failed-to-boot disk drive to another computer and read logs? How?
Maybe the answer is to use -D or --directory to point to the
attached disk drives journal directory?
Takes a directory path as argument. If
specified, journalctl will operate on the specified journal
directory DIR instead of the default runtime and system
journal paths.
Added in version 187.
Example: journalctl --directory=/path/to/your/journal/
For example, journalctl --directory=/mnt/my_logs/journal
Is my interpretation of the man instructions correct?
Has anyone had the occasion to do this? And if so, does it work
well?
George.
PS I am currently using Thunderbird to try out email threading. Are
the any other good email clients that support email threading and
are packaged in Debian? Reply to: