From nobody@FreeBSD.ORG Mon Aug  9 18:08:34 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 8CD5D15383; Mon,  9 Aug 1999 18:08:34 -0700 (PDT)
Message-Id: <19990810010834.8CD5D15383@hub.freebsd.org>
Date: Mon,  9 Aug 1999 18:08:34 -0700 (PDT)
From: jzwiebel@cisco.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: after installation on system using COM1, kernel won't allow login
X-Send-Pr-Version: www-1.0

>Number:         13051
>Category:       i386
>Synopsis:       after installation on system using COM1, kernel won't allow login
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug  9 18:10:00 PDT 1999
>Closed-Date:    Fri Nov 16 15:01:01 PST 2001
>Last-Modified:  Fri Nov 16 15:01:47 PST 2001
>Originator:     John Zwiebel
>Release:        3.2 RELEASE
>Organization:
Cisco
>Environment:
ip1-pc# uname -a
FreeBSD ip1-pc.cisco.com 3.2-RELEASE FreeBSD 3.2-RELEASE #1: Mon Aug  9 22:10:30 PDT 1999     root@ip1-pc2.cisco.com:/usr/src/sys/compile/HEADLESS  i386

>Description:
On a PC with no keyboard or mouse or video,
After installing a kernel from ftp.freebsd.org using boot floppies, 
when the system reboots, it will not allow login on the COM1 port.
I was able to use a Cntl-C during the boot process to come up 
single user and modify the /etc/ttys file.  
>How-To-Repeat:
Need a PC with no keyboard or video or mouse, only a com1 port.
Then install FreeBSD.  There wasn't anything obvious that I could
configure in /stand/sysinstall to get around this.
>Fix:


>Release-Note:
>Audit-Trail:

From: "Chris D. Faulhaber" <jedgar@fxp.org>
To: freebsd-gnats-submit@freebsd.org, jzwiebel@cisco.com
Cc:  
Subject: Re: i386/13051: after installation on system using COM1, kernel
 won't allow login
Date: Mon, 9 Aug 1999 22:01:02 -0400 (EDT)

 1) If the machine has network access, use the configure portion of the
 install to add a user in the wheel group, telnet in after the install, su,
 and edit /etc/ttys.
 2) Edit /etc/ttys during the install on the holographic shell (ttyv3).
 
 
 

From: "John M. Zwiebel" <jzwiebel@cisco.com>
To: "Chris D. Faulhaber" <jedgar@fxp.org>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/13051: after installation on system using COM1, kernel won't allow login 
Date: Mon, 09 Aug 1999 19:05:20 -0700

 My attempts at doing this kept failing to configure the network correctly 
 on reboot.  This could have bee me being fat-fingered somehgow
  ^ 1) If the machine has network access, use the configure portion of the
  ^ install to add a user in the wheel group, telnet in after the install, su,
  ^ and edit /etc/ttys.
 
 
 The following is not an option because the holographic shell doesn't work
 over my commserver connection to COM1.
  ^ 2) Edit /etc/ttys during the install on the holographic shell (ttyv3).
  ^ 
  ^ 
 Thanks
 
 ------------------------------------------------------------------------------
 	John Zwiebel                       Phone: 408-526-5303
 	Cisco Systems Inc.                 
 	IP Multicast Group                   
 
 
State-Changed-From-To: open->closed 
State-Changed-By: jedgar 
State-Changed-When: Fri Nov 16 15:01:01 PST 2001 
State-Changed-Why:  
sysinstall in recent 4.x releases contains support for modifying 
/etc/ttys during an install. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=13051 
>Unformatted:
