Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!news.unomaha.edu!news.mtholyoke.edu!world!bloom-beacon.mit.edu!ai-lab!life.ai.mit.edu!mycroft From: mycroft@duality.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.questions Subject: Re: Mice/Mail in NetBSD0.9 Date: 09 Nov 1993 00:51:57 GMT Organization: MIT Artificial Intelligence Lab Lines: 53 Distribution: world Message-ID: <MYCROFT.93Nov8195157@duality.gnu.ai.mit.edu> References: <752783802snz@triton.demon.co.uk> NNTP-Posting-Host: duality.ai.mit.edu In-reply-to: paul@triton.demon.co.uk's message of Mon, 8 Nov 1993 18:36:42 +0000 (You should have emailed netbsd-help@sun-lamp.cs.berkeley.edu.) In article <752783802snz@triton.demon.co.uk> paul@triton.demon.co.uk (Paul Medcalf) writes: Could anybody give me some simple instruction on how to solve mouse problems with serial mice. You haven't specified what type of mouse you have, or how it's specified in your Xconfig file. I read a single line on this in the FAQ's and install docs, that said it was an OS problem and to try connecting to it with tip/cu. This isn't very helpful unless you know the code to send to the mouse to get it to start sending data. That depends on the type of mouse. In this case I get the connected message, and my system hangs. You mean `tip hangs'? That's not surprising. tip was never meant for that usage. If anything, try cu. +++<ctrl Z> will not exit either. That's a modem control sequence. It is on dos com1 (BSD com0 ?). Dos can see it, BSD cant. What do you mean by that? It's called `com0'. Is that listed during boot or not? Q. Vanilla Netbsd 0.9 installs with a com1 linked to tty01 and no com0. I did a MAKEDEV com0 which then linked com0 to tty00. Is this correct ? Are you sure those aren't vestiges of a 0.8 system (which numbered the com ports starting with 1)? I *just* checked the distribution files, and there is certainly a com0 in there. Q. I created an entry in /etc/remote called com0:com0:dv=/dev/com0 wth a baud rate of 9600. Do I need to simply tip com0 ? See above. By the way, sendmail does not appear to have a default sendmail.cf for me to hack about. It would be very hard for us to provide a generic sendmail.cf. Our feeling is that it is better to simply not provide one and have users create their own before using sendmail than to supply one which does the wrong thing on most machines.