From owner-freebsd-arch Tue May 7 10:54: 2 2002 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 24A0D37B408; Tue, 7 May 2002 10:53:56 -0700 (PDT) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.3/8.12.3) with SMTP id g47HrZb5083637; Tue, 7 May 2002 13:53:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 7 May 2002 13:53:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Eivind Eklund Cc: John Baldwin , Matthew Dillon , arch@FreeBSD.ORG, Poul-Henning Kamp Subject: Re: syscall changes to deal with 32->64 changes. In-Reply-To: <20020507185119.C11452@phoenix.dmnstech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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