EDIT 2
Perhaps LineMax= parameter in journal configuration can force line breaks that are reflected during the boot process itself
(source).
I did not try that.
"Note that values below 79 are not accepted and will be bumped to 79."
(I am not sure this suits you).
EDIT
By default, journalctl truncates lines longer than screen width, but in some cases, it may be better to enable wrapping instead of truncating. This can be controlled by the SYSTEMD_LESS environment variable, which contains options passed to less (the default pager) and defaults to FRSXMK (see less(1) and journalctl(1) for details).
By omitting the S option, the output will be wrapped instead of truncated. For example, start journalctl as follows:
$ SYSTEMD_LESS=FRXMK journalctl
To set this behaviour as default, export the variable from ~/.bashrc or ~/.zshrc.
(source).
With journalctl you can view system logs (albeit after, not during, boot).
Use journalctl --list-boots to see details on recorded boots, including hashes/boot ID (you should have enabled the persistent storage of log messages).
Then use journalctl /usr/lib/systemd/systemd -b <boot ID> to view system log for a specific boot process (or the current one if boot ID is omitted). You can also use -1 e.g. instead of the boot ID, to see the previous boot.
While viewing a log, you can use left and right arrows to view complete lines.
Also, sudo less -R /var/log/boot.log.1, or other log files.
Is that enough for you?
Related
- https://freedesktop.org/wiki/Software/systemd/Debugging/
- https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
- https://unix.stackexchange.com/questions/229188/journalctl-how-to-prevent-text-from-truncating-in-terminal
