Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!doc.cs.unm.edu!lee
From: lee@doc.cs.unm.edu (Lee Ward)
Newsgroups: comp.unix.wizards
Subject: Re: syscall(2) function
Keywords: syscall, not system calls
Message-ID: <2292@unmvax.unm.edu>
Date: 27 Feb 89 23:52:20 GMT
References: <3740@ucdavis.ucdavis.edu> <9742@smoke.BRL.MIL>
Sender: news@unmvax.unm.edu
Reply-To: lee@doc.cs.unm.edu ()
Organization: University of New Mexico at Albuquerque
Lines: 31

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?
>
>It's not a system call, just a library function.
>Of course it is not necessary in any logical sense.
>I don't even think it's particularly useful these days;
>the last time I saw it used was on a Sixth Edition UNIX system.


It still has uses...

#include <stdio.h>

/* 4.{2,3} reset UBA - BSD VAX */

#define	RESUBA		119

main(argc, argv)
	int	argc;
	char	*argv[];
{

	if (argc != 2) {
		fprintf(stderr, "Usage: %s UBA#\n", argv[0]);
		exit(1);
	}

	exit (syscall(RESUBA, atoi(argv[1])));
}
			--Lee (Ward)