From owner-freebsd-arch Wed Aug 21 12:38:55 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C89E437B400; Wed, 21 Aug 2002 12:38:51 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E3543E81; Wed, 21 Aug 2002 12:38:51 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g7LJZQRo059065; Wed, 21 Aug 2002 21:35:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jon Mini Cc: Alexander Leidinger , arch@freebsd.org Subject: Re: timestamping kernel messages In-Reply-To: Your message of "Tue, 20 Aug 2002 17:54:14 PDT." <20020821005414.GJ3751@elvis.mu.org> Date: Wed, 21 Aug 2002 21:35:26 +0200 Message-ID: <59064.1029958526@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020821005414.GJ3751@elvis.mu.org>, Jon Mini writes: >Poul-Henning Kamp [phk@critter.freebsd.dk] wrote : > >> I think we need to revamp the console/logging system in toto. >It has several problems that really irritate me, such as the fact >that messages are sent to the console one character at a time, >resulting in jumbled messages like: > > | MSoMuPn:t iAnPg CrPoUo t# 1f rLoamu nucfhse:d/!d > | ev/ad0a I think we need to recognize that "_the_ console" is not an appropriate metaphor anymore. We have, at least the following roles: The place we print the kernels bootstrap information. The place the kernel can ask questions during bootstrap. The place we print panics The place we print kernel debugging information. The place we interract with gdb The place we print the single-user to multi-user information The place we print certain run-time error/log messages In addition to this we have at least: The channel for sending kernel log events to syslogd I have no idea what the right solution looks like, but the current code isn't it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message