By the way, putting a hostname after file:// does either not work,
or initiates an ftp session...
On Tue, Jan 29, 2013 at 04:40:49PM +0100, Johnny Billquist wrote:
On 2013-01-29 15:29, Erik Olofsen wrote:
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
I suspected as much from the comments in the url you sent.
Seems silly, though. What happens if you just say "file://mim::info.txt" ?
(I must admit that I'm slightly confused on how many slashes are
appropriate...)
Johnny
Erik
On Tue, Jan 29, 2013 at 03:26:01PM +0100, Johnny Billquist wrote:
On 2013-01-29 14:53, Erik Olofsen wrote:
If we may use an url such as mim::something.html, which would normally be a
file:// there would be some basic functionality I think?
Right, since that is basically just using the file: transport/protocol.
The fact that files can be accessed transparently over DECnet makes it
possible to access documents "over DECnet".
Depending on how the parsing/handling of the url for something in the
file: domain is done, this might actually work straight away.
Johnny
Erik
On Tue, Jan 29, 2013 at 02:04:39PM +0100, Johnny Billquist wrote:
On 2013-01-29 13:44, Erik Olofsen wrote:
HECnetters,
Is anyone interested in using Lynx on HECnet?
Using node names in the url is not possible; some information is here:
http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html
On my Alpha with VMS 6.1, I'm able to compile Lynx version 2.3.
It seems that the latest version, 2.8.7, does not compile under VMS 8.3.
Perhaps I'm going to have a look at the old sources; perhaps I'm going
to do something more useful...
Well, the basic "problem" is that there is no http object defined in
DECnet, nor any equivalent to the http protocol, so how would you expect
it to work?
DECnet is not IP, nor TCP.
Johnny
In the meantime I have a working Lynx 2.8.7 and studied the url
parsing in the debugger.
When specifying a VMS file name, it is first converted to a valid url;
then there are many url checks, and of course when the file needs to be
opened, it is converted back to a VMS file specification.
Interestingly (is it a feature or a bug?),
$ lynx file://localhost/rullfs:/.www/simple.html
or just
$ lynx /rullfs:/.www/simple.html
works, because it is assumed that the the first part is a device name,
without a colon, on localhost. But because it already contains a colon,
it is converted to a host specification...
I've not checked yet what happens if http:// is part of the url, and
what needs to be done if there were an html object at the remote host.
Erik
On Tue, Jan 29, 2013 at 04:40:49PM +0100, Johnny Billquist wrote:
On 2013-01-29 15:29, Erik Olofsen wrote:
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
I suspected as much from the comments in the url you sent.
Seems silly, though. What happens if you just say "file://mim::info.txt" ?
(I must admit that I'm slightly confused on how many slashes are
appropriate...)
Johnny
Erik
On Tue, Jan 29, 2013 at 03:26:01PM +0100, Johnny Billquist wrote:
On 2013-01-29 14:53, Erik Olofsen wrote:
If we may use an url such as mim::something.html, which would normally be a
file:// there would be some basic functionality I think?
Right, since that is basically just using the file: transport/protocol.
The fact that files can be accessed transparently over DECnet makes it
possible to access documents "over DECnet".
Depending on how the parsing/handling of the url for something in the
file: domain is done, this might actually work straight away.
Johnny
Erik
On Tue, Jan 29, 2013 at 02:04:39PM +0100, Johnny Billquist wrote:
On 2013-01-29 13:44, Erik Olofsen wrote:
HECnetters,
Is anyone interested in using Lynx on HECnet?
Using node names in the url is not possible; some information is here:
http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html
On my Alpha with VMS 6.1, I'm able to compile Lynx version 2.3.
It seems that the latest version, 2.8.7, does not compile under VMS 8.3.
Perhaps I'm going to have a look at the old sources; perhaps I'm going
to do something more useful...
Well, the basic "problem" is that there is no http object defined in
DECnet, nor any equivalent to the http protocol, so how would you expect
it to work?
DECnet is not IP, nor TCP.
Johnny
On 2013-01-30 02:54, Steve Davidson wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Tuesday, January 29, 2013 13:47
To: hecnet at Update.UU.SE
Cc: Pete Edwards
Subject: Re: [HECnet] Returning to HECNET
On 2013-01-29 18:35, Pete Edwards wrote:
Ok maybe I need to re-phrase the question.
My ISP now only offers me a dynamic IP address.
My understanding is that Johnny's bridge program is not tolerant of
changing IP addresses. Is that still the case?
Correct.
So based on Sampsa's answer I can connect via a Multinet tunnel and
there's at least one Hecnet member (Steve Davidson) who can
keep that
connected even if the IP address changes?
Correct.
Would that mean I need to move into another area or request
an area to myself?
You need to move to Steve's area, or set one up of your own.
Johnny
Or move to Sampsa's area.
That would very much depend on where he connects, if he is an endnode...
Johnny
-Steve
Top-posting on top of a top-posted reply :) On 29 January
2013 00:30,
<sampsa at mac.com> wrote:
Well Steve Davidson has built a system for updating IP
addresses of MULTINET circuits - it seems to work pretty well.
sampsa
On 29 Jan 2013, at 02:29, Pete Edwards
<stimpy.u.idiot at gmail.com> wrote:
Hi All,
After a rather suddenly enforced break over 2 years ago I'm in a
position where I can try and get back onto HECNET.
I've renewed my VMS PAKs and have a couple of simh VMS
7.3 instances up again.
Unfortunately when I dropped off back then I lost my
static IP, so
step one, I guess, is asking this: What are the current
best options
the group has found to deal with dynamic addresses?
Alas FLETCH (1.100), my VS4000/60 has suffered some kind of disk
trauma during the intervening 2 house moves so it might
be a while
before I can connect a physical system.
Nice to see the return of the mapping project too - rather more
elegant than my own short-lived efforts.
Cheers,
Pete
--
Pete Edwards
"There's a man with a mullet going mad with a mallet in
Millets!" -
HMHB
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 30 Jan 2013, at 11:25, Mark Wickens wrote:
On 30/01/2013 05:45, Sampsa Laine wrote:
On 30 Jan 2013, at 06:23, Ian McLaughlin wrote:
Chimpy. Sorry for the autocorrect on your name below - just noticed :)
Oh cool, glad to know someone finds it useful.
sampsa
I probably mumbled at one time about setting up a gateway via the 'hecnet.eu' domain - alas I don't have the technical skills to do this, but there is a 24/7 VAX SIMH instance running behind that domain that could easily be used to run a gateway.
Regards, Mark.
The subdomain -> machine mapping would be cool, maybe some other MTA like PMDF (or whatever it's called) oculd handle it?
On 30/01/2013 05:45, Sampsa Laine wrote:
On 30 Jan 2013, at 06:23, Ian McLaughlin wrote:
Chimpy. Sorry for the autocorrect on your name below - just noticed :)
Oh cool, glad to know someone finds it useful.
sampsa
I probably mumbled at one time about setting up a gateway via the 'hecnet.eu' domain - alas I don't have the technical skills to do this, but there is a 24/7 VAX SIMH instance running behind that domain that could easily be used to run a gateway.
Regards, Mark.
On 30 Jan 2013, at 06:23, Ian McLaughlin wrote:
Chimpy. Sorry for the autocorrect on your name below - just noticed :)
Oh cool, glad to know someone finds it useful.
sampsa
Hi All,
I requested access to HECNET some moons ago. Due to family Business
and heavy Workload in my Day-Job I had to pause this project for a
while.
Now as things settled I am back with my SimH/Vax (running 24/7 on a
raspberry pi) and my Alpha (an Alphastation 255 I newly aquired).
There are Decstations in Storage too (these odd MIPS Boxes) - maybe
one of these could be connected too - provided there's DECNet Support
in Ultrix.
What I'm asking for are three Node-Numbers (I don't need a whole area
- NodeNames would be MINE, EMMA and JACK) and a bit of advice with
Multinet. I have only a Dynamic IP uplink and am absolutely
unexperienced with Multinet.
Best Regards,
Wolfgang
PS: This may be double posted. First submission was from a wrong email adress.
--
Ing. Wolfgang Eichberger
Homepage: www.eichberger.org - Blog: 5ewl.blogspot.com - Genealogy:
genealogie.eichberger.org
Ahnenforschung Dauersuche: A(E)ichberger, B(P)ruckmayr in Ober sterreich
Chimpy. Sorry for the autocorrect on your name below - just noticed :)
Ian
Sent from my iPad
On 2013-01-29, at 8:14 PM, sampsa at mac.com wrote:
On 30 Jan 2013, at 06:13, Ian McLaughlin <ian at platinum.net> wrote:
Samosa
I've used the gateway for a few tests and it worked for me. I am considering subscribing to HECnet and dectech through it.
Ian
Which gateway? CHIMPY or the other one?
sampsa
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=9E00749C6A9311E2A…
On 30 Jan 2013, at 06:13, Ian McLaughlin <ian at platinum.net> wrote:
Samosa
I've used the gateway for a few tests and it worked for me. I am considering subscribing to HECnet and dectech through it.
Ian
Which gateway? CHIMPY or the other one?
sampsa
Samosa
I've used the gateway for a few tests and it worked for me. I am considering subscribing to HECnet and dectech through it.
Ian
Sent from my iPad
On 2013-01-29, at 8:08 PM, sampsa at mac.com wrote:
Is anyone (aside from myself)* running a mail gateway between HECnet and the Internet at large?
I remember there being a plan to set up a domain and then set up subdomains for each node, but not sure what happened to that..
* CHIMPY gateways mail to and from the Internet, rather awkwardly though and not all providers like the slightly wacky addresses it produces.
To send, mail to: CHIMPY::smtp%"joe at example.com"
Your inbound address is <NODENAME>::<USERNAME>@chimpymail.com
Sampsa
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=C24402206A9211E2A…
