Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755511AbXJHDZT (ORCPT ); Sun, 7 Oct 2007 23:25:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752542AbXJHDZH (ORCPT ); Sun, 7 Oct 2007 23:25:07 -0400 Received: from 1wt.eu ([62.212.114.60]:2824 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753018AbXJHDZG (ORCPT ); Sun, 7 Oct 2007 23:25:06 -0400 Date: Mon, 8 Oct 2007 05:23:05 +0200 From: Willy Tarreau To: Oleg Verych Cc: Rene Herman , Ingo Molnar , Jan Engelhardt , Linux Kernel Mailing List , Dave Jones , Krzysztof Halasa , Medve Emilian-EMMEDVE1 , Helge Deller Subject: Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Message-ID: <20071008032305.GA28755@1wt.eu> References: <20071006195105.GE22435@flower.upol.cz> <20071006194820.GA30579@elte.hu> <20071006210349.GG22435@flower.upol.cz> <20071007060706.GA18768@elte.hu> <20071007111035.GO22435@flower.upol.cz> <20071007161255.GA22102@elte.hu> <470929D8.80003@keyaccess.nl> <20071007191309.GS10199@1wt.eu> <20071007194725.GS22435@flower.upol.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071007194725.GS22435@flower.upol.cz> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2343 Lines: 51 On Sun, Oct 07, 2007 at 09:47:25PM +0200, Oleg Verych wrote: > On Sun, Oct 07, 2007 at 09:13:09PM +0200, Willy Tarreau wrote: > > On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote: > > > On 10/07/2007 06:12 PM, Ingo Molnar wrote: > > > > > > >* Oleg Verych wrote: > > > > > > >>Coloring isn't useful. If it was, it would be implemented ~16 years > > > >>ago. > > > > > > > >Congratulations, this is the most stupid argument i've ever read on > > > >lkml. > [] > > I would say that while I'm not particularly fond of flashy colors > > everywhere, I think that being able to use colors to indicate particular > > actions in progress or conditions can be a good thing. RAID errors, > > devices disabled due to command-line parameters, and general anomalies > > which can cause a hang or panic a few line laters are worth coloring. > > That *is* the coloring, i'm talking about. > > > And I don't believe in userland's help here, because for that type of > > messages, the indication should be returned immediately. > > In the very buggy cases, i think, everything just hang. Otherwise > initramfs stuff can deal with it. > > > For instance, anyone who has experienced read errors on and IDE disk > > knows that it can literally take hours/days to boot, after displaying > > thousands of messages. Here, having the ability to see that no IRQ was > > assigned or something like this could help. > > As i'm pretty much in all that text(tty)-mode stuff anyway, maybe after > some time i will propose something klibc/tty based. Mainly a bit of user > interface: split scrolling regions for errors and notifications; flexible > color schemas (keyword highlighting); keyboard events. Of course it will > work in such IDE cases, only if driver is a module. But what I cannot understand is how you expect userspace to work while the lines are being displayed. If this is just to repaint the screen once everything is up, it is 100% useless. I'm interested in seeing errors _while_ they are happening. Basically, I need no color if the machine boots correctly. Willy - 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/