Return to BSD News archive
Newsgroups: comp.os.386bsd.misc 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!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (A Wizard of Earth C) Subject: Re: Using the sio ports for terminals w/o modem ctl signals Message-ID: <1993Aug15.232601.17314@fcom.cc.utah.edu> Sender: news@fcom.cc.utah.edu Organization: Weber State University, Ogden, UT References: <CBJnzu.6nG@obiwan.uucp> <1993Aug10.193616.16846@fcom.cc.utah.edu> <24grraINNl92@kralizec.zeta.org.au> Date: Sun, 15 Aug 93 23:26:01 GMT Lines: 33 In article <24grraINNl92@kralizec.zeta.org.au> bde@kralizec.zeta.org.au (Bruce Evans) writes: >In <1993Aug10.193616.16846@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >There might still be problems from broken programs such as getty blindly >turning CLOCAL off. Why would getty leave CLOCAL set on a modem? I don't understand. If DCD drops, my applications are supposed to get SIGHUP. You are suggesting that it's OK to leave my root shell up there for the next caller. It's possible that the DCD dropped not because I was stupid and didn't log out first, but because I had a power failure on my end but not the host end. Is it still implied to be "my fault" that the next caller gets root access to the machine? >>The correct way to handle this is to have a different driver for the board >>so that it ignores it before making requirements on the board at all; if the >>board provides these signals as "floating", it's a broken board. From >>what I remember of the thing, it doesn't, and you *do* need a different >>(or at least indifferent 8-)) driver. > >It is sufficient to have a non-broken board and/or cables with DCD wired on. I'd like to see you strap DCD on an internal modem. If the answer is that I should buy different hardware, my answer is that software is to make up for the deficiencies of hardware (at least driver software). It is the responsiblity of software engineers (like myself) to *make it work* where possible, come hell or high water. Anything else violates the rule of least astonishment (one of the seven deadly software sins). Terry Lambert terry@icarus.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.