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!wupost!howland.reston.ans.net!xlink.net!math.fu-berlin.de!irz401!uriah!not-for-mail
From: j@bonnie.tcd-dresden.de (J Wunsch)
Newsgroups: comp.os.386bsd.questions
Subject: Re: What do com[0-2] represent in DOS terms?
Date: 5 Jul 1993 17:45:17 +0200
Organization: Textil Computer Design GmbH, Dresden, Germany
Lines: 14
Message-ID: <219iadINNa5r@bonnie.tcd-dresden.de>
References: <1993Jun30.143558.26430@news.weeg.uiowa.edu>
NNTP-Posting-Host: bonnie.tcd-dresden.de
In article <1993Jun30.143558.26430@news.weeg.uiowa.edu> jboggs@news.weeg.uiowa.edu (John D. Boggs) writes:
>I have /dev/com[0-2] on my NetBSD system. /dev/com0 seems to be hooked
>up to my machine's COM1 port. Is it safe to assume that /dev/com[1-2]
>are COM2 and COM3?
>
It appears so. (I'm not totally sure, still have an older 386bsd.)
The /dev/com* is for the sake of dos users, traditional unices have
a naming convention of /dev/tty00... which i'd still prefer. Makes
better sense when looking at the ps(1) output.
--
in real life: J"org Wunsch | ) o o | primary: joerg_wunsch@tcd-dresden.de
above 1.8 MHz: DL 8 DTL | ) | | private: joerg_wunsch@uriah.sax.de
| . * ) == |
``An elephant is a mouse with an operating system.''