From owner-freebsd-stable@FreeBSD.ORG Fri May 14 03:12:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF30C106566B for ; Fri, 14 May 2010 03:12:11 +0000 (UTC) (envelope-from fred@storming.org) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFE88FC18 for ; Fri, 14 May 2010 03:12:10 +0000 (UTC) Received: by fxm17 with SMTP id 17so1118373fxm.13 for ; Thu, 13 May 2010 20:12:10 -0700 (PDT) Received: by 10.239.129.197 with SMTP id 5mr77623hbg.77.1273806730143; Thu, 13 May 2010 20:12:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.148.78 with HTTP; Thu, 13 May 2010 20:11:50 -0700 (PDT) In-Reply-To: <20100514025125.GA84336@icarus.home.lan> References: <20100514025125.GA84336@icarus.home.lan> From: Fred Souza Date: Fri, 14 May 2010 00:11:50 -0300 Message-ID: To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Mount root error / New device numbering? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2010 03:12:11 -0000 On Thu, May 13, 2010 at 23:51, Jeremy Chadwick w= rote: > 1) We use csup now, not cvsup. =A0csup comes with the base system, so > =A0 there's no need to install cvsup. > > 2) I'm not sure why you're downloading ports.tar.gz and extracting it. > =A0 This means that /var/db/sup/ports-all won't match what's in > =A0 /usr/ports. =A0You should just use csup to populate /usr/ports. > =A0 You can do this by doing: > > =A0 csup -h -L 2 /usr/share/examples/cvsup/ports-supfile > > =A0 You can also populate /usr/src (and thus /var/db/sup/src-all) by > =A0 doing: > > =A0 csup -h -L 2 /usr/share/example/cvsup/stable-supfile > > =A0 There are also /etc/make.conf variables you can set to make this > =A0 process easier once you've populated /usr/ports and /usr/src; you > =A0 can do something like "cd /usr/ports ; make update". Thank you, that is something I didn't see changing. I will try that out from now on. > Well, if what you're doing is an "in-place" 7.x upgrade to 8.x, I don't > know how to do this or if it works. =A0Others can help. No, I did a fresh 8.0-RELEASE install and then tried updating it to -STABL= E. > Otherwise, the steps you're describing for building a system are not > what's in src/Makefile (not src/UPDATING). =A0These are the steps: > > # =A01. =A0`cd /usr/src' =A0 =A0 =A0 (or to the directory containing your= source tree). > # =A02. =A0`make buildworld' > # =A03. =A0`make buildkernel KERNCONF=3DYOUR_KERNEL_HERE' =A0 =A0 (defaul= t is GENERIC). > # =A04. =A0`make installkernel KERNCONF=3DYOUR_KERNEL_HERE' =A0 (default = is GENERIC). > # =A0 =A0 =A0 [steps 3. & 4. can be combined by using the "kernel" target= ] > # =A05. =A0`reboot' =A0 =A0 =A0 =A0(in single user mode: boot -s from the= loader prompt). > # =A06. =A0`mergemaster -p' > # =A07. =A0`make installworld' > # =A08. =A0`make delete-old' > # =A09. =A0`mergemaster' =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = (you may wish to use -U or -ai). > # 10. =A0`reboot' > # 11. =A0`make delete-old-libs' (in case no 3rd party program uses them a= nymore) Yeah, that is very close to what I did: # cd /usr/src # make buildworld # make kernel KERNCONF=3DLIGHTNING # reboot That was for the first install, that got completely borked after rebooting and me trying to change the contents of /etc/fstab. On this current install, I did this: # cd /usr/src # make buildworld # make kernel KERNCONF=3DLIGHTNING # mergemaster -p # make installworld # make delete-old # mergemaster -i # make delete-old-libs # reboot The reason for me to try all that before rebooting, like I said on the first e-mail, was that I thought the drive numbers changing could be related to the -STABLE kernel running on top of -RELEASE userland. All those steps ran just fine, though. But when I reboot, I still see the kernel assigning ad10 to my first drive (it's ad8 with the -RELEASE kernel) and ad16 for the second (ad14 with -RELEASE). I have no idea what is causing this change in numbering. Thanks, Fred