In comp.sys.laptops Jaz <harbell@beerburp.com> wrote:
> On Wed, 12 Oct 2005 21:18:19 +0200, "Peter T. Breuer"
> <ptb@oboe.it.uc3m.es> wrote:
>>In comp.sys.laptops Jaz <harbell@beerburp.com> wrote:
>>> and use a terminal proggie, but if the console happens to be on the
>>> video or if it's running Windows...
>>
>> ... you run VNC.
> The idea is to have a console, not a terminal. The console allows
> watching the post while booting, etc.
That's not the salient difference - you are talking about a bios
function, sending post messages to a particular device. It's not
affected by what kind of device you are using, but by what device the
bios is sending the messages to, something which depends on the bios,
what it may be configured to do, and the hardware that the bios works
with. You need a "server bios" that can do i/o to the serial line i/o
port address and irq or elsewhere. It's nothing to do with what you
have as a device, nor with what operating system (will be) running.
> Thus, it has to use the HD15/vga
> and PS2 connectors of the client/rack-server/etc.
There is no "thus". If you want to watch the whole kaboodle, including
post, you might as well get proper server hardware/mobo/bios that can
send that kind of thing out across the net or a serial line.
If you are happy with just watching the o/s kernel messages, then you
can get away without the special hardware, because the kernel can
substitute for the hardware. If you are happy with just watching
everything AFTER the kernel has booted, as I assumed you were saying,
as you said "if it's running Windows" (which implies that Windows is
running, and hence has already booted), then VNC will do you fine.
>>
>>> IP-based solutions are a pain; Raritan Dominion, which is small,
>>> requires a power brick, and ties up the network port, etc.
>>
>>Use wireless? Or run ppp or slip over the serial line. You can
I should also point out that you "don't tie up a network port" by using
the net. The net deals with huge numbers of packets at a time.
Actually, server bioses or kernels with a network console DO send out
packets on a UDP port (either broadcast or single-target, as
configured), but I wouldn't call that "tying up" a port. You are free to
ignore those packets on the net in any client, etc. etc..
>>I rather like your description "pcmcia kvm"! Look it up on google!
>>http://www.kvm-switches-online.com/aten.html may well have something
>>you like.
> [please excuse the burp when replying]
I heard nothing over here. Can you repeat?
Peter