From owner-freebsd-current@FreeBSD.ORG Mon Jun 28 08:59:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4BC516A4CE; Mon, 28 Jun 2004 08:59:36 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ECD543D2D; Mon, 28 Jun 2004 08:59:36 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (localhost [127.0.0.1]) by fw.farid-hajji.net (Postfix) with ESMTP id 23FBF4AC31; Mon, 28 Jun 2004 11:00:10 +0200 (CEST) From: Cordula's Web To: dillon@apollo.backplane.com In-reply-to: <200406280653.i5S6rufW076565@apollo.backplane.com> (message from Matthew Dillon on Sun, 27 Jun 2004 23:53:56 -0700 (PDT)) X-Mailer: Emacs-21.3.1/FreeBSD-5.2.1-RELEASE References: <200406280653.i5S6rufW076565@apollo.backplane.com> Message-Id: <20040628090010.23FBF4AC31@fw.farid-hajji.net> Date: Mon, 28 Jun 2004 11:00:10 +0200 (CEST) cc: freebsd-current@freebsd.org cc: rwatson@freebsd.org cc: alex@hightemplar.com Subject: Re: HEADSUP: ibcs2 and svr4 compat headed for history X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cpghost@cordula.ws List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2004 08:59:36 -0000 Matthew Dillon wrote: > The actual kernel work required to implement such a layer is not all > that complex -- really all the kernel has to do is take an INT 0xN > and throw it back in userland's face (or even just make the INT 0xN vector > an LDT vector that runs in userland's protection ring and never even > enters the kernel). That's the old trampoline approach used in Lites/Mach. It's OT here, but if you plan to microkernelize dFly, do you know L4? L4Ka::Pistachio (http://l4ka.org/) is released under the BSD license ;) > So, as you can see, there is great potential flexibility in such a > design. So much so, in fact, that the ability to move things like > SysV and IBCS2 out of the kernel become mere side effects of a larger > purpose. It would be a huge advance over the crufty syscall methodology > that all UNIXes today employ. Absolutely. > -Matt -cpghost. -- Cordula's Web. http://www.cordula.ws/