Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!milano!cactus.org!wixer!dpm From: dpm@wixer.bga.com (David Maynard) Subject: Re: /dev/com1 on NetBSD 0.9 Message-ID: <1993Sep10.172611.1546@wixer.bga.com> Organization: Real/Time Communications References: <26oup9$aaf@agate.berkeley.edu> Date: Fri, 10 Sep 1993 17:26:11 GMT Lines: 26 In article <26oup9$aaf@agate.berkeley.edu> sky@soda.berkeley.edu writes: >For some reason I don't seem to have a device driver for com 2 (/dev/com1) >on my NetBSD 0.9 system. The bootup sequence recognizes its existence, but >neither make com1 or make com* will create it. What am I doing wrong? There is a bug in the MAKEDEV script related to the new device names (tty0?). "MAKEDEV tty01" doesn't work, but "MAKEDEV com1" does. The "MAKEDEV std" command uses the 'tty01' name, so it isn't created in the standard distribution. You can create the device by hand, but I recommend "MAKEDEV com1" since it will create the link from com1 -> tty01 and will set the device owner/mode correctly. On a related note, the XFree86 install script also needs to be updated to deal with the new kernel and com port names. I plan to submit an offical bug report and fix for the MAKEDEV problem later today. I would have submitted it sooner, but I had a disk head crash yesterday (before doing a 0.9 backup :-( ). I thought IDE disks were supposed to fix themselves! -David -- David P. Maynard, Carnegie Mellon University & Dependable Solutions USMail: 14312 Richard Walker Blvd, Austin, TX 78728-6862 EMail: dpm@depend.com, Tel: +1 512 251 8122, Fax: +1 512 251 8308