From owner-freebsd-hackers Sun Oct 12 10:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03835 for hackers-outgoing; Sun, 12 Oct 1997 10:22:00 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03830 for ; Sun, 12 Oct 1997 10:21:54 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA07453; Sun, 12 Oct 1997 11:21:52 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA27665; Sun, 12 Oct 1997 11:21:49 -0600 (MDT) Date: Sun, 12 Oct 1997 11:21:49 -0600 (MDT) Message-Id: <199710121721.LAA27665@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: fnord0: disabled, not probed. In-Reply-To: <12637.876627122@time.cdrom.com> References: <12637.876627122@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ disabled probe messages ] > The only conceivable counter-argument I can see concerns the psm0 > entry which is disabled by default in the distributed GENERIC, it > being a plausible argument that the "psm0: disabled, not probed." > message at boot-time served as a much needed indicator of its disabled > state should the user actually want to have it enabled. On the other > hand, I seem to recall some folks also talking about the ps/2 mouse > driver finally reaching a level of maturity where it could just be > enabled by default, and I'd rather have that happen in any case if > it's possible. I've gotten reports that the PS/2 mouse driver still wipes out some Pentium boxes, so it's still not safe for 2.2 yet. I'm hoping that by enabling it in -current we can get more feedback and possibly find a fix so we can un-disable it in 2.2. As far as writing out 'disabled' I can see value in doing it both ways, so I have no preference. Nate