From owner-freebsd-questions@FreeBSD.ORG Sat Oct 18 18:02:40 2003 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 9993E16A4B3 for ; Sat, 18 Oct 2003 18:02:40 -0700 (PDT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8112D43FAF for ; Sat, 18 Oct 2003 18:02:38 -0700 (PDT) (envelope-from judmarc@fastmail.fm) Received: from mail.messagingengine.com (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id 9FEF130D526; Sat, 18 Oct 2003 21:02:35 -0400 (EDT) Received: from 10.202.2.150 ([10.202.2.150] helo=mail.messagingengine.com) by messagingengine.com with SMTP; Sat, 18 Oct 2003 21:02:35 -0400 X-Epoch: 1066525355 X-Sasl-enc: pkoboyvbTCcwJ/EoWYsElw Received: from sparky (dialup-67.74.84.253.Dial1.Philadelphia1.Level3.net [67.74.84.253]) by mail.messagingengine.com (Postfix) with ESMTP id 87A0630D519; Sat, 18 Oct 2003 21:02:32 -0400 (EDT) To: "Robert H. Perry" , FreeBSD-Questions References: <3F91D517.7040100@earthlink.net> Message-ID: From: Jud Content-Type: text/plain; format=flowed; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Sat, 18 Oct 2003 21:02:31 -0400 In-Reply-To: <3F91D517.7040100@earthlink.net> User-Agent: Opera7.21/Win32 M2 build 3218 Subject: Re: Upgrade to 4.8 RELEASE 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: Sun, 19 Oct 2003 01:02:40 -0000 X-List-Received-Date: Sun, 19 Oct 2003 01:02:40 -0000 On Sat, 18 Oct 2003 20:04:39 -0400, Robert H. Perry wrote: > Hello, > > I'm making plans to upgrade from 4.7 RELEASE to 4.8 RELEASE. My > previous attempt was a binary upgrade from 4.5 to 4.7 which did not go > very well. I eventually purchased the 4.7 CD. The FreeBSD Handbook > stresses backing up the system and implies that /dump/ is a better > backup program. Chapter 12.9.8.1 of the handbook recommends having a > copy of the boot and fixit floppies available and making sure they have > all your devices, otherwise you'll need to prepare two bootable custom > floppies that contain /fdisk, disklabel, newfs, mount, /and your backup > program. It goes on to say that these programs must be statically > linked. I understand hard and soft links but I'm not familiar with > static links. The handbook also provides a script for creatinng a > bootable floppy. > > Can someone help me understand static link? Secondly, can I assume that > the script must be reviewed for likely modifications? I'm just learning > shell programming and if significant modifications are necessary, I may > end up purchasing a CD for 4.8. > > Any suggestions relative to the upgrade process is also appreciated. Unless there is a specific reason not to do so, cvsup and make world would seem to be an easier and altogether better way to go for an upgrade from one minor version number to the next. Many users do this quite routinely (e.g., I do it once every week or two). See . While this section of the Handbook talks about the "cutting edge" development branches, -CURRENT and -STABLE, the same process can be used to upgrade to a -RELEASE. Jud