From owner-freebsd-questions Tue Jul 16 19:09:29 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03502 for questions-outgoing; Tue, 16 Jul 1996 19:09:29 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA03497 for ; Tue, 16 Jul 1996 19:09:23 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id UAA27620; Tue, 16 Jul 1996 20:09:12 -0600 (MDT) Date: Tue, 16 Jul 1996 20:09:12 -0600 (MDT) Message-Id: <199607170209.UAA27620@rocky.mt.sri.com> From: Nate Williams To: Ken Marsh Cc: questions@freebsd.org Subject: Re: MAKEDEV making symbolic link, not mouse dev. In-Reply-To: References: Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am trying to get my mouse going so I can run Xwindows. My mouse comes up > in dmesg as: > > sio0 at 0x3f8-0x3ff irq 4 on isa > > I don't know where I got this, but I suspect the device file to be tty00 > or mouse. However, if I do "/dev/MAKEDEV tty00" then /dev/tty00 is NOT > created, and no error message is given. If I try "/dev/MAKEDEV mouse" then > a symbolic link, /dev/mouse is created, linked to ITSELF.... I don't know why the 'mouse' target exists in MAKEDEV, but that' irrelevant. In any case, if you do a 'man sio', you'll see: FILES /dev/ttyd? for callin ports /dev/ttyid? /dev/ttyld? corresponding callin initial-state and lock-state devices /dev/cuaa? for callout ports /dev/cuaia? /dev/cuala? corresponding callout initial-state and lock-state devices /etc/rc.serial examples of setting the initial-state and lock-state de- vices So, since the mouse 'calls in' (sends data to the system), you would use /dev/ttyd?, where ? is the device number of the port, in your case it would be /dev/ttyd0. Nate