Date: Sun, 29 May 2011 17:28:08 +0200 From: rank1seeker@gmail.com To: hackers@freebsd.org Subject: Re: Active slice, only for a next boot Message-ID: <20110529.152808.781.1@DEV> In-Reply-To: <4DE139C9.2080808@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> <BANLkTinnZyGoi9RCZRX0JQNvBhHnQwEOSg@mail.gmail.com> <20110528.130639.921.1@DEV> <4DE139C9.2080808@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: Julian Elischer <julian@freebsd.org> To: rank1seeker@gmail.com Cc: hackers@freebsd.org, Doug Ambrisko <ambrisko@freebsd.org> Date: Sat, 28 May 2011 11:07:05 -0700 Subject: Re: Active slice, only for a next boot > 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, > .. > Well, if he has a working code and you have an idea, then it should be modernized and integarted into FreeBSD's src tree. So everyone could use it. > > > > > > 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" > > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110529.152808.781.1>