From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 26 21:28:39 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25DA4106564A; Mon, 26 Mar 2012 21:28:39 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7AD7A8FC20; Mon, 26 Mar 2012 21:28:38 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so5998508bkc.13 for ; Mon, 26 Mar 2012 14:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Aq01YYiFPnDUkopjuHmg/NKkIeUlqmYWrd9HkGOxCGw=; b=ADvmEE1VtFc9hqYn0G+CFbmtMU+Jmte/PPgRS3HyR4IQudNT/BsVpLqOXXdfQl9xPU DmCYjUrRt6cjZ1j+kB5YmycRvNVhHjcXCSQx5LMHqAttOeO5Dg8RV23OP5KqBzYuUr6c UtQM+AZPc9EdVEoXDGGWfKDZ9cESzkpPVzxP4tuL9QnfDISA4NhjpShA5jjj3cS6xh/X h2eT9p6p7JIqn6XvXoHp67YMIbBHm53qWRWiEJReKEENX6sWrE4osVsCHpCeXXLnyTln DQfrZMh8Zpu7a/VqetWmovv6l20ete+jXZM3MejlQVPr6bF3T+5SLXQKZ5DtThGs0+oq 73bg== Received: by 10.205.137.15 with SMTP id im15mr9116454bkc.54.1332797317363; Mon, 26 Mar 2012 14:28:37 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.202.142 with HTTP; Mon, 26 Mar 2012 14:28:07 -0700 (PDT) In-Reply-To: <20120326.181050.391.3@DOMY-PC> References: <20120325.184917.751.1@DOMY-PC> <201203261018.53717.jhb@freebsd.org> <20120326.181050.391.3@DOMY-PC> From: Chris Rees Date: Mon, 26 Mar 2012 21:28:07 +0000 X-Google-Sender-Auth: sP5uODGMdMIP4Edz6csF2G42VA4 Message-ID: To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: Active slice, only for a next boot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 21:28:39 -0000 On 26 March 2012 18:10, wrote: > ----- Original Message ----- > From: John Baldwin > To: freebsd-hackers@freebsd.org > Cc: rank1seeker@gmail.com, hackers@freebsd.org > Date: Mon, 26 Mar 2012 10:18:53 -0400 > Subject: Re: Active slice, only for a next boot > >> On Sunday, March 25, 2012 2:49:17 pm rank1seeker@gmail.com wrote: >> > After having a thought about this issue and also currently looking at = a >> BootEasy boot manager ... >> > 'boot0cfg' is almost perfect for this task and should/could be "exploi= ted". >> > >> > It's '-o noupdate' already does a major task, of keeping main slice ac= tive. >> > Now all we need is a flag, through which we specify slice to boot (rep= lacing >> human presing button). >> > From that point on, existing code simply proceeds with received value. >> > >> > '-o noupdate' ensures next boot will bring up main/active slice. >> >> You mean like 'boot0cfg -s 4'? >> >> -- >> John Baldwin >> > > > Yes, but new flag for that purpose ('-n' for example =3D> nextboot). > > I.e; > =A0 =A0# 'boot0cfg -s 4 -o noupdate -n 3' > > Would, set the default/main boot selection to slice 4 and =A0'-o noupdate= ' =A0ensures it remains that way, while '-n 3' would auto press/choose slic= e 3 in selection menu, as human would. > Well in that case, better to not show menu at all, thus only "blic" into = slice 3. > At next boot it is at slice 4 again. I'm afraid this sounds like a great way to make a very confusing scenario, where you have to reboot twice to be sure of a consistent boot sector, unless I've misunderstood you. Chris