Date: Fri, 28 Feb 2003 08:10:57 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: John Baldwin <jhb@FreeBSD.org> Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, Geoffrey <geoffrey@reptiles.org>, current@FreeBSD.ORG, Garance A Drosihn <drosih@rpi.edu>, David Schultz <das@FreeBSD.ORG> Subject: Re: Any ideas why we can't even boot a i386 ? Message-ID: <3E5F8A11.81E4726B@mindspring.com> References: <XFMail.20030228103456.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > Or you can use PXE at your provisioning center and have the > BIOS setup to boot from the hard disk first, which will fail > for the initial boot and fall back to PXE. Then once the box > is installed you ship it to its destination. This is a possibility; however, there are a number of system failure scenarios that make this undesirable. Specifically, it's desirable to support the idea of a fallback boot (e.g. "nextboot") for a partially functional system, to downgrade it automatically, and make it at least something other than a doorstop on which one has to pay international shipping. In your scenario, there's no possible reupgrade method. I understand that FreeBSD doesn't have a built-in graceful fallback mechanism, and that appliance vendors have had to, traditionally, "roll their own", but, for example, the Whistle InterJet had a fairly marvelous fallback mechanism, which did work really well, as long as you didn't try to do version insertion (that's a middle management problem, not a technical one). > We just launched a closed-box appliance yesterday. Actually, > it's going live to actual customers in about an hour and a > half, but I digress. :) You should shout it to the world... at least post a press release to -advocacy! -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E5F8A11.81E4726B>