From owner-freebsd-current Fri Nov 10 01:30:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA13543 for current-outgoing; Fri, 10 Nov 1995 01:30:21 -0800 Received: from lobster.dataplex.net ([199.183.109.243]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA13537 for ; Fri, 10 Nov 1995 01:30:17 -0800 Received: from [199.183.109.242] (COD.DATAPLEX.NET [199.183.109.242]) by lobster.dataplex.net (8.6.11/8.6.9) with SMTP id DAA06064; Fri, 10 Nov 1995 03:29:41 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 10 Nov 1995 03:29:45 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: config, other kernel build tools Cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Sender: owner-current@FreeBSD.org Precedence: bulk At 2:52 AM 11/10/95, J Wunsch wrote: >As Terry Lambert wrote: >> >> Because I don't want to install the new one to use the new one. > >Since my userland stuff is usually way behind -current, while i'm >keeping the kernel up to the latest bits more often, i cvs checkout >the modules config, include, lkm, and sys under a separate home >directory, and simply run config right from there. (Yes, all of them >belong to the kernel in some way, with include being the least >important one [mostly identical to the regular include].) > >Doesn't this also work for you? This is exactly the philosophy that needs to apply to the entire build process. Namely that you check out the (entire) tree in its own separate home and compile away using only things (including the include files) from within that home. ---- Richard Wackerbarth rkw@dataplex.net