From owner-freebsd-current Wed Oct 27 16:11:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id F202214E08 for ; Wed, 27 Oct 1999 16:11:34 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40344>; Thu, 28 Oct 1999 09:06:31 +1000 Content-return: prohibited Date: Thu, 28 Oct 1999 09:11:23 +1000 From: Peter Jeremy Subject: Re: make buildworld problem... In-reply-to: <19991027143653.B21727@dragon.nuxi.com> To: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct28.090631est.40344@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991027143653.B21727@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: >IF you are going to run -CURRENT, you need to read this list. And read /usr/src/UPDATING which also warns about this >(/me wonders how many MORE times we are going to have to say this because >of the signal changes...) A very large number I suspect. IMHO, the correct solution is to for the entire make world process to be re-worked. I believe the process should always be to boot a new kernel first (as bde(?) commented - it's much easier to recover from a broken kernel than a broken world), and then install a new world. Getting there from here is non-trivial - the major problem being that our build process does not adequately differentiate between compiling code that must run now and code that must run with the new kernel. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message