Re: serielle console/headless clients

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

 



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

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

http://searchopensource.techtarget.com/tip/0,289483,sid39_gci1118136,00.html

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

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/console-server/article.html

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
https://www.redhat.com/archives/fedora-list/2006-September/msg00604.html
(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 (?))

	ronald


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux