From owner-freebsd-current Wed Aug 5 20:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15939 for freebsd-current-outgoing; Wed, 5 Aug 1998 20:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15932 for ; Wed, 5 Aug 1998 20:27:00 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4GhH-0006Mc-00; Wed, 5 Aug 1998 20:26:35 -0700 Date: Wed, 5 Aug 1998 20:26:32 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Andrew Reilly cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <19980806112955.A4299@reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Andrew Reilly wrote: ... > Now if you were prepared to rely on hardware memory /protection/ > without using the hardware memory /mapping/, you could probably > do the same thing in C or C++ (or assembly language). I believe > that this has been tried in some of the Acorn ARM based OS's > (RiscOS and the Newton OS.) Most microkernel OSes are this way. QNX for x86 does something similar. The kernel is basically just a scheduler (a QNX kernel is less than 50K), and all other services that would normally be in the kernel are in their own address spaces, using strict IPC interfaces between modules. > -- > Andrew Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message