From owner-freebsd-hackers@FreeBSD.ORG Sat May 28 11:06:48 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 461C6106566B for ; Sat, 28 May 2011 11:06:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id BBD658FC13 for ; Sat, 28 May 2011 11:06:47 +0000 (UTC) Received: by bwz12 with SMTP id 12so2727719bwz.13 for ; Sat, 28 May 2011 04:06:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=xImvqhDbjU9ng867tQJyiCJQgO8VhGCnP1R4AO3wHrY=; b=j3ZSFDv9QRD5SWMDEDGlTs6EANgVpfnvHJYBC7Dc55MIds2EUN0M0hPYunRpYK7iNP ZHg+WQw+aLk/12Izlgdeb8OYPN+OiEZ7R28IzPa5wowlU1Iy9i/CLAHiLWuaW+j4EKc0 BFYjeA8Q64slN6Zwi1QnHB5oJAi/KSqZYQkLg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=vqw7WuNaPISn8GWHYGwy49d2xzhZ0DkdmSibj+asd5xWtNq/okSuBWyqQSIVKp/C4Z HIh2IjEcNCrxiwiFOUyrnHNVbtai67BYSUjiczOU1QtcUqQhtmr9S6v66pvyDgKSv/Nu BJgbAkihxC6ohmnlwiB19qOp4A5mINICc4BkA= MIME-Version: 1.0 Received: by 10.204.82.149 with SMTP id b21mr2525360bkl.196.1306580806363; Sat, 28 May 2011 04:06:46 -0700 (PDT) Received: by 10.204.66.81 with HTTP; Sat, 28 May 2011 04:06:46 -0700 (PDT) Received: by 10.204.66.81 with HTTP; Sat, 28 May 2011 04:06:46 -0700 (PDT) In-Reply-To: <4DE0BA7C.8080707@freebsd.org> References: <20110527.124553.718.1@DEV> <20110527134754.GA94769@freebsd.org> <20110527.164723.750.2@DEV> <496B0C04-7777-458D-A116-27944A4006BB@bsdimp.com> <4DE0BA7C.8080707@freebsd.org> Date: Sat, 28 May 2011 12:06:46 +0100 Message-ID: From: Chris Rees To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: rank1seeker@gmail.com, 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 Reply-To: utisoft@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2011 11:06:48 -0000 On 28 May 2011 10:04, "Julian Elischer" wrote: > > On 5/27/11 11:34 AM, Warner Losh wrote: >> >> On May 27, 2011, at 10:47 AM, rank1seeker@gmail.com wrote: >> >>> ----- Original Message ----- >>> From: Alexander Best >>> To: rank1seeker@gmail.com >>> Cc: hackers@freebsd.org >>> Date: Fri, 27 May 2011 13:47:54 +0000 >>> Subject: Re: Active slice, only for a next boot >>> >>>> On Fri May 27 11, rank1seeker@gmail.com wrote: >>>>> >>>>> Idea is ... >>>>> I have i.e; 3 slices, of which first is active. >>>>> Now I wana set slice 2 active, but only for a one/next boot. >>>>> Once slice 2 is booted and system is shutdown or rebooted, once again, >>> >>> first slice is active and booted, without user's intervention. >>>>> >>>>> Is this possible or should be implemented? > > > nextboot(8) USED to do this before it was broken by someone to "look into the filesystem" > for it's next boot hint which is obviously broken if you are trying to get to another filesystem > because the main one is broken. > Doesn't sound that useful to me- I think of the main use for nextboot being to try new kernels on a one-time basis. If you're rescuing a broken filesystem surely it's better to just set another slice active? Chris