Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!ncar!noao!arizona!arizona.edu!UAVAX0.CCIT.ARIZONA.EDU!CITDEM
From: citdem@UAVAX0.CCIT.ARIZONA.EDU
Newsgroups: comp.sys.next
Subject: How do I restore /dev/cua?
Message-ID: <00949B71.E30D81A0@UAVAX0.CCIT.ARIZONA.EDU>
Date: 6 Jun 91 03:29:59 GMT
Reply-To: citdem@UAVAX0.CCIT.ARIZONA.EDU
Distribution: na,local
Organization: University of Arizona
Lines: 11
Nntp-Posting-Host: uavax0.ccit.arizona.edu

Well, it's happened again: another NeXT/Mach novice has stumbled and needs
a helping hand.  I clobbered /dev/cua.  Then I tried to restore by cp'ing
from my 2.1 OD.  No. No. No.  So (ahem), just how does one restore 
/dev/cua?

A related question (guess why /dev/cua was clobbered): if a serial port is
busy/locked, how does one free it up?  This all started because I brought
my Cube down too fast during a sudden T'storm.  I think I forgot to exit
kermit.  Now kermit and the modem aren't talking.  Other possibilities?

Don McCollam  (citdem@uavax0.ccit.arizona.edu - ASCII responses only, please)