drexl
asked on
Hiding messages during boot
Hi,
I have a linux Debian system with a grub boot loader where I would like to hide all the messages that is output to console during boot. I do not necessarily have to hide the output made initially by grub but rather the system information displayed after grub.
What should I do?
Sincerely
Joakim
I have a linux Debian system with a grub boot loader where I would like to hide all the messages that is output to console during boot. I do not necessarily have to hide the output made initially by grub but rather the system information displayed after grub.
What should I do?
Sincerely
Joakim
ravenpl
I'm not familiar with debian, but other systems supports "quiet" kernel option
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well,
Thank you for your suggestions.
Ravenpl: the quiet kernel option does a little, but in my case not that much.
nedvis: If I'm not mistaken, your suggestion involves downloading a new kernel. I'd rather have my own kernel.
Is there no way to just suppress the messages by somehow temporarily pointing /dev/console to /dev/null during boot?
Thank you for your suggestions.
Ravenpl: the quiet kernel option does a little, but in my case not that much.
nedvis: If I'm not mistaken, your suggestion involves downloading a new kernel. I'd rather have my own kernel.
Is there no way to just suppress the messages by somehow temporarily pointing /dev/console to /dev/null during boot?
You should try passing "quiet" parameter /option to kernel when booting system.
Usually, parameters are passed to the kernel when it is invoked from a boot file such as the GRUB or LILO configuration file ( usually located in /boot/grub/grub.conf )
Kernel boot option "quiet" will suppress/disable all log messages.
Set the default kernel log level to KERN_WARNING (4), which
suppresses all messages during boot except extremely serious ones.
(Log levels are defined under the loglevel parameter.)
Please have look at this chapter ( Kernel Boot Command-Line Parameter Reference )
http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf
for detailed instructions.
As its stated there :
"There are three ways to pass options to the kernel and thus control its behavior:
• When building the kernel. Most of this book discusses these options.
• When starting the kernel. Usually, parameters are passed to the kernel when
it is invoked from a boot file such as the GRUB or LILO configuration file.
• At runtime, by writing to files in the /proc and /sys directories."
You'll hopefully be able to get around the problem by editing grub.conf file and adding
"guiet" option to your command line for booting your kernel.
Usually, parameters are passed to the kernel when it is invoked from a boot file such as the GRUB or LILO configuration file ( usually located in /boot/grub/grub.conf )
Kernel boot option "quiet" will suppress/disable all log messages.
Set the default kernel log level to KERN_WARNING (4), which
suppresses all messages during boot except extremely serious ones.
(Log levels are defined under the loglevel parameter.)
Please have look at this chapter ( Kernel Boot Command-Line Parameter Reference )
http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf
for detailed instructions.
As its stated there :
"There are three ways to pass options to the kernel and thus control its behavior:
• When building the kernel. Most of this book discusses these options.
• When starting the kernel. Usually, parameters are passed to the kernel when
it is invoked from a boot file such as the GRUB or LILO configuration file.
• At runtime, by writing to files in the /proc and /sys directories."
You'll hopefully be able to get around the problem by editing grub.conf file and adding
"guiet" option to your command line for booting your kernel.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.