Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!SAMADAMS.PRINCETON.EDU!tr
From: tr@SAMADAMS.PRINCETON.EDU (Tom Reingold)
Newsgroups: comp.sys.att
Subject: Re: VT Initialization
Message-ID: <9103170740.AA03323@samadams.Princeton.EDU>
Date: 17 Mar 91 07:40:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Noo Joizy -- The Cultural Mecca
Lines: 25

In article <1991Mar05.175251.15013@chinet.chi.il.us>
les@chinet.chi.il.us (Leslie Mikesell) writes:

$ [...]
$ 
$ Now what I'd like is a way to (a) automatically start up an assortment
$ of things on the different VT's when I log in, and (b) a way to
$ access them (saved screen and all) from a dial-up or network login.

As for (a), why not check for the tty name in your ENV file and act
upon that?

As for (b), my strong suspicion is that VT's are made possible by a
device driver that reads the keyboard and writes the video board
directly.  Accessing them remotely would mean writing a replacement
device driver: difficult.  Maybe one day, someone will rewrite "screen"
to run under System V.  Maybe one day *I* will do it.  Well, by the
time I can get around to it, everyone will have windowing systems
running over packet switched networks so it we won't want VT's any
more.
--
        Tom Reingold
        tr@samadams.princeton.edu  OR  ...!princeton!samadams!tr
        "Warning: Do not drive with Auto-Shade in place.  Remove
        from windshield before starting ignition."