Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: syscall(2) function
Keywords: syscall, not system calls
Message-ID: <9747@smoke.BRL.MIL>
Date: 28 Feb 89 04:48:24 GMT
References: <3740@ucdavis.ucdavis.edu> <9742@smoke.BRL.MIL> <2292@unmvax.unm.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <2292@unmvax.unm.edu> lee@doc.cs.unm.edu () writes:
-In article <9742@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
->In article <3740@ucdavis.ucdavis.edu> kerchen@iris.ucdavis.edu (Paul Kerchen) writes:
->>Is the system call "syscall()" necessary?
->I don't even think it's particularly useful these days; ...
-It still has uses...
-	exit (syscall(RESUBA, atoi(argv[1])));

Only because Berkeley neglected to provide a resuba() hook in
the C library!  Given direct hooks in the library for all system
calls, I know of no real requirement for the syscall() function.