From owner-freebsd-current Tue Feb 17 05:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21698 for freebsd-current-outgoing; Tue, 17 Feb 1998 05:25:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from murkwood.gaffaneys.com (dialup7.gaffaneys.com [208.155.161.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21687 for ; Tue, 17 Feb 1998 05:25:09 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.8/8.8.6) id HAA27746; Tue, 17 Feb 1998 07:24:45 -0600 (CST) Message-ID: <19980217072445.51226@gaffaneys.com> Date: Tue, 17 Feb 1998 07:24:45 -0600 From: Zach Heilig To: Terry Lambert Cc: sthaug@nethelp.no, nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: devfs persistence References: <17495.887701138@verdi.nethelp.no> <199802171057.DAA10576@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199802171057.DAA10576@usr07.primenet.com>; from Terry Lambert on Tue, Feb 17, 1998 at 10:57:48AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 17, 1998 at 10:57:48AM +0000, Terry Lambert wrote: > > - ln -s cuaa0 mouse > This is somewhat non-sensical as well. The mouse should use a protocol > virtualizer so that a /dev/mouse is reexported, and it doesn't matter > what your physical mouse hardware is, the thing looks like a mousesystems > (or other) mouse, always, so that programs don't have to care about this. > I think your problem is that the current mouse interface is so primitive. Actually, as long as daemons can make entries for devfs (in this case, moused), everything would make sense again. -- Zach Heilig -- zach@gaffaneys.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message