lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071007212311.GB27685@elte.hu>
Date:	Sun, 7 Oct 2007 23:23:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Oleg Verych <olecom@...wer.upol.cz>
Cc:	Willy Tarreau <w@....eu>, Rene Herman <rene.herman@...access.nl>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	Krzysztof Halasa <khc@...waw.pl>,
	Medve Emilian-EMMEDVE1 <Emilian.Medve@...escale.com>,
	Helge Deller <deller@....de>
Subject: Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:'
	usage"


* Oleg Verych <olecom@...wer.upol.cz> wrote:

> > 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.

Jan's code is here today and it works fine for me. How can you 
coherently argue against the plain fact that his feature solves my 
usecases perfectly fine, while your hypothetical solution clearly does 
not solve them? (Although i'm not too hopeful you'll give me a straight 
answer to my straight question, given your track record on lkml. It is 
almost as if you were more interested in ranting and in controversy than 
in the progress of Linux.)

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ