From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264360AbTDKNlJ (for ); Fri, 11 Apr 2003 09:41:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264361AbTDKNlJ (for ); Fri, 11 Apr 2003 09:41:09 -0400 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:10625 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S264360AbTDKNlJ (for ); Fri, 11 Apr 2003 09:41:09 -0400 From: John Bradford Message-Id: <200304111340.h3BDet5i000926@81-2-122-30.bradfords.org.uk> Subject: Re: kernel support for non-English user messages To: 76306.1226@compuserve.com (Chuck Ebbert) Date: Fri, 11 Apr 2003 14:40:55 +0100 (BST) Cc: torvalds@transmeta.com (Linus Torvalds), linux-kernel@vger.kernel.org (linux-kernel) In-Reply-To: <200304110919_MC3-1-33FD-6E7@compuserve.com> from "Chuck Ebbert" at Apr 11, 2003 09:17:22 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > I've used VMS, and error code number encoding is a total heap of crap. > > Maybe for developers, but users like it. I can still remember back in > the Old Days, taking those error codes and looking them up in something > called a "manual" where there was a coherent explanation of > what had gone wrong and even suggestions on what to do about it. Well, you don't need error codes to make a comprehensive manual, you can just look up the English error message, and get a detailed explaination of it, in any language. John.