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

From ArchWiki
Jump to: navigation, search
(Remove quiet from GRUB_CMDLINE_LINUX_DEFAULT)
m (Better use a drop-in file ?: remove closed discussion)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== 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)
 
: +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>
 

Latest revision as of 15:07, 11 April 2017