Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!ftpbox!mothost!delphinium.cig.mot.com!zeus!aztec!essenl From: essenl@aztec.swindon.rtsg.mot.com (Lee Essen) Newsgroups: comp.os.386bsd.questions Subject: Re: more NetBSD/modem questions Date: 1 Feb 1994 13:31:38 GMT Organization: Motorola Ltd., European Cellular Infrastructure Division Lines: 34 Sender: essenl@aztec (Lee Essen) Distribution: world Message-ID: <2illjq$ieo@zeus.swindon.rtsg.mot.com> References: <2ikepi$r1l@portal.gmu.edu> NNTP-Posting-Host: aztec.swindon.rtsg.mot.com In article <2ikepi$r1l@portal.gmu.edu>, twallace@mason1.gmu.edu ( ) writes: [stuff deleted] |> These are the pertinant facts: |> 1. I recently added a serial port to Zippy, and it shows up as |> being properly installed both in the AMI bios and during the NetBSD |> boot. During the boot it says it is com0. |> |> 2. There is a file /dev/com0. When I do a ls -l com0 I get the |> following: |> lrwxrwxrwx 1 root wheel 5 Dec 9 21:57 com0 -> tty00 |> I have no idea what this means. This means that the file com0 is 'symbolically linked' to tty00. This basically means that any access to com0 will actually act on tty00. So you need to check the permissions on /dev/tty00 and make sure that the major and minor device numbers are correct. If in doubt, I think you can type (in /dev)... ./MAKEDEV com0 Which should create a character device with a major device number of 8 and a minor of 0. The default ownership is uucp.wheel. Hope thats useful. Lee. -- MIS Technical Support Email: essenl@aztec.swindon.rtsg.mot.com Motorola Ltd Phone: +44 793 545336 16 Euroway, Blagrove Swindon, Wiltshire SN5 8YW