From owner-freebsd-current@FreeBSD.ORG Fri Jun 25 18:01:31 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79F7E106566B; Fri, 25 Jun 2010 18:01:31 +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 3FA1D8FC1D; Fri, 25 Jun 2010 18:01:30 +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 o5PI1UVZ039244; Fri, 25 Jun 2010 11:01:30 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.4/8.14.4/Submit) id o5PI1Umj039243; Fri, 25 Jun 2010 11:01:30 -0700 (PDT) (envelope-from david) Date: Fri, 25 Jun 2010 11:01:30 -0700 From: David Wolfskill To: John Baldwin Message-ID: <20100625180130.GV90096@albert.catwhisker.org> References: <20100625114011.GO90096@albert.catwhisker.org> <201006250837.36220.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jr/gb2Ce1GM9KKZD" Content-Disposition: inline In-Reply-To: <201006250837.36220.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, brucec@freebsd.org Subject: Re: 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 18:01:31 -0000 --jr/gb2Ce1GM9KKZD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 25, 2010 at 08:37:36AM -0400, John Baldwin wrote: > On Friday 25 June 2010 7:40:11 am David Wolfskill wrote: > > 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. >=20 > 209469 perhaps? Apparently so. Here's what I did to test the above assertion: * Booted the build machine from slice 4 (usual "head" slice); cloned that slice to slice 1; booted from slice 1. * In a "head" src working directory, I issued svn diff -c209469 and saw that r209469 merely added 2 lines to usr.sbin/boot0cfg/boot0cfg.c. * On the build machine's src working directory, I edited usr.sbin/boot0cfg/boot0cfg.c to remove the lines in question. * Then (as root), I made /usr/src/usr.sbin/boot0cfg/ my current working directory and issued: make && make install * I then issued boot0cfg -s 4 aacd0 && shutdown -r now then watched the serial console. * I noticed that the default boot slice -- which had been 1 -- was now 4. * For grins, I then booted slice 4 (head) in single-user mode, mounted the file systems, then invoked the boot0cfg executable from slice 1 to switch the default to slice 2, then issued "halt -p". I waited a bit, then powered the machine back up (WoL can be handy!) noted it was booting from slice 2, brought it up in single-user mode, then issued "halt -p" to reduce its power consumption and heat & nouse generation. All that said, it looks as if r209469 merely noticed an existing error condition and tried to do something arguably sensible with it, rather than merely ignore it. So it would seem that there's a more fundamental issue at stake, here.... 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. --jr/gb2Ce1GM9KKZD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwk7vkACgkQmprOCmdXAD18OACcCvf7TfrtK9WtxGaNmvPuKuX8 PbIAn1NvfOGp+GfsnHIVYz3g9T8ekggO =pcn7 -----END PGP SIGNATURE----- --jr/gb2Ce1GM9KKZD--