Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1602 - mgetty fails with null modem
Summary: mgetty fails with null modem
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mgetty
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-03-18 16:47 UTC by David Lawrence
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-03-23 19:27:02 UTC

Attachments (Terms of Use)

Description Derek Tattersall 1999-03-18 16:47:45 UTC
Using mgetty -r and minicom, mgetty does not print
/etc/issue to the minicom screen.

Comment 1 Preston Brown 1999-03-23 19:27:59 UTC
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.