Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!naitc!karl From: karl@naitc.uucp (Karl Denninger) Newsgroups: comp.unix.sysv386 Subject: Re: PD uugetty for Interactives 386/ix? Summary: More on drivers and the like Message-ID: <1990Sep12.191012.19760@naitc.uucp> Date: 12 Sep 90 19:10:12 GMT References: <9009011253.AA13674@esegue.segue.boston.ma.us> <1990Sep03.060502.27179@ddsw1.MCS.COM> <1990Sep09. <3QBJ5BI@geminix.mbx.sub.org> Reply-To: karl@naitc.naitc.com (Karl Denninger) Organization: A.C. Nielsen Bannockburn, IL Lines: 62 In article <3QBJ5BI@geminix.mbx.sub.org> gemini@geminix.mbx.sub.org (Uwe Doering) writes: >I haven't fixed the line discipline. First, the design goal for the >dialout ports with modem control was that their behaviour is the same >as with getty ports, with the only difference that they ignore the >DCD line until this line goes to high. After that it will behave >exactly like the getty ports...... Ok, I guess that's ok. It's not quite what I had in mind, but it should work ok for most purposes. >I can assure you that there are only few (if any) problems with real- >world applications and FAS. This DCD behaviour was the same with all >previous releases of FAS, and I yet have to find a program that refuses >to work on the dialout port. I haven't got any reports about this issue, >either. > >Therefor, I still think it's much worse to let a program read/write >from/to the port when it isn't supposed to, than to disable the port >until the program explicitely sets it up again either by closing and >reopening the port or by an ioctl call with the TCSETA{W|F} command. >As I said this works with all the programs I've used so far. And >if a program wants to ignore DCD completely it can do so by setting >the CLOCAL termio(7) flag. That is ok, providing that O_NDELAY toggling and control is properly implemented. You've said that it is; this is good. >>>BTW, FAS 2.07 (not yet released) _will_ have VP/ix support. You won't >>>need the X5/X6 drivers any more. :-) >> >>For outgoing connections AND terminal use? Half the solution doesn't do >>much; if I can run a mouse off it (ie: COM1MOUSE works) then you've got >>something. > >Yes, COM1MOUSE works as well as COM1, and you can use COM2 at the same >time. I've used the telecommunication program Telemate 2.10 to talk >to a modem on COM2 while I could move the mouse cursor with a mouse >on COM1. That's necesasry in order to be able to say you have VP/ix support. More than one vendor doesn't do the second half of the job... >And if you dial in via a modem (or have a dos mode terminal connected >to the computer) you can start VP/ix directly on this serial line. >I tried this with a VT100 terminal emulation and to my surprise I >could use several fullscreen DOS applications. :-) Even if the modem >carrier drops while you are in VP/ix the DOS emulator won't hang the >line but instead will exit due to a SIGHUP signal. > >Karl, is this what you had in mind? Yes, it is. Unfortunately, it only handles dumb ports. Too bad; you can't get enough of them in with a reasonable impact on the system, even with 16550's. -- Karl Denninger AC Nielsen kdenning@ksun.naitc.com (708) 317-3285 Disclaimer: Contents represent opinions of the author; I do not speak for AC Nielsen on Usenet.