From owner-freebsd-current@FreeBSD.ORG Fri Jun 25 11:40:13 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03DFC1065672 for ; Fri, 25 Jun 2010 11:40:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id AD70B8FC16 for ; Fri, 25 Jun 2010 11:40:12 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.4/8.14.4) with ESMTP id o5PBeBvJ035286 for ; Fri, 25 Jun 2010 04:40:11 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.4/8.14.4/Submit) id o5PBeBQu035285 for current@freebsd.org; Fri, 25 Jun 2010 04:40:11 -0700 (PDT) (envelope-from david) Date: Fri, 25 Jun 2010 04:40:11 -0700 From: David Wolfskill To: current@freebsd.org Message-ID: <20100625114011.GO90096@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FTsVDVnBYKo0tCDH" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: Use of boot0cfg to set boot slice broke between r209459 and r209502 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2010 11:40:13 -0000 --FTsVDVnBYKo0tCDH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Well, one one of my machines -- I realize that there are some machines for which it's been problematic for a while. And all of the machines I'm using run FreeBSD/i386. But it had been working on my build machine since I acquired it (a few months ago) in daily use. Of course, I didn't notice the effect, as after I finished building & smoke-checking head on the build machine, I power it off, via: sudo boot0cfg -s 2 aacd0 && sudo shutdown -p now || sudo shutdown -r now (as leaving it on generates too much noise and heat). And when I powered it up last night (in preparation for the nightly update of my local mirrors and the start of the morning's builds), I failed to note that it was running head, vs. stable/7 (as I had intended). A similar use of boot0cfg on my laptop remains working. Here are the respective "uname -a" outputs from the build machine: FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #198 r2094= 59: Wed Jun 23 06:05:16 PDT 2010 root@freebeast.catwhisker.org:/usr/obj= /usr/src/sys/GENERIC i386 FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #199 r2095= 02: Thu Jun 24 05:41:59 PDT 2010 root@freebeast.catwhisker.org:/usr/obj= /usr/src/sys/GENERIC i386 (As you can see, I run a GENERIC kernel on the build machine.) I've placed a copy of a recent stable/7 dmesg.boot in ; when I next boot CURRENT, I'll grab dmesg.boot & stuff it in . (That should be within a few hours.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --FTsVDVnBYKo0tCDH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwklZoACgkQmprOCmdXAD0WIQCfVUneHes83yxuXIv76pE0q7V3 MF8AmwUlNgjr+rYs4EGDwf+EnDw3PIoL =hyAb -----END PGP SIGNATURE----- --FTsVDVnBYKo0tCDH--