From owner-freebsd-isp Wed Jan 12 8:24:34 2000 Delivered-To: freebsd-isp@freebsd.org Received: from tetron02.tetronsoftware.com (ftp.tetronsoftware.com [208.236.46.106]) by hub.freebsd.org (Postfix) with ESMTP id 948AF14BB7 for ; Wed, 12 Jan 2000 08:24:31 -0800 (PST) (envelope-from zeus@tetronsoftware.com) Received: from tetron02.tetronsoftware.com (tetron02.tetronsoftware.com [208.236.46.106]) by tetron02.tetronsoftware.com (8.9.3/8.9.3) with ESMTP id KAA18767; Wed, 12 Jan 2000 10:28:06 -0600 (CST) (envelope-from zeus@tetronsoftware.com) Date: Wed, 12 Jan 2000 10:28:06 -0600 (CST) From: Gene Harris To: Victor Meirans Cc: FreeBSD ISP mailing list Subject: Re: Upgrading FreeBSD 3.2 -> 3.4 In-Reply-To: <387C9293.AFB6019D@rezekne.lv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 12 Jan 2000, Victor Meirans wrote: > Hello, > > I am going to upgrade my 3.2 box to 3.4 pretty soon. > Anyone who did this? How it went? Are there ahy things I should consider > before doing it? > > Thanks in advance... > -- > ---> ViC <--- > > --==> Rezekne Internet Service Center http://www.risc.lv > "PCT Latgale" Ltd. Phone: +371-4622972 > Baznicas 17, Rezekne, Fax: +371-4622972 > LV-4601, Latvia GSM: +371-9577569 > -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- > I did a simple upgrade using source code only. I grabbed one of the late December source code images from releng3.freebsd.org. I compiled a new kernel first, then did a make buildworld && make installworld. Then I merged any changes in /etc/default/rc.conf with the version in the source image. I also search for any new files to for inclusion in etc. I held my breath and rebooted. Took about 2 hours, never missed a beat. My ppp came up no problem, postgre and apache all startup up with no problem. I have heard of a lot of problems when trying to upgrade from binaries. Gene Harris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message