From owner-freebsd-hackers@FreeBSD.ORG Sat May 28 18:07:11 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 1DBD7106564A for ; Sat, 28 May 2011 18:07:11 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id CB17E8FC0A for ; Sat, 28 May 2011 18:07:06 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4SI6vhb069219 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 28 May 2011 11:06:59 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DE139C9.2080808@freebsd.org> Date: Sat, 28 May 2011 11:07:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: rank1seeker@gmail.com 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> <20110528.130639.921.1@DEV> In-Reply-To: <20110528.130639.921.1@DEV> Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 8bit Cc: Doug Ambrisko , 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: Sat, 28 May 2011 18:07:11 -0000 On 5/28/11 6:06 AM, rank1seeker@gmail.com wrote: > And how about this: > > # boot0cfg -o noupdate -s 1 > Now when you choose to hit slice 2, it is only for a this one boot. > Next and each boot, defaults to slice 1 > > Problem is, that you must see, early bootstrap, to manually choose, so this won't work on a remote server. > This requires: > a) physicall access > or > b) ssh access to the remote box, which is conected via serial cable, to your server. > > Anyone has any idea, for a case of a remote server, which is accessible over ssh, only when it is "up"? pull the old bootblocks from about 2000 and use them. and nextboot as well they do exactly what you want. OR ask Doug Ambrisko (cc'd) for a copy of them that he still uses at work. He may have updates to make them work with modern systems that would save you time. the old nextboot(8) stored instructions as to what to do on block 1 of the drive (you can make it a small 1 block partition if you want). Actually it stored a series of them, NULL separated. On each boot the boot 0 bloter would read the first (after skipping any nulls) and then write Nulls over what it just read and write it back to block 1. so it would progress gradualy boot by boot over the sequence written by nextboot. it would pass on the stack, what it had read to boot1. the format was "hd(1,a)/boot/loader" (for example) personally I would like to hav ethis capabiltiy back because it's stupid rely on a possibly dead filesystem to get around booting from the possibly dead filesystem. by default we used to have a /etc/rc entry that would rewrite the 'current' setup several times on successful boot, followed by a couple of alternate boot targets. If boot failed a coupke of times it would automatically boot from the second drive or from another partition, .. > > Domagoj Smolčić > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >