Subject: port-i386/17792: Install process order - network verses disk
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 07/31/2002 18:05:43
>Synopsis: Install process order - network verses disk
>Arrival-Date: Wed Jul 31 23:19:00 PDT 2002
>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 firstname.lastname@example.org:/autobuild/i386/OBJ/autobuild/src/sys/arch/i386/compile/GENERIC 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