Bug 6638

Summary: Init Doesn't Echo Startup messages to terminal
Product: [Retired] Red Hat Linux Reporter: woody
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-24 04:33:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description woody 1999-11-02 05:47:31 UTC
Computer is configured (via lilo boot params) to echo
kernel messages to terminal. This works, but Init (version
2.74) does not echo the nice subsytem startup messages to
the terminal, but instead to tty1, leaving the terminal
looking like the computer has hung, because there is a huge
time gap between the last kernel message (Freed XX Memory)
and the login prompt.


Comment 1 Bill Nottingham 1999-11-22 16:37:59 UTC
What boot parameters are you using?

Comment 2 woody 1999-11-22 23:57:59 UTC
26 [~]@es-dns (admin)> more /etc/lilo.conf
append="console=ttyS0,9600n8 console=tty0"
27 [~]@es-dns (admin)>

Comment 3 Chris Siebenmann 1999-11-23 23:30:59 UTC
This is the unfortunate expected behavior. The problem is that
while LILO and the kernel have a notion of multiple nominal
consoles that can all be active simultaneously, the /dev/console
that program output goes to can only go to one place. One can
send it to the serial port, or to a console screen such as
/dev/tty0, but not both at once.

Comment 4 woody 1999-11-24 05:44:59 UTC
Apparently, the last console given to the kernel is the one that /dev/console
will eventually point to:


append="console=ttyS0,9600n8 console=tty0"


append="console=tty0 console=ttyS0,9600n8"

give reverse results.