Skip site navigation (1)Skip section navigation (2)
Date:      13 May 2000 23:13:17 +0200
From:      Assar Westerlund <assar@sics.se>
To:        Robert Watson <rwatson@FreeBSD.ORG>
Cc:        freebsd-arch@FreeBSD.ORG
Subject:   Re: Procedure for introducing new errno values?
Message-ID:  <5l8zxenogi.fsf@assaris.sics.se>
In-Reply-To: Robert Watson's message of "Tue, 2 May 2000 21:19:38 -0400 (EDT)"
References:  <Pine.NEB.3.96L.1000502211509.19996O-100000@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson <rwatson@FreeBSD.ORG> writes:
> What is the correct procedure for adding new errno values?  Presumably
> errno.8, src/sys/errno.h, as well as presumably some other files (perhaps
> in libc) for defining the string version, et al?

I think src/sys/errno.h, src/lib/libc/gen/errlst.c, and
src/lib/libc/sys/intro.2 should be it.

> I've also noticed that there is an errno.h in both /usr/include and
> /usr/include/sys.

Isn't the one in /usr/include a symlink to sys/errno.h?

> I am proposing EEXTATTR ("Extended attribute not defined"), which would be
> returned when a consumer of the VOP_GETEXTATTR() call attempted to
> retrieve an undefined attribute name.

Sounds fine to me.  Or perhaps ENOEXTATTR?

/assar


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5l8zxenogi.fsf>