From owner-freebsd-questions@FreeBSD.ORG Tue Sep 21 18:02:58 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1E3A16A4CF for ; Tue, 21 Sep 2004 18:02:58 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3917C43D39 for ; Tue, 21 Sep 2004 18:02:58 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 4AFFEB81E for ; Tue, 21 Sep 2004 13:02:57 -0500 (CDT) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96938-10 for ; Tue, 21 Sep 2004 13:02:55 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 4F52EB808 for ; Tue, 21 Sep 2004 13:02:55 -0500 (CDT) From: Kirk Strauser To: freebsd-questions@freebsd.org Date: Tue, 21 Sep 2004 13:02:48 -0500 User-Agent: KMail/1.7 References: <451E9011-0BF5-11D9-B049-000393934006@npc-usa.com> In-Reply-To: <451E9011-0BF5-11D9-B049-000393934006@npc-usa.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3566926.ZW7N1EQEIX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409211302.51160.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: Re: Port upgrading - my way X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 18:02:58 -0000 --nextPart3566926.ZW7N1EQEIX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 21 September 2004 12:40, Curtis Vaughan wrote: > Then I run: > > portupgrade -a > > That's it. You missed the most important middle step: less /usr/ports/UPDATING to see what critical changes have been made in the meantime that will affec= t=20 your system. For example, the www/apache2 port recently disabled the=20 various mod_proxy modules by default. Since my company's site depends on=20 those, I would have been in a mess if I hadn't planned to handle that=20 change before running the portupgrade. =2D-=20 Kirk Strauser --nextPart3566926.ZW7N1EQEIX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBBUGzL5sRg+Y0CpvERAoUIAKCPkcvaYkgQvr6aldgRfprRuDEyvACdGMyb gqWVLkGdwjgWCoTjsW0V5xM= =8LzJ -----END PGP SIGNATURE----- --nextPart3566926.ZW7N1EQEIX--