From owner-freebsd-hackers Mon Oct 2 09:21:18 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07379 for hackers-outgoing; Mon, 2 Oct 1995 09:21:18 -0700 Received: from victor.innovus.com (victor.innovus.com [192.75.186.54]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA07352 for ; Mon, 2 Oct 1995 09:21:12 -0700 Received: (from martin@localhost) by victor.innovus.com (8.6.11/8.6.9) id MAA18912; Mon, 2 Oct 1995 12:35:18 -0400 From: Martin Renters Message-Id: <199510021635.MAA18912@victor.innovus.com> Subject: Re: FreeBSD 2.1 will require a minimum of 8MB for installation. To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 2 Oct 1995 12:35:18 -0400 (EDT) Cc: davidg@Root.COM, bde@zeta.org.au, hackers@freefall.freebsd.org, jkh@time.cdrom.com, julian@ref.tfs.com In-Reply-To: <199510021502.AAA11626@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 3, 95 00:32:17 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 475 Sender: owner-hackers@FreeBSD.org Precedence: bulk > > >Surely there is more of a problem fitting everything at runtime than just > > >loading it? > > > > Nope, as far as I know the only problem is sufficient space to decompress > > the kernel binary and MFS filesystem. After this has occurred, there is > > "plenty" of room. How about uncompressing backwards and overwriting the compressed image during the uncompression? (ie: rather than starting at 1Mb and working up, start at 1M+kernel size and work down) Martin