From owner-freebsd-stable Thu Mar 16 5:33: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wodc7-1.relay.mail.uu.net (wodc7-1.relay.mail.uu.net [199.171.54.114]) by hub.freebsd.org (Postfix) with ESMTP id 7C4E737B769 for ; Thu, 16 Mar 2000 05:33:02 -0800 (PST) (envelope-from boyd@vacationclub.com) Received: from mcnc-mdm1-ex07.marriott.com by wodc7mr0.ffx.ops.us.uu.net with ESMTP (peer crosschecked as: host036.marriott.com [162.130.1.36]) id QQigtq23475 for ; Thu, 16 Mar 2000 13:33:01 GMT Received: from oberon.vacationclub.com (172.16.24.79 [172.16.24.79]) by mcnc-mdm1-ex07.marriott.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id G7K75P1D; Thu, 16 Mar 2000 08:32:50 -0500 Received: (from boyd@localhost) by oberon.vacationclub.com (8.9.3/8.9.3) id IAA89263; Thu, 16 Mar 2000 08:32:56 -0500 (EST) (envelope-from boyd) Date: Thu, 16 Mar 2000 08:32:56 -0500 (EST) Message-Id: <200003161332.IAA89263@oberon.vacationclub.com> To: stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions In-Reply-To: References: From: Daniel Boyd Reply-To: Daniel Boyd Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Glen Gross writes: > For me the main issue is that I like my 3.4 RELEASE box so much. I don't > want to risk sacrificing it in the event that the ad devices do not work > as well as the wd devices currently in use. [some people have been > reporting problems having their ad0 devices detected during the install.] You don't need to buy another whole system if you can put another hard drive in there. I had an extra 2GB free as wd0s3, so I did my 4.0-CURRENT install there on wd0s3[a-e]. This saved me when I later forgot to run single-user for installworld of the "3.3-STABLE" to "4.0-CURRENT" upgrade on the regular wd0s1 partition -- I was able to boot to the new system partition, mount the old filesystems under /mnt, and do another "make installworld" with DESTDIR=/mnt. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message