From owner-freebsd-emulation  Wed Sep 10 07:38:33 1997
Return-Path: <owner-freebsd-emulation>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA05218
          for emulation-outgoing; Wed, 10 Sep 1997 07:38:33 -0700 (PDT)
Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA05205
          for <emulation@freebsd.org>; Wed, 10 Sep 1997 07:38:19 -0700 (PDT)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00810;
	Thu, 11 Sep 1997 00:05:35 +1000 (EST)
Message-Id: <199709101405.AAA00810@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: emulation@freebsd.org
Subject: Re: Net posting: SCO gets Linux emulation 
In-reply-to: Your message of "Mon, 08 Sep 1997 18:11:26 MST."
             <16911.873767486@time.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 Sep 1997 00:05:30 +1000
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-emulation@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Could be interesting and/or instructional, yes?

Moderately.  It's somewhat barer-bones than our support so far.

They list 162 system calls in their dispatch list, and give 14 as 
"nosys".  Another 61 are implemented as returning ENOSYS, ie. they 
implement 87 system calls to some degree.
They list the following syscalls that we don't :
 getsid
 fdatasync		   (+)
 sysctl			(*)(+)
 mlock			(*)(+)
 munlock		(*)(+)
 mlockall		   (+)
 munlockall		   (+)
 sched_setparam		   (+)
 sched_getparam		   (+)
 sched_setscheduler	   (+)
 sched_getsheduler	   (+)
 sched_yield		   (+)
 sched_get_priority_max	   (+)
 sched_get_priority_min	   (+)
 sched_rr_get_interval	   (+)

(*) We could implement these, but don't. 
(+) They don't actually implement these, just list them.

We have 146 system calls listed, 4 marked unimplemented.  There are 41 
ENOSYS returns, ie. we implement 101 system calls.

There are a substantial number of ioctls for which they return ENOSYS, 
most of which we have already implemented.

This is all pretty unscientific; without sitting down and doing a 
one-to-one comparison it's a bit difficult to convey the relative 
"feel" of the two emulations.

mike