From owner-freebsd-arch Thu Dec 23 5:53:43 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 7265614D4A for ; Thu, 23 Dec 1999 05:53:41 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id OAA23495 for ; Thu, 23 Dec 1999 14:53:40 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA38760 for freebsd-arch@freebsd.org; Thu, 23 Dec 1999 14:53:36 +0100 (MET) Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 615B614F59 for ; Thu, 23 Dec 1999 05:53:27 -0800 (PST) (envelope-from freebsd-arch@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA84548 for arch@FreeBSD.org; Thu, 23 Dec 1999 14:36:25 +0100 (CET) (envelope-from freebsd-arch@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for arch@FreeBSD.org (arch@FreeBSD.org) To: arch@freebsd.org Date: Thu, 23 Dec 1999 14:36:18 +0100 From: Marcel Moolenaar Message-ID: <38622552.8AB44C45@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <19991223132146.71BF11CCE@overcee.netplex.com.au> Subject: Re: [Fwd: Rq for approval: new command: genassym] Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > My concern is chicken/egg problems.. eg: how do you build a 4.0 kernel on a > 3.x system in order to complete the 'installworld' which requires a kernel > to be already built? It's no big deal but it's one more "special" thing. > config(8) and company are in the same boat, I'd rather we did less of this > than more. There's no chicken and egg problem. genassym builds independently of a kernel and is done so by the cross-tools target. Any kernel built as part of an upgrade process uses the freshly built genassym. The installworld problem is solved by not using any binaries that can be overwritten by the install process. I already have this locally. An installworld will not depend on a new kernel itself. An upgrade process can therefore build and install world *and* a kernel and only needs a working reboot to finish it off. Optionally it could install new bootblocks as well. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message