Date: Mon, 4 Jan 1999 18:58:55 -0800 (PST) From: Steve Willoughby <steve@alchemy.com> To: Ludwig Pummer <ludwigp@bigfoot.com> Cc: rick hamell <hamellr@dsinw.com>, Marc Giannoni <marc@versa.eng.comsat.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Console Switchboxes Message-ID: <Pine.BSF.4.01.9901041839430.7758-100000@elemental.alchemy.com> In-Reply-To: <4.1.19990104165644.00b60100@mail-r>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Jan 1999, Ludwig Pummer wrote:
> Get yourself a nice non-mechanical switchbox. You'll end up doing so in the
> future when the cheap one becomes unusable.
Definately. But I'm having this problem even then. I have a pair of
nice non-mechanical switchboxes which do all the keyboard-spoofing to
all hosts and all that (i.e., if a machine boots, it "sees" a keyboard
even if it's not the one switched to the actual keyboard).
This one (Belkin OmniView) is cascadable so that you can put up to 64
systems on a single console, like this:
_______
[monitor]-----| |
[keyboard]----|_______|
| | | | _______
[cpu1]__| | | |_____| |
[cpu2]____| | |_______|
[cpu3]______| | | | |
[cpu4]_______________| | | |
[cpu5]_________________| | |
[cpu6]___________________| |
[cpu7]_____________________|
but it's not behaving like the manual claims it should either. I get
the same "keyboard loss" problem when switching to any of the CPUs on
the 2nd-tier switchbox. I have to power-cycle the 1st-tier box to get
them back. So nothing's a perfect solution, it seems :)
I guess that's a long winded way to say "Yes, I agree", but you never
know if someone else out there has seen the same issues with the same
hardware.
-Steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9901041839430.7758-100000>