On Aug 7, 2022, at 5:46 PM, Johnny Billquist
<bqt(a)softjar.se> wrote:
On 2022-08-07 17:04, John Forecast wrote:
On Aug 7,
2022, at 10:47 AM, Paul Koning <paulkoning(a)comcast.net> wrote:
According to my remote-terminal.txt document, there's another type code not shown in
your table, 18 for Ultrix-32. It wouldn't surprise me if Linux borrowed that code.
The original Linux DECnet code tries to pretend that it’s VMS, so it uses code 7.
When I started to clean up the code (I just noticed that Cterm still uses code 7 when the
client accepts the bind request), I changed FAL to use one of the user-specified values
(192 I think). Most everything works OK except TOPS-10 refuses to connect and I had to
special case returning the Ultrix-32 code.
The funny/weird thing is that mostly the same list of OSes are used by multiple
protocols, but the list is not always identical.
And with CTERM I don't think it really matters. But for NRT it does.
And with FAL, at least RSX can even tell what the remote side is. Nothing breaks for
unknown system types, but it's nice to see.
.ncp tell fedach sho exec
Node summary as of 7-AUG-22 23:45:36
Executor node = 31.13 (FEDACH)
Circuit = eth1, State = On
Identification = DECnet for Linux V3.13.0-170-generic on i686
.nft fedach::/id
NFT -- Version V9.0
Local NFARs V8 DAP V7.1 Buffer size= 2064. OS=RSX-11M+ FS=FCS-11 DC=Yes
Remote FAL V5 DAP V7.2 Buffer size= 65535. OS=VAX/VMS FS=RMS-32 DC=No
I guess somewhat old DECnet/Linux there...
That’s still the default. I wrote an alternative FAL which responds with the
user-specified code and doesn’t try to
emulate any RMS features (indexed files etc). Unfortunately, it only implements DAP
5.6.0 since that’s the latest
version of the spec I could find.