From owner-freebsd-hackers  Wed Feb 26 12:33:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA01314
          for hackers-outgoing; Wed, 26 Feb 1997 12:33:03 -0800 (PST)
Received: from out1.ibm.net (out1.ibm.net [165.87.194.252])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA01281
          for <Hackers@freebsd.org>; Wed, 26 Feb 1997 12:32:37 -0800 (PST)
Received: (from uucp@localhost) by out1.ibm.net (8.6.9/8.6.9) id UAA71641; Wed, 26 Feb 1997 20:32:28 GMT
Message-Id: <199702262032.UAA71641@out1.ibm.net>
Received: from slip166-72-229-228.va.us.ibm.net(166.72.229.228) by out1.ibm.net via smap (V1.3mjr)
	id smaprACrx; Wed Feb 26 20:32:11 1997
Reply-To: <SimsS@IBM.Net>
From: "Steve Sims" <SimsS@IBM.Net>
To: "Nate Williams" <nate@mt.sri.com>
Cc: "Hackers" <Hackers@freebsd.org>
Subject: Re: Building PAO kernel on non-PAO system
Date: Wed, 26 Feb 1997 15:32:03 -0500
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Nate Williams <nate@mt.sri.com> says:
| > What does surprise me is that there isn't a *obvious* way to build
kernels
| > or, for that matter, hardware- and kernel-structure-specific apps for
various
| > architectures, versions and configurations on a single machine and
distribute
| > them to one or more "client" machines.  I've run shops where this would
have
| > been a REQUIREMENT (e.g.: a farm of diskless workstations in a variety of
| > interfaces, processors, etc...)
| 
| What do you mean?  Copy the config to a new name, edit it, build the
| kernel and you're donne.  What more do you want?

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.

This is the point I'm trying to make in my own inept fashion - I can't build
a PAO-enabled kernel to distribute to another machine on a (non-PAO
configured) desktop that's running a different rev of FreeBSD source.  Or can
I? 

...sjs...