Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!oleane!jussieu.fr!math.ohio-state.edu!cis.ohio-state.edu!nntp.sei.cmu.edu!bb3.andrew.cmu.edu!andrew.cmu.edu!rnw+
From: Robert N Watson <rnw+@andrew.cmu.edu>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: FreeBSD 2.1 upgrade path from 2.0.5
Date: Mon, 2 Oct 1995 23:37:05 -0400
Organization: Freshman, H&SS Undeclared, Carnegie Mellon, Pittsburgh, PA
Lines: 23
Message-ID: <ckQ_zVG00YUw4iJ1ti@andrew.cmu.edu>
NNTP-Posting-Host: po6.andrew.cmu.edu
This has probably been discussed/beaten to death on many of the mailing
lists (eg., hackers, questions, etc), but apparently I missed the
debate.. What sort of upgrade path are FreeBSD 2.0.5 servers looking at
to get to 2.1? I run servers for NIS, the WWW, Samba, POP, etc, and
would prefer to minimize downtime and reconfiguration and reinstallation
time on software.. Are we now looking at essentially a plain vanilla
overwrite and restore from files like some unmentioned previous
upgrades, or do we actually get a nice happy upgrade wherein it finds
the bin dist binaries, overwrites them, deals with the kernel, devices,
and generic /etc stuff (rc stuff is fine, just not my passwd stuff, and
samba stuff, etc ;).
Any advice as to how this will work so I can schedule around it without
zapping my system (and my user base) trying it for the first time would
be appreciated. I know some discussion of an upgrade program was in
question, but that was months ago and I've been out of touch since.
Thanks,
Robert Watson
----
Robert Watson (rnw+@andrew.cmu.edu) * Double major: IDS/CS * H&SS
http://www.watson.org/ robert@fledge.watson.org