Date: Fri, 1 Feb 2002 13:14:08 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Alfred Perlstein <bright@mu.org> Cc: Bruce Evans <bde@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern init_sysent.c syscalls.c src/sys/sys syscall.h syscall.mk sysproto.h Message-ID: <Pine.NEB.3.96L.1020201131150.99143B-100000@fledge.watson.org> In-Reply-To: <20020201100622.L18604@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Feb 2002, Alfred Perlstein wrote: > Do you have any input as to whether per-arch syscall.master is a good > idea? Or perhaps syscall.std, or something that specifies which arches > have which syscalls? Specifically so that we could make osigreturn an > i386 only syscall? Personally, I'd much prefer to see one syscalls.master. I've seen the confusion resulting from different system call numbering schemes across architectures on Linux, and it worries me :-). For one thing, it would be nice when handing out a system call number to be able to say "We've allocated 642 for this system call" rather than "We've allocated you 642 on i386, 457 on axp, 493 on ia64, ...". My preference would very much be for keeping one syscalls.master, and just #ifndef ARCHITECTURE_OF_MY_CHOICE return(ENOSYS) #endif. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020201131150.99143B-100000>