Difference between revisions of "Talk:Disable clearing of boot messages"

From ArchWiki
Jump to: navigation, search
(Add GRUB_CMDLINE_LINUX_DEFAULT)
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
cd /etc/systemd/system/getty.target.wants
 
rm getty\@tty1.service
 
cp /usr/lib/systemd/system/getty\@.service getty\@tty1.service
 
[[User:Bwid|Bwid]] ([[User talk:Bwid|talk]]) 12:05, 1 March 2013 (UTC)
 
: Please make it clear what those command is doing. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 00:53, 7 March 2013 (UTC)
 
 
 
== Remove quiet from GRUB_CMDLINE_LINUX_DEFAULT ==
 
== Remove quiet from GRUB_CMDLINE_LINUX_DEFAULT ==
  
 
It may be worth to mention removing flag <code>quiet</code> from <code>GRUB_CMDLINE_LINUX_DEFAULT</code> in <code>/etc/defaults/grub</code> in order to see the actual boot messages, systemd startup status, etc.. Many users may miss this important step. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 00:19, 16 March 2013 (UTC)
 
It may be worth to mention removing flag <code>quiet</code> from <code>GRUB_CMDLINE_LINUX_DEFAULT</code> in <code>/etc/defaults/grub</code> in order to see the actual boot messages, systemd startup status, etc.. Many users may miss this important step. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 00:19, 16 March 2013 (UTC)
 +
: +1. Suggestion: Link to [[Kernel parameters]] instead of list for specific bootloader. -- [[User:Fengchao|Fengchao]] ([[User talk: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 --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 13:38, 19 March 2013 (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 <code>--noclear</code> option to the getty respawn lines:
 +
 +
<code>c1:2345:respawn:/sbin/agetty '''--noclear''' -8 -s 38400 tty1 linux</code>
 +
 +
== Better use a drop-in file ? ==
 +
<code>/etc/systemd/system/getty.target.wants/getty@tty1.service</code> is a symlink to <code>/usr/lib/systemd/system/getty@service</code>.
 +
 +
I think, it is better to create a drop-in directory <code>/etc/systemd/system/getty@tty1.service.d/</code> and place this file in it to override <code>TTYVTDisallocate</code> only:
 +
{{hc|1=/etc/systemd/system/getty@tty1.service.d/noclear.conf|2=
 +
[Service]
 +
TTYVTDisallocate=no
 +
}}

Latest revision as of 15:17, 1 July 2014

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)

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

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