From owner-freebsd-questions@FreeBSD.ORG Tue Nov 22 18:36:19 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F19711065670 for ; Tue, 22 Nov 2011 18:36:19 +0000 (UTC) (envelope-from frank@esperance-linux.co.uk) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by mx1.freebsd.org (Postfix) with ESMTP id 6C1018FC0C for ; Tue, 22 Nov 2011 18:36:18 +0000 (UTC) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id pAMIaHZf007403 for ; Tue, 22 Nov 2011 18:36:17 GMT Received: from orange.esperance-linux.co.uk (host-92-22-121-215.as13285.net [92.22.121.215]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id pAMIaHRK007392 for ; Tue, 22 Nov 2011 18:36:17 GMT Received: by orange.esperance-linux.co.uk (Postfix, from userid 1001) id D716833C1F; Tue, 22 Nov 2011 18:36:16 +0000 (GMT) Date: Tue, 22 Nov 2011 18:36:16 +0000 From: Frank Shute To: FreeBSD Questions Message-ID: <20111122183616.GA4124@orange.esperance-linux.co.uk> References: <20111122164045.GA25322@itcom245.staff.itd.umich.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <20111122164045.GA25322@itcom245.staff.itd.umich.edu> User-Agent: Mutt/1.4.2.3i X-Face: *}~{PHnDTzvXPe'wl_-f%!@+r5; VLhb':*DsX%wEOPg\fDrXWQJf|2\,92"DdS%63t*BHDyQ|OWo@Gfjcd72eaN!4%NE{0]p)ihQ1MyFNtWL X-Operating-System: FreeBSD 8.2-STABLE amd64 X-Organisation: 'shute.org.uk' Subject: Re: where to ask about problems with bsdinstall in 9.0RC2? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frank Shute List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2011 18:36:20 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2011 at 11:40:45AM -0500, William Bulley wrote: > > According to Ian Smith on Sat, 11/19/11 at 13:29: > >=20 > > Unfortunately that concentrates on creating a GPT layout, encouraging a= =20 > > Linux-like single (plus a boot) partition - forget using dump/restore - > > and says nothing much about installing over an existing setup with MBR= =20 > > partitioning and multiple slices, a not uncommon setup on many existing= =20 > > laptops .. eg here I want to install over a previous 7.2-RELEASE 60GB= =20 > > slice partitioned as I want it - 1GB /, 4GB /var, 16GB /usr and ~37GB= =20 > > /home. Further, I want to preserve /home as is, despite having backups. > >=20 > > sysinstall's partitioning is more sophisticated; you get to specificall= y=20 > > toggle on or off newfs'ing each partition, as well as specifying newfs= =20 > > options if you want. So it's clear whether you'll be newfs'ing / and= =20 > > which other partitions, and which you'll be leaving alone, eg /home. > >=20 > > On BETA1 I recorded "Extract Error while extracting base.txz: can't set= =20 > > user=3D0/group=3D0 for /var/empty Can't update time for /var/empty .." = which=20 > > someone/s else also reported, which turned out to be misleading .. the= =20 > > basic problem is that the filesystem isn't empty, ie as after newfs. >=20 > I hate to be a pest about this, but bsdinstall just isn't working for me. > I grabbed the 9.0RC2 bootonly ISO for i386 and tried again to load this > onto this Dell laptop. This time the *.txz files had to be gotten over > the network which took longer that with the DVD1 ISO. :-( >=20 > The files were fetched, and checked/verified, then the actual installation > (extraction) began. Unfortunately, I got the same error pop-up message. > This time I have the exact text of that error message: >=20 > "Error while extracting base.txz: Can't > set user=3D0/group=3D0 for var/emptyCan't > update time for var/empty" >=20 > Note the missing space or CR before the second "Can't" >=20 > What confused me at first was the missing slash ("/") character before the > two "var" pathnames. But I now understand that is because I am updating > (not installing) from a previously working (was 8.2-STABLE in this case) > system where the four partitions (root, swap, /var, and /usr) are present > and full of FreeBSD files, etc. >=20 > If this is a "feature" of bsdinstall, then it should be mentioned in the > documentation somewhere. I used the "Manual" configuration method where > I was asked to name the mount points for root, /var and /usr. My question > is this: "if bsdinstall can't handle installing over top of an already > existing system on disk, then why ask the user for mount points on those > already existing partitions?" This seems weird to me. >=20 > So now I am back to square one. I want to load 9.0RC2 onto this laptop > for reasons that aren't relevant to this thread, yet I am unable to do > so because as of 9.0 sysinstall has been replaced by bsdinstall. =20 >=20 > For the record, how do I upgrade to 9.0RC2 (or any 9.0 variant) from a > system already running 8.2-STABLE? Had this attempt been using the > sysinstall method, I would have long since been up and running FreeBSD > 9.x on this laptop. Please advise. Thanks in advance. Can't help you with your bsdinstall woes but to upgrade from 8.2-STABLE to 9.0-RELEASE(currently RC2) branch you want to do a csup(1)/buildworld cycle. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html You should use the tag: *default release=3Dcvs tag=3DRELENG_9_0 in your supfile. More details at: http://www.shute.org.uk/misc/freebsd_uptodate.html Regards, --=20 Frank Contact info: http://www.shute.org.uk/misc/contact.html --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk7L658ACgkQHduKvUAgeK4zfwCgnUymYXlXNelEb7INBCJ0F9Tx HnMAoIoLc3DdX6dNDUCpPzZPOZadyD26 =oPWg -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--