From owner-freebsd-current Tue Mar 12 20:40:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 0963537B417 for ; Tue, 12 Mar 2002 20:40:03 -0800 (PST) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g2D4e0c26630 for ; Wed, 13 Mar 2002 13:40:00 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: References: <20020312191211.A78611@xor.obsecurity.org> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (bamboo) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 13 From: Makoto Matsushita To: current@FreeBSD.org Subject: Re: eaccess(2) breaks execution of 4.x binaries on 5.x Date: Wed, 13 Mar 2002 13:39:56 +0900 Message-Id: <20020313133956E.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG rwatson> Certainly we can MFC eaccess(), but that's not going to make rwatson> the problem go away. Fundamentally our model is backward rwatson> compatibility, not forward compatibility. We need to build rwatson> 5.0 packages on 5.0. That's why I build FreeBSD 5-current snapshots on a 5-current box. Note that we have already experienced such a situation before (at least in September 1999, sigset_t change). -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message