From nobody  Wed Jul  8 17:59:56 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA26413;
          Wed, 8 Jul 1998 17:59:56 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199807090059.RAA26413@hub.freebsd.org>
Date: Wed, 8 Jul 1998 17:59:56 -0700 (PDT)
From: simon.smith19@virgin.net
To: freebsd-gnats-submit@freebsd.org
Subject: boot fails to run sysinstall, msg '/stand/sysinstall running as init on vty0'
X-Send-Pr-Version: www-1.0

>Number:         7222
>Category:       bin
>Synopsis:       boot fails to run sysinstall, msg '/stand/sysinstall running as init on vty0'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul  8 18:00:00 PDT 1998
>Closed-Date:    Wed Jul 8 18:09:36 PDT 1998
>Last-Modified:  Wed Oct 26 05:43:10 GMT 2005
>Originator:     simon smith
>Release:        2.2.6
>Organization:
Deutsche bank
>Environment:
system 386 (still tyring to boot, help)
>Description:
whilst booting, after  disabling conflicts, the system goes idle after the 
following message :
rootfs is 1440 kbyte complied in MFS
/stand/sysinstall running as init on vty0

The sysinstall program fails to run, please help

system 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Wed Jul 8 18:09:36 PDT 1998 
State-Changed-Why:  
Not enough info here for a truly meaningful analysis, though if I had 
to hazard a wild guess I'd assume that the user deleted sc0 as a "conflict" 
and ended up deleting his own console driver, leading to sysinstall 
attempting to talk to a serial device instead. 

- Jordan 
>Unformatted:
