[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: serielle console/headless clients

Phil Meyer wrote:
ronald wrote:
following the last discussion about headless clients.

one question:
are there differences between the setup for a serielle console (esp. catch kernel panic's)


the setup for headless clients ?
Serial console is serial console, whether server or client. On PC type hardware, the BIOS does not support serial console any more. There used to be jumper switches on the mother board to force serial console, but since the death of MS DOS, that option no longer exists.

However, once serial console is set up, (whether SUN, HP, IBM, PC, etc) the real question is how to capture it for later study in case of issues, and still be able to use it when needed.

This is what good terminal servers do. There are several terminal servers that store lots of screens of console data.

In a data center where people know what to do, terminal servers rule instead of KVMs. There are differences in commercial terminal servers. Some have lots of memory per port, some do not. Check before purchasing.

Here is an interesting plan and discussion for making a PC with lots of serial ports into a terminal server with capabilities of storing as much console data as you could want.


Its worth a read for those who may not have done allot of serial consoles, and also explains why this is a good thing.

Good luck!

thx for support.

okay, my question was not clear.
i to get caught at this entry:

serial ['--unit=unit'] ['--port=port'] ['--speed=speed'] [Command] ['--word=word'] ['--parity=parity'] ['--stop=stop'] ['--device=dev']

having/working/booting with the *kernel parameter's only* to capture (my) panic's, etc, up to now. so, my thought was: for what do i need to specify a *2cd* entry to configure it.

walking through the docs mentioned here
(good and informative links. my night work yesterday, -sorry- today)

i realized that this - iirc- is needed to capture the bootloader screen also, where *screen* should be without graphical stuff.

bios capturing is another "road works"...
(dictionary: baustelle := road works (?))


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]