From owner-freebsd-arch@FreeBSD.ORG Fri Jun 8 16:23:50 2007 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA4A916A4E2; Fri, 8 Jun 2007 16:23:50 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7A32A13C468; Fri, 8 Jun 2007 16:23:50 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l58GNnpQ029527; Fri, 8 Jun 2007 12:23:49 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Fri, 08 Jun 2007 12:23:49 -0400 (EDT) Date: Fri, 8 Jun 2007 12:23:49 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Roman Divacky In-Reply-To: <20070608161523.GB27624@freebsd.org> Message-ID: References: <20070604162430.GA76813@freebsd.org> <896DB1FBFFD5A145833D9DA08CA12A85051A7F@seaxch07.desktop.isilon.com> <20070606074429.GA42032@freebsd.org> <4666F0FB.8020101@FreeBSD.org> <20070607070455.GA71012@freebsd.org> <896DB1FBFFD5A145833D9DA08CA12A85051A84@seaxch07.desktop.isilon.com> <20070607210313.GA603@freebsd.org> <896DB1FBFFD5A145833D9DA08CA12A85051A87@seaxch07.desktop.isilon.com> <20070608161523.GB27624@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Eric Lemar , arch@freebsd.org Subject: Re: *at family of syscalls in FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 16:23:50 -0000 On Fri, 8 Jun 2007, Roman Divacky wrote: >> It looks like draft 3 will be released June 15, 2007 (in 10 days). > > is it ok to have this committed after June 15 (afaik the branching day)? maybe > without the native syscalls but with the kern_fooat() backend. (ie. *at syscalls > can be added for 7.1R with a few lines patch) I don't have any objection over adding linux compat functionality. I just don't want us to add native functions that don't conform to POSIX, mostly the API is what I am concerned about. We can change the behavior slightly to conform with whatever POSIX dictates, but we shouldn't knowingly introduce non-conforming APIs (because once 7.0 is released, we'll would always have to support both the non-conforming APIs as well as adding and supporting the conforming APIs). -- DE