From owner-freebsd-questions  Tue Jul 16 18:58:47 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA02557
          for questions-outgoing; Tue, 16 Jul 1996 18:58:47 -0700 (PDT)
Received: from homer26.u.washington.edu (durang@homer26.u.washington.edu [140.142.78.16])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA02550
          for <questions@freebsd.org>; Tue, 16 Jul 1996 18:58:45 -0700 (PDT)
Received: from localhost by homer26.u.washington.edu
	(5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA27860;
	Tue, 16 Jul 96 18:58:38 -0700
Date: Tue, 16 Jul 1996 18:58:38 -0700 (PDT)
From: Ken Marsh <durang@u.washington.edu>
To: questions@freebsd.org
Subject: MAKEDEV making symbolic link, not mouse dev.
Message-Id: <Pine.A32.3.92a.960716185047.22821B-100000@homer26.u.washington.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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....

Thanks to all those who responded to my fstab problem, it works fine now.
Thanks in advance to any who will shed light on my mouse dilemma.

Ken Marsh