From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 21:10:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AE7016A469; Mon, 21 Jan 2008 21:10:09 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 122B413C468; Mon, 21 Jan 2008 21:10:08 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.2/8.14.2/NETPLEX) with ESMTP id m0LLA2Mm022834; Mon, 21 Jan 2008 16:10:02 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 21 Jan 2008 16:10:02 -0500 (EST) Date: Mon, 21 Jan 2008 16:10:02 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Schultz In-Reply-To: <20080121210145.GA9107@VARK.MIT.EDU> Message-ID: References: <200801181217.52788.jkim@FreeBSD.org> <20080119121316.GA21917@VARK.MIT.EDU> <200801211152.07680.jkim@FreeBSD.org> <20080121210145.GA9107@VARK.MIT.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Jung-uk Kim , freebsd-arch@freebsd.org Subject: Re: [RFC] SysV SHM on 64-bit platforms X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 21:10:09 -0000 On Mon, 21 Jan 2008, David Schultz wrote: > On Mon, Jan 21, 2008, Jung-uk Kim wrote: >> On Saturday 19 January 2008 07:13 am, David Schultz wrote: >>> For 8-CURRENT, I'd say go ahead and fix it and add the syscall >>> compat goop. Then I guess backport it to 7-STABLE after a while if >>> nothing important breaks and nobody has any objections to that >>> plan. >> >> Well, since the policy is 'no seat belt for -CURRENT', I think that is >> aceptable, too. > > Right, but you need the compat shims to avoid breaking the ABI > when 8.0 is released anyway. The compat shims should be committed at the same time as the actual change so that applications built on [4-7].x will continue to work. -- DE