* Oleg Verych <[email protected]> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
