Bug 1144 - Don't clear the screen before first login
Summary: Don't clear the screen before first login
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 5.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
: 17854 47518 131463 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 1999-02-13 08:25 UTC by Marc MERLIN
Modified: 2007-04-18 16:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-02-15 20:53:05 UTC

Attachments (Terms of Use)

Description Marc MERLIN 1999-02-13 08:25:54 UTC
In /etc/inittab:

 # Run gettys in standard
+1:12345:respawn:/sbin/mingetty --noclear

Boot messages shouldn't disappear as soon as mingetty is
launched. It makes debugging the boot process really

Comment 1 Marc MERLIN 1999-09-13 19:47:59 UTC
I just realized that no reason was ever given for the discard.
I'll respect your opinion, but since my request was reasonable, maybe
you can tell me why clearing boot messages right away is a good thing?

Comment 2 Bill Nottingham 1999-09-13 21:43:59 UTC
Consistency of display across all virtual terminals.
Less ugliness on the screen.
It's the way it's always been done. ;)

In any case, the boot messages are logged in 6.0+.

Comment 3 Bill Nottingham 2000-10-02 22:19:46 UTC
*** Bug 17854 has been marked as a duplicate of this bug. ***

Comment 4 Bill Nottingham 2001-07-06 02:30:46 UTC
*** Bug 47518 has been marked as a duplicate of this bug. ***

Comment 5 Bill Nottingham 2004-09-01 16:48:15 UTC
*** Bug 131463 has been marked as a duplicate of this bug. ***

Comment 6 Daniel Reed 2004-09-01 16:58:03 UTC
This may contribute to poor bug reports and general user frustration.
At worst, this should be controlled by some easy/obvious knob. (I was
not able to determine what was causing the screen to be cleared
without asking.)

Comment 7 Bill Nottingham 2005-02-15 20:53:05 UTC
Closing out bugs on older unsupported releases.

This has been this way for so long that I don't see it really changing. It's
certainly editable in inittab for those that want otherwise; keying inittab
information off of a separate configuration flag isn't really practical, and
won't make it much more user friendly.

Note You need to log in before you can comment on or make changes to this bug.