From owner-freebsd-current Sat Aug 11 18:21:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id BD62937B408 for ; Sat, 11 Aug 2001 18:21:22 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f7C1Onb04132; Sat, 11 Aug 2001 18:24:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108120124.f7C1Onb04132@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joe Kelsey Cc: current@freebsd.org Subject: Re: FreeBSD's aggressive keyboard probe/attach In-reply-to: Your message of "Sat, 11 Aug 2001 17:57:02 PDT." <15221.54366.195608.585938@zircon.zircon.seattle.wa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Aug 2001 18:24:49 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Obviously, a purely mechanical switch cannot misbehave in the > way specified--for one thing, you need to take special action to allow > reboot on the machines which are not actively connected to the keyboard, > otherwise they will stop in the BIOS... That "special action" is typically asking the BIOS not to fail on a keyboard error. It's a pretty common feature. > "People" don't complain about KVM's on FreeBSD because the developers > are obviously interested in doing things exactly one way and not > interested in hearing about misbehaviors. The keyboard/mouse code is > quite opaque and needs massive work, but no one seems interested in > doing the work. "People" don't seem to check the CVS logs, or follow up on the lengthy discussions about actual keyboard/mouse behaviour that have been held over the years, nor do they talk to the current, active maintainer of the keyboard/mouse drivers. > Why does FreeBAD cause so much trouble that other OS's seem to be able > to deal with? We don't know. We don't have your hardware, nor your cooperation in order to track it down. > Even now that I have decomissioned the old Solaris x86 box, I still get > the psmintr errors on a standard Logitech wireless mouse. Why? Should > I be stepping thorugh the driver code to figure it out? Yes. > surely others have seen the errors and can deal with them. Surely you have seen the errors and can deal with them. Surely? Why should it be someone else? What prevents you from getting involved? You bitch about "FreeBSD's developers" like you were paying for them or something - and completely miss the point. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message