From owner-freebsd-hackers  Mon Oct 23 03:07:17 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA01349
          for hackers-outgoing; Mon, 23 Oct 1995 03:07:17 -0700
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA01340
          for <freebsd-hackers@freebsd.org>; Mon, 23 Oct 1995 03:07:12 -0700
Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <15335-0@bunyip.cc.uq.oz.au>; Mon, 23 Oct 1995 20:05:37 +1000
Received: from orion.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id TAA13996; Mon, 23 Oct 1995 19:57:08 +1000
Received: by orion.devetir.qld.gov.au (8.6.10/DEVETIR-0.3) id TAA22795;
          Mon, 23 Oct 1995 19:53:21 +1000
Date: Mon, 23 Oct 1995 19:53:21 +1000
From: Stephen McKay <syssgm@devetir.qld.gov.au>
Message-Id: <199510230953.TAA22795@orion.devetir.qld.gov.au>
To: Steven Wallace <swallace@ece.uci.edu>
cc: freebsd-hackers@freebsd.org, syssgm@devetir.qld.gov.au
Subject: Re: SYSCALL IDEAS [Was: cvs commit: src/sys/kern sysv_msg.c sysv_sem.c 
         sysv_shm.c]
Sender: owner-hackers@freebsd.org
Precedence: bulk

Steven Wallace <swallace@ece.uci.edu> wrote:

>>   semsys() and shmsys() syscall interfaces are BAD because they
>>   multiplex several syscalls that have different types of args.
>>   There was no reason to duplicate this sysv braindamage but now
>>   we're stuck with it.  NetBSD has reimplemented the syscalls properly
>>   as separate syscalls #220-231.
>>   
>I agree.  This is yucky!
>
>We need a better way to handle these syscall subcodes (as SYSV calls 'em).

Is it not true that this System V stuff can be written as library routines
that use BSD facilities such as mmap() and sockets?  I would be happy to see
the effort expended this way so that I can keep my kernel free of such cruft.

Stephen McKay.