From owner-freebsd-arch@FreeBSD.ORG Mon Mar 30 18:33:23 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 1F47F10656CC for ; Mon, 30 Mar 2009 18:33:23 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout021.mac.com (asmtpout021.mac.com [17.148.16.96]) by mx1.freebsd.org (Postfix) with ESMTP id 1053F8FC1C for ; Mon, 30 Mar 2009 18:33:22 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from iphone-5.jnpr.net ([66.129.224.36]) by asmtp021.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KHB006RLY3H1N70@asmtp021.mac.com> for arch@freebsd.org; Mon, 30 Mar 2009 10:33:18 -0700 (PDT) Message-id: <8321954E-5CFF-45F9-9F87-BE83659E4C8D@mac.com> From: Marcel Moolenaar To: FreeBSD Arch Date: Mon, 30 Mar 2009 10:31:56 -0700 X-Mailer: Apple Mail (2.930.3) Cc: Subject: 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: Mon, 30 Mar 2009 18:33:23 -0000 All, I've often found myself going over the existing error codes in search for one that seems to match best or is the least unsuitable. This begs the question: what is stopping us from adding new error codes? With so many drivers returning ENXIO whenever something (i.e anything) is wrong, how meaningful is ENXIO in diagnosing problems? What do the various standards dictate or allow us to do? -- Marcel Moolenaar xcllnt@mac.com