Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!ultima!kralizec.zeta.org.au!godzilla.zeta.org.au!not-for-mail From: bde@kralizec.zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.bugs Subject: Re: PROBLEMS WITH FreeBSD Date: 8 Jan 1994 13:10:10 +1100 Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis and v.42bis Lines: 22 Message-ID: <2gl4m2INNiq@godzilla.zeta.org.au> References: <CIq8w7.7rM@csi.compuserve.com> <2g2ere$esn@solaria.mil.wi.us> <2g4itv$fbu@wzv.win.tue.nl> <2g8dtb$b7c@solaria.mil.wi.us> NNTP-Posting-Host: godzilla.zeta.org.au In article <2g8dtb$b7c@solaria.mil.wi.us>, Joe Greco <jgreco@solaria.sol.net> wrote: >If you have a hard wired terminal, you don't particularly care if there are >bidir capabilities, you simply don't do stupid things like accessing the >outgoing device. Setting clocal to handle such devices has the advantage of being Standard. >machine. I was a tad exasperated when I saw the first few lines in sio.c, >and a lot more irritated by the omission of "COM_BIDIR" in GENERICAH. > >This seems like a pointless and unfortunate kernel omission, unless there is >some disadvantage to COM_BIDIR that I am overlooking. One reason that COM_BIDIR is not the default is that it has some known bugs. E.g., you have to set clocal to use the dialout port, and clear clocal to (securely) use the dialin port, and the driver doesn't enforce the correct settings, and neither does getty. This bug is fixed in the current (unreleased) version of FreeBSD. -- Bruce Evans bde@kralizec.zeta.org.au