Talk:Disable clearing of boot messages

From ArchWiki
Jump to: navigation, search

Remove quiet from GRUB_CMDLINE_LINUX_DEFAULT

It may be worth to mention removing flag quiet from GRUB_CMDLINE_LINUX_DEFAULT in /etc/defaults/grub in order to see the actual boot messages, systemd startup status, etc.. Many users may miss this important step. --Mloskot (talk) 00:19, 16 March 2013 (UTC)

+1. Suggestion: Link to Kernel parameters instead of list for specific bootloader. -- Fengchao (talk) 09:42, 19 March 2013 (UTC)
Yes, link would do, but IMO it's also important to give a note explaining that it is about enabling verbose logging of booting process --Mloskot (talk) 13:38, 19 March 2013 (UTC)
[1], closing. -- Alad (talk) 15:50, 22 August 2016 (UTC)
On legacy installations running without systemd, there is another solution. To avoid clearing the screen after boot, the /etc/inittab file must be changed. Just add a --noclear option to the getty respawn lines:
c1:2345:respawn:/sbin/agetty --noclear -8 -s 38400 tty1 linux
—This unsigned comment is by Bstocker (talk) 14:45, 29 May 2013. Please sign your posts with ~~~~!

Better use a drop-in file ?

/etc/systemd/system/getty.target.wants/getty@tty1.service is a symlink to /usr/lib/systemd/system/getty@service.

I think, it is better to create a drop-in directory /etc/systemd/system/getty@tty1.service.d/ and place this file in it to override TTYVTDisallocate only:

/etc/systemd/system/getty@tty1.service.d/noclear.conf
[Service]
TTYVTDisallocate=no

—This unsigned comment is by Frank (talk) 14:03, 7 January 2014. Please sign your posts with ~~~~!

[2], closing. -- Alad (talk) 12:56, 17 August 2016 (UTC)