Well from this link
http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html
it doesn't seem to be straightforward...
Erik
On Tue, Jan 29, 2013 at 04:45:18PM +0200, sampsa at mac.com wrote:
I wonder how hard that would be to change?
sampsa
On 29 Jan 2013, at 16:29, Erik Olofsen <e.olofsen at xs4all.nl> wrote:
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
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
I wonder how hard that would be to change?
sampsa
On 29 Jan 2013, at 16:29, Erik Olofsen <e.olofsen at xs4all.nl> wrote:
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
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
Johnny Billquist <bqt at softjar.se> writes:
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.
There are web servers for VMS and I believe you have one running on RSX.
The problem is not one of http but shipping that http over DECnet. Get
the browser and web server speaking DECnet and you're 99% of the way to
the goal.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
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-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
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?
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-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
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...
Erik
Mike,
Area 39 is available. If you decide to use Multinet Tunnels then configure it to connect to 69.21.253.158 and send me mail with your IP address. If it is a dynamic IP address then I will need to know the domain as well.
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Michael Holmes
Sent: Mon 1/28/2013 18:42
To: hecnet at Update.UU.SE
Subject: [HECnet] New HECnet Area Request
Hi all,
My alphaserver 800 finally arrived and I'm setting it up now and would like to request a HECNET area so I experiment with connecting to HECNET.
I saw a previous message listing available areas and I'd like to request area 39 if its not already spoken for.
I finally found a SCSI drive that will work in it and am currently installing VMS 8.3 and DECNET IV on it right now.
Hopefully will have it finished tonight and be able work on the HECNET options (router, etc) through the week and weekend.
I also have a DEC 3000L and a multia that I'll try to bring back to life sometime later.
Thanks
Mike
Alexandria, VA
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
