NetBSD Problem Report #17792

Received: (qmail 18141 invoked by uid 605); 1 Aug 2002 06:18:22 -0000
Message-Id: <>
Date: Wed, 31 Jul 2002 18:05:43 +1000 (EST)
Subject: Install process order - network verses disk
X-Send-Pr-Version: 3.95

>Number:         17792
>Category:       install
>Synopsis:       Install process order - network verses disk
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    install-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 01 06:19:00 +0000 2002
>Last-Modified:  Mon Mar 29 01:17:20 +0000 2004
>Originator:     Marc Boschma
>Release:        NetBSD 1.6_BETA4
System: NetBSD troy 1.6_BETA4 NetBSD 1.6_BETA4 (GENERIC) #0: Sun Jul 28 18:17:59 UTC 2002 i386
Architecture: i386
Machine: i386

During the install of this host I ran into the following problem.

The sysinst process committed changes to the disk before network connectivity
was known to work. This meant the previous OS was formatted away before it
was evident that the install kernel did not support the network card in the
box. Well it did and it didn't... It was not recognised correctly. ec0 as
against the old ed0 (the machine was at 1.2.1).

This was particularly problematic since the install was being done via FTP.

If it wasn't for shutting down another non-critical host to get it's
network card the machine being upgraded (primary DNS, mail hub, etc) wouldn't
have been able to be restored.

(Yes I know that there should be back ups etc., and there are, but the option
to just reboot until things could be worked out would have been nice).

Maybe the order of the network configuration and disk labeling could be

Responsible-Changed-From-To: port-i386-maintainer->install-manager 
Responsible-Changed-By: fair 
Responsible-Changed-When: Mon Mar 29 01:15:08 UTC 2004 

As I read this PR, it's asking for changes/formats/commits to disk 
to be deferred until the viability of the various device drivers in 
NetBSD is confirmed for the platform being installed, and thus this 
is really a generic installation problem, rather than specific to 

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.