From owner-freebsd-questions Mon Jan 4 19:01:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17282 for freebsd-questions-outgoing; Mon, 4 Jan 1999 19:01:21 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from elemental.alchemy.com (elemental.alchemy.com [206.58.126.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17275 for ; Mon, 4 Jan 1999 19:01:11 -0800 (PST) (envelope-from steve@alchemy.com) Received: from elemental.alchemy.com (elemental.alchemy.com [206.58.126.23]) by elemental.alchemy.com (8.9.1/8.9.1) with SMTP id SAA07806; Mon, 4 Jan 1999 18:59:00 -0800 (PST) Date: Mon, 4 Jan 1999 18:58:55 -0800 (PST) From: Steve Willoughby To: Ludwig Pummer cc: rick hamell , Marc Giannoni , freebsd-questions@FreeBSD.ORG Subject: Re: Console Switchboxes In-Reply-To: <4.1.19990104165644.00b60100@mail-r> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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