Date: 08 Jan 1999 02:06:47 +0100 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Julian Elischer <julian@whistle.com> Cc: Nate Williams <nate@mt.sri.com>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Message-ID: <xzpg19m8teg.fsf@flood.ping.uio.no> In-Reply-To: Julian Elischer's message of "Thu, 07 Jan 1999 14:42:42 -0800" References: <199901072037.NAA22536@mt.sri.com> <Pine.BSF.3.95.990107124507.3875I-100000@current1.whistle.com> <199901072101.OAA22809@mt.sri.com> <36952F5F.2781E494@whistle.com> <199901072214.PAA24446@mt.sri.com> <36953862.59E2B600@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer <julian@whistle.com> writes: > no the upgrade code didn't have the ability to run arbitrary code > BEFORE booting into the new system. It has the ability to schedule > arbitrary code to be run AFTER teh new kernel has booted (so that > the arbitrary code is running on the same systemit was compiled on) > but before the actual application starts, but that's too late for > changing the bootblocks. Is that so? Install the new kernel and bootblocks in a temporary space, and throw in a script that installs the bootblocks, then the new kernel, and reboots. Customer upgrades, boots the Interjet with the old bootblocks and kernel, script does its job, Interjet reboots with new bootblocks and kernel. Only hitch is 30-60 seconds more downtime required for the upgrade. And you call yourself a programmer? Furrfu. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpg19m8teg.fsf>