Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!news.duke.edu!news-feed-1.peachnet.edu!emory!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!bigbang.astro.indiana.edu!ahabig From: ahabig@bigbang.astro.indiana.edu (Alec Habig) Subject: tty vs cua Message-ID: <Cstx0K.7qL@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: bigbang.astro.indiana.edu Organization: Indiana University Astrophysics, Bloomington, IN Date: Tue, 12 Jul 1994 13:19:32 GMT Lines: 22 In repsponse to the various complainst about using tip/kermit on tty, and the clocal hack not working anymore, I decided to try using the cua device instead. However, a MAKEDEV tty* nets me the following devices : tty01 tty02 cua03 The tty's are correct (I've got a slightly twisted setup), but why on earth cua03? Ok, sez I, I'll just MAKEDEV cua02 (my modem). Bzzzt. It seems that the "make tty" and "make cua" parts of the MAKEDEV script are mutually exclusive. Each section rm's _all_ tty's and cua's before making anything! So using MAKEDEV as written will land you either tty's or cua's, not both. I was under the impression that cua's were simply another incarnation of the tty's. Why can't they coexist? Is it safe to hack MAKEDEV to let me build cua02 along with my tty's? (tty01 is my mouse port, after all!). And why on earth was cua03 built when I made tty* - sio3 is even commented out in my kernel! Alec