--vGgW1X5XWziG23Ko
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 26, 2005 at 06:34:40PM -0500, Brian wrote:
  | so over at bsdnexus forums, we're having a discussion about the proper
  | order of the steps used to update an existing NetBSD system.
  |=20
  | http://forums.bsdnexus.com/viewtopic.php?id=3D678
  |=20
  | WIntellect claims that you should build tools, build distribution, build
  | and install kernel, reboot, and install the userland.
  |=20
  | as I've always understood it, you're supposed to build and install a new
  | kernel before doing anything else, e.g. build tools, build and install
  | kernel, reboot, build distribution, install the userland.


 non-root% ./build.sh -U distribution sets kernel=3Dfoo releasekernel=3Dfoo

 install kernel
 reboot to single user
 extract sets
 run:  postinstall -s /path/to/etc.tgz fix
 reboot


IMNSHO this is the safest way to upgrade, because with build.sh
we've separated the ``build the OS'' operation from the
``install the OS''.  Infact, you can do the build.sh on a separate
system and just transfer the appropriate kernel & sets to
each target machine as required.

(I also build sourcesets and store the contents of ${RELEASEDIR}
on a (bootable) CD-ROM.)

--vGgW1X5XWziG23Ko
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFDt0ncpBhtmn8zJHIRAnQbAJ9DXOkgDop2c7+jzcJT4nrpkGSVfQCffMTh
q2+ROi/9RJb/usrnBUAk3RI=
=qwx7
-----END PGP SIGNATURE-----

--vGgW1X5XWziG23Ko--