From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0610171724u1ca1d1d2u6ecaf2d5d7a31f6a@mail.gmail.com>
Date: Tue, 17 Oct 2006 20:24:39 -0400
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 9pm/Plan 9 kernel in user space
In-Reply-To: <20061017233134.GA19696@debian31m>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20061017233134.GA19696@debian31m>
Topicbox-Message-UUID: cb897628-ead1-11e9-9d60-3106f5b1d025

You could get that version compiling with some
work, but I don't think it's a very good idea.
You'll still need to write a lot of code to deal
with things like process management, which a
user level kernel can't actually help with.
Having device files for the disks only gets you so far.

You'd be better off just porting fossil (venti is ported)
to the current Plan 9 from User Space, which does
not depend on a central user-space kernel.
http://swtch.com/plan9port/

If you still want a user-space kernel, the drawterm code
is essentially that, though it doesn't contain any
provisions for running "system calls" on behalf of
other processes.
http://swtch.com/drawterm/

Russ