Received: (from major@localhost)
	by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id MAA15404
	for pups-liszt; Thu, 18 Feb 1999 12:32:52 +1100 (EST)
Received: from moe.2bsd.com (0@MOE.2BSD.COM [206.139.202.200])
	by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id MAA15399
	for <pups@minnie.cs.adfa.oz.au>; Thu, 18 Feb 1999 12:32:38 +1100 (EST)
Received: (from sms@localhost)
	by moe.2bsd.com (8.9.0/8.9.0) id RAA05895
	for pups@minnie.cs.adfa.oz.au; Wed, 17 Feb 1999 17:25:53 -0800 (PST)
Date: Wed, 17 Feb 1999 17:25:53 -0800 (PST)
From: "Steven M. Schultz" <sms@moe.2bsd.com>
Message-Id: <199902180125.RAA05895@moe.2bsd.com>
To: pups@minnie.cs.adfa.oz.au
Subject: Re: 2.11BSD, non-split i/d issues
Sender: owner-pups@minnie.cs.adfa.edu.au
Precedence: bulk

Hi -

> From: allisonp@world.std.com (Allison J Parent)
> The F11 does not do I&D split but does have user/system.  

	Correct.  Some systems also have an 18bit only MMU which restricts
	memory to 248kb max (others have a 22bit MMU and can physically
	have more memory).

> It's my understanding that 2.11 will run on F11 systems (pro350 and 11/23)
> if properly configured but the only binaries loose are for split I&D.

	Not likely.  The kernel won't fit in 48kb that I know of.  And there
	will be no networking support since that requires supervisor mode
	which non-split I/D systems don't have.

> So if properly configured you can get 2.11 to utilize the user/system spaces.

	The skeleton of a Makefile for non-split a kernel exists but it 
	will take much work (it is essentially just a list of file that may
	or may not be 100% current) to kick into shape.  Also, remember that
	programs like 'csh', 'vi' and so on are not only split I/D but 
	overlaid - they will not run on a non-split machine. 

	Steven Schultz

