From owner-freebsd-hackers  Fri Oct 31 19:57:34 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA27131
          for hackers-outgoing; Fri, 31 Oct 1997 19:57:34 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from word.smith.net.au (word.smith.net.au [202.0.75.3])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27105
          for <hackers@FreeBSD.ORG>; Fri, 31 Oct 1997 19:57:20 -0800 (PST)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA00788;
	Sat, 1 Nov 1997 14:23:46 +1030 (CST)
Message-Id: <199711010353.OAA00788@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: hackers@FreeBSD.ORG
cc: elh@svic.com
Subject: Re: 2.2.5 installation bug on 1gig machines 
In-reply-to: Your message of "Fri, 31 Oct 1997 16:40:21 -0800."
             <199711010040.QAA25276@implode.root.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 01 Nov 1997 14:23:44 +1030
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>    The problem with this is that the memory is already sized before
> 'userconfig' is called (it needs to be that way for various reasons). This
> basically means that we can't limit the memory during an install. You'll
> have to physically pull out some of the memory and/or replace it with
> lower density SIMMs until you've finished the installation and built a
> customized kernel.

It's often easier to pull the *disk* from the machine, and do the 
install and configuration alterations on another (smaller) system.

mike