Bug 1602 – mgetty fails with null modem

Bug 1602 - mgetty fails with null modem

Summary:	mgetty fails with null modem

Status:	CLOSED NOTABUG

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-03-18 11:47 EST by David Lawrence
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-03-23 14:27:02 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Derek Tattersall 1999-03-18 11:47:45 EST

Using mgetty -r and minicom, mgetty does not print
/etc/issue to the minicom screen.

Comment 1 Preston Brown 1999-03-23 14:27:59 EST

Do you get the issue file after you press enter a number of times?
Are you sure the connection is established?  The man page / info page
states that the issue file will not be printed until mgetty is sure
that the connection is established when '-r' is used, so I suspect
that this is the intended behaviour.  Please read the info page, and
if your experience is different than described, reopen the bug with
more information.

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