Date: Wed, 8 May 2002 17:49:48 +0200 From: Eivind Eklund <eivind@FreeBSD.ORG> To: Robert Watson <rwatson@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: <20020508174948.B28633@phoenix.dmnstech.net> In-Reply-To: <Pine.NEB.3.96L.1020507135200.83455A-100000@fledge.watson.org>; from rwatson@FreeBSD.ORG on Tue, May 07, 2002 at 01:53:35PM -0400 References: <20020507185119.C11452@phoenix.dmnstech.net> <Pine.NEB.3.96L.1020507135200.83455A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 07, 2002 at 01:53:35PM -0400, Robert Watson wrote: > > 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 :-). I was thinking of adding the suggested improvements as comments between the lines in the copy of syscalls.master, just using it as a red thread to make sure we examine a number of the relevant issues, and get a structured document out. And even the conversions you mention would end up being relevant there, as we would add comments on which syscalls would need a converting frontend to gain backwards compatibility. Eivind. 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?20020508174948.B28633>