From owner-freebsd-hackers Tue Dec 10 13:38:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03207 for hackers-outgoing; Tue, 10 Dec 1996 13:38:22 -0800 (PST) Received: from eterna.com.au (mhri-10.mhri.edu.au [203.3.164.25]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA03192 for ; Tue, 10 Dec 1996 13:38:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by eterna.com.au (8.8.4/8.8.3) with SMTP id IAA23198; Wed, 11 Dec 1996 08:35:45 +1100 (EST) Message-Id: <199612102135.IAA23198@eterna.com.au> X-Authentication-Warning: splode.eterna.com.au: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: thorpej@nas.nasa.gov, jb@cimlogic.com.au, hackers@freebsd.org, tech-kern@netbsd.org, jonathan@dsg.stanford.edu (Jonathan Stone) From: matthew green Subject: Re: poll(2) In-reply-to: Your message of "Tue, 10 Dec 1996 11:20:55 PDT." <199612101820.LAA04523@phaeton.artisoft.com> Date: Wed, 11 Dec 1996 08:35:18 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If we did this _now_ we could, perhaps, reuse the existing syscall > number, since AFAIK poll(2) has never been in an official NetBSD release. Yes. The only conflict is call gate for ABI with some other OS that does poll with which you want binary compatability. Solaris might be one example. It really depends on whether execution classes imply system call interfaces, or not (they should, meaning no conflict). netbsd uses separate a system call table for each emulation (what you call an `execution class').