Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 30 Dec 2001 16:00:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 30 Dec 2001 15:59:54 -0500 Received: from dial-up-2.energonet.ru ([195.16.109.101]:6784 "EHLO dial-up-2.energonet.ru") by vger.kernel.org with ESMTP id ; Sun, 30 Dec 2001 15:59:45 -0500 Date: Mon, 31 Dec 2001 00:01:09 +0000 (GMT) From: ertzog To: Lennert Buytenhek cc: linux-kernel@vger.kernel.org, jdike@karaya.com Subject: Re: [PATCH][RFC] global errno considered harmful In-Reply-To: <20011230110623.A17083@gnu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org And can anybody explain, why is it so ? (I mean checking for -1, and the switch(errno){}.) AFAIK, syscall returns us a number (on i386 it is in eax) and we can use it. Is errno a kernel thing, or GLIBC ? Haven't we a return code in eax, after int 0x80 ? (sorry, but I never worked on Linux on other architectures) Best regards. On Sun, 30 Dec 2001, Lennert Buytenhek wrote: > Is there any particular reason we need a global errno in the kernel > at all? (which, by the way, doesn't seem to be subject to any kind of - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/