Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!dogie.macc.wisc.edu!decwrl!shlump.nac.dec.com!mipsbx!thomas
From: thomas@mipsbx.nac.dec.com (Matt Thomas)
Newsgroups: comp.unix.ultrix
Subject: Re: Logging dlogin session to VMS
Message-ID: <7403@shlump.nac.dec.com>
Date: 12 Jan 90 00:39:05 GMT
References: <9269@cbmvax.commodore.com> <9225@cbmvax.commodore.com> <1995@eric.mpr.ca> <7225@shlump.nac.dec.com> <7256@shlump.nac.dec.com>
Sender: newsdaemon@shlump.nac.dec.com
Reply-To: thomas@decwrl.dec.com
Organization: Digital Equipment Corporation
Lines: 22

In article <9269@cbmvax.commodore.com>, grr@cbmvax.commodore.com (George
Robbins) writes:
> I guess this is an issue, but opening /dev/tty conveys no obvious advantage
> over duping or using stdin/stdout.

dlogin does not (repeat that: does not) open /dev/tty.  it uses stdin/stdout.

>                                     Even with the flow control/input purge
> problem, it would still be possible to "talk" to a VMS system from the
> shell using standard pipe techniques, which is the kind of capability you
> want to preserve as far as possible in the unix environment...

Depending *if* I can warp dlogin to accept a pipe/socket/fifo as input
(those pesky
tty ioctl's could be a problem), I *might* allow dlogin to read from a
pipe/socket/fifo
as well as from a tty.  No promises and don't count on it.
-- 
Matt Thomas                     Internet:   thomas@decwrl.dec.com
DECnet-ULTRIX Development       UUCP:       ...!decwrl!thomas
Digital Equipment Corporation   Disclaimer: This message reflects my own
Littleton, MA                               warped views, etc.