From owner-freebsd-hackers  Wed Feb 26 14:43:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA08069
          for hackers-outgoing; Wed, 26 Feb 1997 14:43:38 -0800 (PST)
Received: from monorail.net-tel.co.uk (monorail.net-tel.co.uk [193.122.171.247])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08056
          for <Hackers@freebsd.org>; Wed, 26 Feb 1997 14:43:27 -0800 (PST)
From: Andrew.Gordon@net-tel.co.uk
Received: (from root@localhost)
          by monorail.net-tel.co.uk (8.8.4/8.8.4)
	  id WAA19697; Wed, 26 Feb 1997 22:42:39 GMT
Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk
        (Route400-RFCGate); Wed, 26 Feb 97 22:38:52 +0000
X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/";
         Relayed; Wed, 26 Feb 97 22:38:52 +0000
X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; 
        Wed, 26 Feb 97 22:38:52 +0000
X400-MTS-Identifier: 
        ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:7086-970226223852-7E55]
X400-Content-Type: P2-1984 (2)
X400-Originator: Andrew.Gordon@net-tel.co.uk
Original-Encoded-Information-Types: IA5-Text
X400-Recipients: non-disclosure:;
Date: Wed, 26 Feb 97 22:38:52 +0000
X400-Content-Identifier: Re(2): Building 
Message-Id: <"2818-970226224035-BC18*/G=Andrew/S=Gordon/O=NET-TEL Computer
 Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>
To: SimsS <SimsS@IBM.Net>
Cc: Hackers <Hackers@freebsd.org>
In-Reply-To: <199702262032.UAA71641@out1.ibm.net>
Subject: Re(2): Building PAO kernel on non-PAO system
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I think you missed my point - It's not possible (or I'm not smart enough to
> know how) to build, say, 2.1.7, 2.2 *AND* -current kernels on a single
> "super
> server" and then blow them out amongst the unsuspecting users depending on
> their needs (and possibly their threshold for pain).  Can such a thing be
> done?  Obviously, I can build different *configurations* of a single
> release
> version, but I can't (easily) have different versions of the OS all build
> from the same source tree.

I have had success in the past with working in a chroot environment.
My reason for wanting to do this was that I had a fast-ish machine
used for real work and hence running -stable, plus an old 386sx
available for hacking on, clearly quite unsuitable for doing 'make world'!

Since I was adding an extra drive to hold the -current sources,
I took the easy option for getting it initialised: I just used sysinstall
to do a basic install, such that the new drive contained a bootable
system.  I then did as follows:

mount the new drive as /current
install -current source on /current/usr/src
chroot /current
cd /usr/src
make world
build kernel

On the 386:
NFS mount big_machine:/current/usr/src on /usr/src
cd /usr/src
make install

The only minor snag I ran into was that 'make install' left
/usr/include/* as symlinks into the /usr/src, which needed to be
undone if I didn't want to leave the NFS mounts in place permanently.

Maybe there are other snags, but it was remarkably painless for me.