On Wed, 28 Apr 1999, Matt Clay wrote:
> It sounds like you have a problem similar to one I'm working on. I'm
> trying to connect a telnet session to a program running in DOSEmu that
> uses the com port/modem for input/output.
>
> My approach so far (to avoid using null modem cables), is to use pseudo
> tty's. They are devices that come in pairs like "/dev/ptypN" and
> "/dev/ttypN". Where N is a single hex digit. You should be able to run
> agetty on "/dev/ptypN" and tell DosEmu to use "/dev/ttypN" as the com
> port (I havn't actually done it this way myself). Make sure you use a
> psuedo tty that is not already in use (telnet connections use psedo
> tty's).
Thanks for advice.
I tried several configurations with pty's and tty's with no success.
Most promising was to use named pipe and redirect bash stdin and stodu to
to it like
bash <> /dev/testpipe
and configuring this pipe as a serial devide at dosemu.conf. Most os the
stuff went thru but for reason or another not all stdout. All stderr text
were missed.
More strange this worked only with com2:, not com3: for example.
I thingk it would be useful feature to broaden serial device redirection
for example to to test terminal emulator / workstation / network stack
programs usin only single machine. Unfortunately i am not skilled enough
to make these drivers myself:<
--
Ari Moisio, Niittykatu 7, 41160 Tikkakoski, +358-40-5055239
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
PGP 0x3FAF0F05, fp 8A91 96E2 9864 D04D 575E 3EEE 72E9 DDD2
WWW: http://www.sci.fi/~armoi,http://www.arlainst.fi/~arimo
