From owner-freebsd-standards@FreeBSD.ORG Sun Feb 26 18:40:24 2006 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 117A616A420 for ; Sun, 26 Feb 2006 18:40:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 595EE43D45 for ; Sun, 26 Feb 2006 18:40:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1QIeM0h088674 for ; Sun, 26 Feb 2006 18:40:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1QIeMOL088673; Sun, 26 Feb 2006 18:40:22 GMT (envelope-from gnats) Date: Sun, 26 Feb 2006 18:40:22 GMT Message-Id: <200602261840.k1QIeMOL088673@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Robert Millan Cc: Subject: Re: kern/93705: [patch] ENODATA and EGREGIOUS (for glibc compat) X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Millan List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 18:40:24 -0000 The following reply was made to PR kern/93705; it has been noted by GNATS. From: Robert Millan To: Gleb Smirnoff Cc: FreeBSD-gnats-submit@FreeBSD.org, Jordan Hubbard Subject: Re: kern/93705: [patch] ENODATA and EGREGIOUS (for glibc compat) Date: Sun, 26 Feb 2006 19:36:17 +0100 On Sun, Feb 26, 2006 at 02:35:48PM +0300, Gleb Smirnoff wrote: > On Wed, Feb 22, 2006 at 02:53:56PM +0100, Robert Millan wrote: > R> >Description: > R> Please could you add ENODATA and EGREGIOUS errno codes for compatibility with > R> Glibc systems? > R> > R> They have the same meaning as ENOATTR and EDOOFUS, respectively. > R> > R> As a side benefit, in the case of EDOOFUS this might be of interest to the Apple > R> developers who complained about this macro name (i.e. they could use EGREGIOUS in > R> Darwin exclussively if they want). > > The ENODATA error code is standardized as a part of XSI streams: > > http://www.opengroup.org/onlinepubs/000095399/basedefs/errno.h.html > > I don't think we should hardcode it equal to ENOATTR, which is a BSD specific > code, afaik. Linux uses ENODATA for no attribute errors, which afaik is the same as ENOATTR. However since the XSI definition is more generic as you point out, perhaps it'd be better to rename ENOATTR to ENODATA and make ENOATTR an alias for ENODATA instead? -- Robert Millan