LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 12-23-2001, 04:56 PM   #1
aethereal
Member
 
Registered: Dec 2000
Location: Seattle
Distribution: Red Hat 8.0
Posts: 41

Rep: Reputation: 15
Question suppressing boot output to terminal


How can I suppress all of the output that occurs during the boot process (e.g., lilo) from appearing on my terminal screen?

Let's suppose my system boots normally:
All of the output that occurs during the boot process appears to be logged to /var/log/boot.log (among other places), so I don't feel that I need to watch this output streaming past my eyes every time I startup.

So, how can I simply suppress all of this output that is displayed on my terminal screen during the boot process?

Thanks,
Ben
 
Old 12-23-2001, 05:44 PM   #2
bluecadet
Member
 
Registered: Oct 2001
Distribution: MD81 RH71
Posts: 555

Rep: Reputation: 30
ok, so a critical module fails for some totally unknown reason.. then what? it's really not the kind of thing that a linux user wants to do. if you want to hide away all the nasty stuff, then i'd recommend using mandrake as that lilkes to put a really patronising picture on the screen to hide it all, which most linux users would hate.. might suit you tho, if you really want to make it all so pretty.

I don't think it's at all possible to hide the boot up, as no one ever thought it'd be a worthwhile thing to do. what if fsck kicks in and does a check... you could easily have recurring errors affecting your system that you have no idea about. it's really not a good idea i don't think.
 
Old 12-23-2001, 09:29 PM   #3
aethereal
Member
 
Registered: Dec 2000
Location: Seattle
Distribution: Red Hat 8.0
Posts: 41

Original Poster
Rep: Reputation: 15
It's interesting: You raised exactly the sort of issue I had been thinking
about. It had occurred to me that startup could fail and then one would have no
way of knowing what went wrong without having a working system with which to
check /var/log/boot.log, for example. However, would knowing what went wrong
necessarily change anything? (Perhaps yes. I'm just asking this question
rhetorically for now.) That is to say, if something failed on
startup one would necessarily be able to fix it without being able
to successfully boot into a working system, even if one did know precisely what
did fail? (I would guess yes, but mainly because the system does (by default)
bother spewing all of the startup diagnostics and you, for example, suggest that
this could be vital.)

Some additional comments, however:
1. Just to be perfectly clear, I'm not necessarily interested in "seeing a
pretty picture" instead of watching startup diagnostics. This whole issue has
nothing to do with aesthetics for me. In my case, it just literally irritates
my eyes to track text that scrolls by superfast. (e.g., I almost never scroll
down any pages. I almost always page down, instead.)
2. But, for that matter, what would be wrong with displaying a "pretty picture"
instead of outputting diagnostic information, so long as that info is somehow
accessible in the event of failure. To use an analogy, when Windows starts up,
I do not see reams of diagnostic info flying by. However, I doubt that, in
the event of startup difficulties in Windows, a user would be completely without
any means of diagnosing what might be the matter. From this standpoint, I do
somewhat question your suggestion that without spewing all of the boot output a
user could not possibly diagnose what might have gone wrong. (If Windows
(probably) has some means of doing this), why not Linux?)

Another idea: Why not simply startup ~without~ displaying all of the diagnostic
info by default. And simply have an option, upon startup, of a "verbose"
startup that displays all that sh*t, in the event startup fails, or the user
would simply like to see it.

Btw (and this does go back to the aesthetics/"pretty picture" idea): If I
~were~ in charge of tweaking Linux for the widest possible audience, I would
definitely not have that kind of diagnostic info flying by. It certainly seems
very unnecessary/non-optimal to me.

Ben
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Redirect terminal output to file AND terminal shan Linux - General 3 09-29-2006 09:36 AM
Squid Output to the Terminal? mattsthe2 Linux - Networking 5 10-27-2005 03:02 PM
Suppressing the output from tar marri Programming 2 05-03-2005 04:19 AM
how to redirect the output of a terminal? cpukiller Linux - Networking 5 11-10-2004 08:07 AM
Stupid question... too much output in terminal Darx Linux - Newbie 4 04-15-2004 10:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:04 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration