----- Original Message -----
From: "Bob Rasmussen" <ras@anzio.com>
To: "Brian K. White" <brian@aljex.com>
Cc: <sco-misc@lists.celestial.com>
Sent: Monday, March 17, 2008 3:14 PM
Subject: Re: Remote Control a terminal or the console.


> On Sun, 16 Mar 2008, Brian K. White wrote:
>
>> ...
>> If I could find a windows programmer to pay to finish my few remaining hacks
>> to Putty, and port my existing hacks up to the current putty, then I could
>> finally escape facetwin and get dv-like functionality back in the form of
>> ttysnoop. *sigh*...
>
> What are you looking for in Putty in this regard?

Nothing to do with tty sharing, that would just be a side effect.
Currently I have a 0.58 or 0.59 based putty with:
* run-program escape sequence
* passthru print flush timer (stock putty causes a page-eject every time filepro toggles the printer off during a report where screen updates are interspersed with print data)
* ability to load settings from a url (instead of windows registry)
* ability to auto-launch putty from a web link and auto load settings mentioned above.

Thise are a great and major start, and I use that version myself for all my day to day admin stuff and application development and testing the same app that the users use via facetwin, just so it gets as much testing as possible and I have a good chance to hit any glitches myself before users.
But it's not yet good enough for production until I also add:
* Automatically discover the default windows printer on the fly and use it by default if the settings don't define a printer or maybe if the settings define a special value that means automatic. (So I can have a web link to a highly configured set of settings, and have everyone use that same link, yet everyones printer works who's default printer is pcl capable.
* Ability to optionally, easy/simply, save the current settings to a local file (or registry I guess, though a file is so much handier for emailing, copying to a new pc, etc...) So people can log in via the web link, to get a correct set of settings that I have configured to start with, and then customize it locally by defining a non-default printer, storing the login name & password, font size/window size, etc..
* Ability to store the name & password in the settings in a SIMPLE direct manner, and works regardless which connection protocol telnet/rlogin/ssh/serial. no ssh keys.

Then, not necessary, but would be nice to also port my existing mods from 0.5x to 0.6x. I had someone look at it and they said that 0.60 is very different from 0.5x and they basically couldn't do it because the guy who actually did my original work was gone and no one else was familiar enough with it.

What this has to do with tty sharing is not even about putty but the server daemons. putty connects to telnetd, rshd, sshd, or getty, all of which ttysnoop works with. So, if I can ever finish getting putty hacked on to the point where I can actually put it into production, I'll regain dv-like functionality in the form of ttysnoop. I can't use dv itself because it's too kernel specific and I don't happen to use any kernels it supports, and even if I did, I know that in 10 minutes I may change the kernel and thus break dv, so I'd be dumb to use something that I knew would break that easily, or that would prevent me from managing my systems as I wish/need just so as not to break dv. I don't think I can use spyfs either, I never saw any source code for it and I think it was specific to the sco osr5 kernel.

--
Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!