Bug 1144 - Don't clear the screen before first login
Don't clear the screen before first login
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
5.2
All Linux
medium Severity low
: ---
: ---
Assigned To: David Lawrence
:
: 17854 47518 131463 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-02-13 03:25 EST by Marc MERLIN
Modified: 2007-04-18 12:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-15 15:53:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marc MERLIN 1999-02-13 03:25:54 EST
In /etc/inittab:

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

Boot messages shouldn't disappear as soon as mingetty is
launched. It makes debugging the boot process really
difficult.
Comment 1 Marc MERLIN 1999-09-13 15:47:59 EDT
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 17:43:59 EDT
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 18:19:46 EDT
*** Bug 17854 has been marked as a duplicate of this bug. ***
Comment 4 Bill Nottingham 2001-07-05 22:30:46 EDT
*** Bug 47518 has been marked as a duplicate of this bug. ***
Comment 5 Bill Nottingham 2004-09-01 12:48:15 EDT
*** Bug 131463 has been marked as a duplicate of this bug. ***
Comment 6 Daniel Reed 2004-09-01 12:58:03 EDT
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 15:53:05 EST
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.