From nobody@FreeBSD.ORG  Mon Jun  5 08:34:24 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 309E837BEEC; Mon,  5 Jun 2000 08:34:24 -0700 (PDT)
Message-Id: <20000605153424.309E837BEEC@hub.freebsd.org>
Date: Mon,  5 Jun 2000 08:34:24 -0700 (PDT)
From: msal@ednixon.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Installer assumes /dev exists if target disk has a filesystem on it.
X-Send-Pr-Version: www-1.0

>Number:         19025
>Category:       misc
>Synopsis:       Installer assumes /dev exists if target disk has a filesystem on it.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 05 08:40:04 PDT 2000
>Closed-Date:    Fri Jan 18 08:14:39 PST 2002
>Last-Modified:  Fri Jan 18 08:15:33 PST 2002
>Originator:     Mort Salazar
>Release:        4.0-release (iso image)
>Organization:
>Environment:
>Description:
standalone sysinstall makes invalid assumption that a hard disk
with a filesystem on it must include /dev, then tries to use
devices like the cdrom, though the nonexistent /dev entry,
and fails.  Means you can spend much time replacing the files
that were on the disk later.  In order to make the install actually
work, the disk needs to be blank.  Not clear what an upgrade install
would do on a disk with no prior operating system on it, or a disk
with, for example, with missing or wrong  major/minor numbers on
/dev entries (say, restored from some alien unix system).
>How-To-Repeat:
create a filesystem on a new second hard disk, and put some files on it,
but no /dev
go about installing 4.0-release on that hard disk.
the installer will fail to mount the cdrom drive, because it 
proudly announces it assumes /dev must exist because there's
a filesystem on it already, and then can't find the cd device.
>Fix:
do a MAKEDEV acd  and MAKEDEV cd  in the install scripts, probably
also for whatever other devices could be needed for installation.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Sat Jul 21 20:07:30 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19025 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Jan 18 08:14:39 PST 2002 
State-Changed-Why:  
Automatic feedback timeout.  If additional feedback that warrants 
the re-opening of this PR is available but not included in the 
audit trail, please include the feedback in a reply to this message 
(preserving the Subject line) and ask that the PR be re-opened. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19025 
>Unformatted:
