On 2012-12-30 04:22, sampsa at mac.com wrote:
Yeah, RHESUS does the DECNET stuff - I actually screen scrape the results of http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
So there are DECNET operations, but the results are delivered over HTTP :)
Yikes! Well, that works, I guess. :-)
I'm sure we could throw something native together in no time, and make it totally internal to rhesus... :-)
Johnny
Well Python does run on RHESUS so I could do a bunch of stuff that way.
But this works, so until it stops working, I'll leave it :)
Fair enough.
BTW, do you want to write something for the top section of the HLP file?
Currently I just copy pasted the website stuff.
Nothing right now anyway. Might get back to you some other time, if I feel inspired. :-)
Johnny
On 2012-12-30 04:16, sampsa at mac.com wrote:
Ok. But how do you pull the INFO.TXT files from other machines here?
I can see that you can pull files out using ftp, and then process them on your Unix machine, and put the result back, but there are some DECnet operations in here...
Yeah, RHESUS does the DECNET stuff - I actually screen scrape the results of http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com
So there are DECNET operations, but the results are delivered over HTTP :)
Yikes! Well, that works, I guess. :-)
I'm sure we could throw something native together in no time, and make it totally internal to rhesus... :-)
Johnny
On 2012-12-30 03:58, sampsa at mac.com wrote:
Curious - do you have a Unix system on which you run this then. What kind of Unix system did you manage to talk DECnet good enough?
Or how does this hang together, since you're using cron it's obviously driven by Unix somewhere in the back...
Same box that runs the bridge.
Basically, I've got a Python script that scrapes the rhesus.sampsa.com info's, adds any local customized help files to that, and FTPs it to RHESUS.
Ok. But how do you pull the INFO.TXT files from other machines here?
I can see that you can pull files out using ftp, and then process them on your Unix machine, and put the result back, but there are some DECnet operations in here...
Johnny
Curious - do you have a Unix system on which you run this then. What kind of Unix system did you manage to talk DECnet good enough?
Or how does this hang together, since you're using cron it's obviously driven by Unix somewhere in the back...
Same box that runs the bridge.
Basically, I've got a Python script that scrapes the rhesus.sampsa.com info's, adds any local customized help files to that, and FTPs it to RHESUS.
Sampsa
On 2012-12-30 03:46, sampsa at mac.com wrote:
On 30 Dec 2012, at 04:28, Dennis Boone <drb at msu.edu> wrote:
So what's supposed to be in this INFO.TXT file that everyone's been
talking about lately? I think I may be too much of a newcomer here to
know about it. Where should it be, and what should it contain?
Bob has a nice explanation in his INFO.TXT file on LEGATO.
Yup. Be aware that the HLP compiler cuts out any text after the .BEGIN-HECNET-INFO bit so put anything you want in the help files ABOVE that.
Speaking of HLP compilers, I've set up a cron job to run on Sundays at 0500 EET, my robot will be sending update notices to the list when they happen.
Curious - do you have a Unix system on which you run this then. What kind of Unix system did you manage to talk DECnet good enough?
Or how does this hang together, since you're using cron it's obviously driven by Unix somewhere in the back...
Johnny
On 30 Dec 2012, at 04:28, Dennis Boone <drb at msu.edu> wrote:
So what's supposed to be in this INFO.TXT file that everyone's been
talking about lately? I think I may be too much of a newcomer here to
know about it. Where should it be, and what should it contain?
Bob has a nice explanation in his INFO.TXT file on LEGATO.
Yup. Be aware that the HLP compiler cuts out any text after the .BEGIN-HECNET-INFO bit so put anything you want in the help files ABOVE that.
Speaking of HLP compilers, I've set up a cron job to run on Sundays at 0500 EET, my robot will be sending update notices to the list when they happen.
Sampsa