Date: Tue, 25 Apr 2006 21:42:57 +0300 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: hans@lambermont.dyndns.org (Hans Lambermont) Cc: Frank Laszlo <laszlof@vonostingroup.com>, freebsd-ports@freebsd.org Subject: Re: libtool upgrade, entry 20060223 in UPDATING Message-ID: <20060425214257.6648ca76@it.buh.tecnik93.com> In-Reply-To: <20060425182639.GC1351@leia.lambermont.dyndns.org> References: <20060425154800.GB1351@leia.lambermont.dyndns.org> <444E4624.6070509@vonostingroup.com> <20060425182639.GC1351@leia.lambermont.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Apr 2006 20:26:39 +0200 hans@lambermont.dyndns.org (Hans Lambermont) wrote: > Frank Laszlo wrote: > > > Hans Lambermont wrote: > >> The 20060223 entry in UPDATING suggests that the only reliable way of > >> upgrading a system is to remove all packages and reinstalling from > >> scratch. > ... > >> Next to that I'd like to hear from others how to accomplish this > >> all-ports upgrade on servers where one wants the downtime to be > >> minimal. > > > > portupgrade -afp isnt good enough? > > No, I want to have minimal downtime of the server. When using > 'portupgrade -afp' the system is in flux for almost a week. I want to > avoid that, and the only way I know how to avoid that is to use a > staging and build server (at least that's the idea). If you can build your ports on an non-production server, use portugrade -PP with modified package site in pkgtools.conf If you can afford that non-production server the fastest way is to delete all installed packages and build them all from scratch. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #17: fat electrons in the lines
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060425214257.6648ca76>