Date: Tue, 7 May 2002 13:53:35 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Eivind Eklund <eivind@FreeBSD.ORG> Cc: John Baldwin <jhb@FreeBSD.ORG>, Matthew Dillon <dillon@apollo.backplane.com>, arch@FreeBSD.ORG, Poul-Henning Kamp <phk@FreeBSD.ORG> Subject: Re: syscall changes to deal with 32->64 changes. Message-ID: <Pine.NEB.3.96L.1020507135200.83455A-100000@fledge.watson.org> In-Reply-To: <20020507185119.C11452@phoenix.dmnstech.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 May 2002, Eivind Eklund wrote: > Somewhere between 0 and 3.5 we should have an > > X) Write a list of proposed changes to the syscalls by just going > through the syscalls list and adding proposed changes, based on public > discussion. > > I think the right thing to do might be to just make a copy of > syscalls.master and let people commit suggested improvements, and then > post it to arch for discussion after a while (e.g, 3 weeks.) Probably close to the right strategy -- unfortunately most of the more interesting changes are in the supporting structs (struct stat, struct ipcperm, ...), which does complicate things. Also, many of the changes have to do with changing a type -- ino_t, or the like, rather than changing the arguments to the system call. This breaks the ABI, but maintains source-level compatibility as visible in syscalls.master :-). 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 freebsd-arch" 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.1020507135200.83455A-100000>