From owner-cvs-all Sun May 26 8:44:50 2002 Delivered-To: cvs-all@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9D08837B408; Sun, 26 May 2002 08:44:45 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 May 2002 16:44:44 +0100 (BST) To: obrien@FreeBSD.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/boot0cfg boot0cfg.8 In-Reply-To: Your message of "Sun, 26 May 2002 08:04:24 PDT." <20020526080424.C48489@dragon.nuxi.com> Date: Sun, 26 May 2002 16:44:44 +0100 From: Ian Dowse Message-ID: <200205261644.aa54710@salmon.maths.tcd.ie> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020526080424.C48489@dragon.nuxi.com>, David O'Brien writes: >I mind very much until you prove to me it is not needed. Below is what I >went thru to reboot a remote box from 5-CURRENT to 4.5. I can't explain or repeat that - the update flag is only supposed to affect whether making a boot selection from the boot0 boot manager (not boot0cfg) causes that selection to be made the default for the next boot. The "-s" flag should change the default slice regardless of the update/noupdate setting. The reason for saying that "-s" is useful with "-o noupdate" is because with the noupdate flag, "-s" is the _only_ way of changing the default slice, since booting from another slice does not change it. Could you investigate further what is happening here? If "-s" isn't always updating the MBR then there is a bug in boot0cfg, not in the documentation. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message