From owner-freebsd-questions Tue Mar 19 17:50:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA20215 for questions-outgoing; Tue, 19 Mar 1996 17:50:08 -0800 (PST) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA20210 for ; Tue, 19 Mar 1996 17:50:05 -0800 (PST) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id RAA11241; Tue, 19 Mar 1996 17:50:26 -0800 Date: Tue, 19 Mar 1996 17:50:26 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Brian Queen cc: questions@FreeBSD.ORG Subject: Re: devices&/dev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, Brian Queen wrote: > I got a few good tips on this the other day, but I > need a bit more. > > If I do a MAKEDEV mouse, or even a MAKEDEV standard, > how does MAKEDEV know to use sio0 or whatever? It doesn't. If you have a serial mouse on sio0/COM1 and are installing X as recommended, you make the symlink yourself: ln -s /dev/cuaa0 /dev/mouse Then specify the Device as "/dev/mouse" in XF86Config. Optionally you can dispense with that and just put /dev/cuaa0 as the Device. Section "Pointer" Protocol "Microsoft" Device "/dev/cuaa0" Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major