From owner-freebsd-arch@FreeBSD.ORG Fri Apr 3 18:02:05 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 686E41065690 for ; Fri, 3 Apr 2009 18:02:05 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id 152768FC23 for ; Fri, 3 Apr 2009 18:02:04 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n33GxtN3021552; Fri, 3 Apr 2009 12:59:57 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <8321954E-5CFF-45F9-9F87-BE83659E4C8D@mac.com> Date: Fri, 3 Apr 2009 12:59:54 -0400 To: Marcel Moolenaar , FreeBSD Arch From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.00 () [Hold at 20.00] 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Cc: Subject: Re: On errno X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2009 18:02:06 -0000 At 9:13 AM -0700 4/1/09, Marcel Moolenaar wrote: >On Mar 30, 2009, at 10:31 AM, Marcel Moolenaar wrote: > >>This begs the question: what is stopping us from adding new >>error codes? > >>>kientzle@ wrote: >>>POSIX does specify the range of allowable error codes >>>for a lot of system calls, but not all. In my experience, >>>straying outside of that causes more problems than it's >>>worth. > >I agree that well-known system calls should not be changed >willy-nilly. But what about error codes returned from GEOM >or other FreeBSD-specific subsystems? I'll make the observation that I've seen a lot of code which calls some system routine, checks the result, and if there was an error it just returns to the caller. Thus, a new errno from GEOM may show up as coming from routines which are not FreeBSD-specific. Now, that might be a fine thing to do. I'm just saying that we can not be sure that any new errno's will *only* show up as coming from routines that are unique to FreeBSD. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu