Bug 45284 – Serial console does not work properly during init

Bug 45284 - Serial console does not work properly during init

Summary:	Serial console does not work properly during init

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	SysVinit (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	David Lawrence
Docs Contact:

URL:	http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:

Duplicates:	42280 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-06-21 03:57 EDT by Need Real Name
Modified:	2014-03-16 22:21 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-06-21 14:55:03 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2001-06-21 03:57:00 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
When init starts, it does not properly initialize the tty for serial 
consoles.  The URL explains the situation and a patch to remedy the 
problem.

How reproducible:
Always

Steps to Reproduce:
1. Configure system to support serial console.
2. Boot
3. Try to press 'I' to do an interactive startup.
4. Find that 'I' does not work through serial console.
	

Actual Results:  Nothing.

Expected Results:  Interactive startup should be envoked.

Additional info:  That's as simple as it gets.

Comment 1 Bill Nottingham 2001-06-21 14:49:14 EDT

*** Bug 42280 has been marked as a duplicate of this bug. ***

Comment 2 Bill Nottingham 2001-06-21 14:54:58 EDT

Fixed in SysVinit-2.78-17; thanks!

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