On Tue, Sep 06, 2005 at 11:00:34AM +0100, Stuart Henderson wrote:
> There doesn't have to be so much difference, actually. With OpenBSD an
> upgrade is usually pretty straightforward. The main part of the process
> (boot from bsd.rd, run the 'upgrade' process) can equally be used for
> patches and upgrades. With an upgrade the initial step is to read
> updateXX.html, with a patch you can first create distribution *.tgz
> files using 'make build' and 'make release' and host them on local ftp
> (a bit of overkill for one or two machines, but invaluable on a larger
> network).
I usually do it the other way. dirty, but works most of the time.
minimal downtime for sure.
pkg_info | awk '{print $1}' > packages-2keep
vi packages-2keep ; leave the bare minimum which will bring the rest
; as dependencies
mkdir /old
mv /bsd /bsd.old
mv bsd /bsd
cp -R /bin /sbin /old/
export PATH=/old/sbin:/old/bin:$PATH
for file in man* comp* base*; do tar -zvxpf $file -C/; done
reboot
then - or pkg_add according to packages-2keep, or ports rebuild
for non-kernel issues tar -zvxpf ... -C/ works like a charm. :-)
--
Igor "CacoDem0n" Grabin, http://violent.death.kiev.ua/
