From owner-freebsd-hackers  Wed Feb 26 11:58:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA29226
          for hackers-outgoing; Wed, 26 Feb 1997 11:58:05 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29221
          for <Hackers@freebsd.org>; Wed, 26 Feb 1997 11:58:02 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA00183; Wed, 26 Feb 1997 12:57:45 -0700 (MST)
Date: Wed, 26 Feb 1997 12:57:45 -0700 (MST)
Message-Id: <199702261957.MAA00183@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: <SimsS@IBM.Net>
Cc: "Nate Williams" <nate@mt.sri.com>, "Hackers" <Hackers@freebsd.org>
Subject: Re: Building PAO kernel on non-PAO system
In-Reply-To: <199702261953.TAA172572@out1.ibm.net>
References: <199702261953.TAA172572@out1.ibm.net>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> | > I've got an old laptop that I'd like to run Our Favorite OS(tm) on, but
> it
> | > **definitely** requires the PAO package to sort out some laptop-esque
> | > "features" that Compaq decided to implement.  I've got 2.1.6 loaded on
> the
> | > laptop right now (with PAO) and it works pretty well....  (Thanks,
> | > Hosokawa-san!)
> | 
> | You could install 2.2 on it and it would *probably* work.
> 
> Well, it didn't work the *last* time I tried.  (About 3 months ago; Same-old
> Same-old with the silly sio probes failing was the biggest headache.)

Hmm, the sio patches in PAO have changed a ton lately.  I don't think
the ones in PAO are *that* much different, although with PAO it adds the
ability to use the serial ports w/out knowing the specifics of the card
itself.  But, if you do *know* the specifics the 2.2 code should work.

> 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?



Nate