Re: [Netconsole-devel] Should netcon be a virtual screen-based protocol?

[<li...@ho...>]

> Originally I said "of course not", but in the car today I started to
> wonder about it.  A (text) virtual screen would fit nicely in a single
> UDP datagram, and would make it very easy to map native console
> operations -- how weird they may be -- onto the virtual screen.  The
> downside is that it makes server-side logging and scrollback harder.

Well, 80x25 characters (never mind attributes) is larger than 1500 bytes.
Do we want to require support for fragmentation?

> Thoughts on this subject?

It also makes defining "catching everything" for logging a bit difficult.

It would theoretically permit using BIOS setup utilities across the
protocol, but is the probability of the support being added non-negligible
enough to worry about it?  What other benefits are there?


It *would* be kind of nice for a Linux boot loader to convert the text-mode
BIOS screen to console logs for dumping, similar to the way that the
various stages manage to coordinate the screen cursor and not overwrite
each other...