Hey folks. Does anyone have images of the RSX-11M v4.8 RK06/RK07
kit? I have the RL kit, but I would like to have the RK06/RK07 kit.
I think Oleg may have it, but my mail server doesn't seem to be
talking to his mail server.
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hey folks, would anyone here happen to have the firmware files for
the Emulex Performance 2500 and Performance 4000 LAT terminal servers?
I really regret not having snagged a copy of that stuff when I
managed a bunch of those in the early 1990s. Wasn't thinking ahead I guess.
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
I’m trying to get mail working from my latest Linux DECnet release to OopenVMS with the intention of eventually upgrading to the mail11v3 protocol. I’m running an up to date version of VAX OpenVMS V7.3 with all patches I’ve found on a recent download of OpenSimh on a really slow ARM system. The system has a default DECnet account as well as a MAIL$SERVER account. Whenever I try to send e-mail, the connection is rejected with a “No such user” error:
Auditable event: Network login failure
Event time: 29-NOV-2023 10:14:32.96
PID: 00000098
Process name: MAIL_8198
Username: DECNET
Remote node id: 42186 (41.202)
Remote username: Linux0000
Status: %LOGIN-F-NOSUCHUSER, no such user
I also get the same rejection error if I try to connect to FAL with no access control information. However, if I connect to FAL using the explicit nonpriviledged userid/password returned by NCP, everything works as expected.
Any ideas?
Thanks,
John.
Version 5.3(248)-5 incorporates additional features, enhancements and
fixes since the minor release of 5.3(235)-5, in June of this year
(11-Jun-2023).These are as follows and can be identified in the code
with the edit number as the prefix of a comment.
[236] Implement /FORKLESS connections for DECnet NRT’s
[237] Implement the RETURN keyword to stop processing a TAKE file
[238] Enhanced NRT disconnect messages
[239] Use .HPTOD (High Precision Time of Day) if the monitor has it
HPTIM% .HPTOD
[240] When logging to a disk file, display the number of bytes written
[241] Handle potential case of incorrect data being sent for CWD
[242] ECHO /TRANSACTION /DEBUG /SESSION Switches
[243] Fix off by one error which appended NUL characters in packets
[244] Fix server FINISH does not close all logs
[245] Rewrite MOVSTU to use EXTEND instead of loop
[246] Additional C escape sequences: \O and \U
[247] Rewrite IAC handling to use EXTEND instead of loop
[248] Fix incorrect string lengths being returned by C constant
expansion
Kermit-20-Testing-Battery-5.3(248)-5 Updates and new Batch Tests
K20DPD: Updated Kermit-20 Packet Decoding Example
K20NRV: Updated Kermit-20 Server functions via Tops-20 DECnet NRT to
local host
K20NRT: Updated Kermit-20 Server functions via Tops-20 DECnet NRT to
remote host
K20DPD: Updated Kermit-20 Packet Decoding Example
K20P8R: New Regression test against Kermit-20 4.2(174) [2-May-85] 8
bit files with parity
K20RDC: New Communications comparison Kermit-20 4.2(174) [2-May-85]
and 5.3(248)-5
K1036N: Kermit-10 36 bit Regression Tests via DECnet NRT
Updated Help
It is available for anonymous NFT from VENTI2:: in the K20MIT
sub-directory. The full announcement may be find in text format in:
VENTI2::TOMMYT:<OINKY.K20MIT.DOCUMENTATION>KERMIT-20_V5_3(248)-5-ANNOUNCEMENT.TXT.
Note that the left and right parenthesis will need to be quoted with a
Control-V. Alternatively, you can just grab the whole documentation
directory and have your local NFT do the naming.
Sometime around mid-2022 the Linux kernel developers decided to remove the DECnet code from the Linux
kernel. Kernel 6.0.x was the last release which included source code for a DECnet implementation. More
recently, there has been some discussion around removing the code from the Long Term Support kernels.
These changes mean that the repository I have been maintaining at
<https://github.com/JohnForecast/RaspbianDECnet> can no longer be installed on recent releases.
Over the past year or so, I have been working on a replacement for this repository with the following
characteristics:
- Designed to be built as an external kernel module
This simplifies and speeds up the installation since we no longer need to rebuild the entire
kernel.
- Can only be built as an ethernet endnode
Again this substantially simplifies the kernel code. The routing code was alway marked as
“experimental” and I never tried to get it running. If you need a DECnet router, pyDECnet or
Route20 are much better solutions.
- Minimize the use of Linux kernel frameworks
Many of the problems with keeping RaspbianDECnet running between Linux versions
were changes to the kernel framework APIs. By limiting the use of these APIs I am hoping
that the kernel module will need fewer changes to keep up with kernel changes. So far,
I have had to make one additional conditional code change at kernel 6.5 and that was in
the socket layer so all networking code would need to be changed.
In addition to a new kernel module there have been a number of changes to the userland code:
- What used to be “fal2” is now the default file access listener. The old “fal” is still available in the
“fal-old” directory
- What used to be “nml2” is now the default and only network management listener.
- There is now a subset implementation of “ncp” which is sufficient to support all of the requests
available from the Linux network management listener. It does implement a “tell” prefix so all
of these commands may be issued to remote systems. In addition, it implements
“ncp copy known nodes from <node name/address>” to update the local node name database.
- The new kernel module now supports node counters as defined in the Network Management
Specification and the ncp/nml combination are able to display and zero them.
- The installation procedure is no longer targeted solely at Raspberry Pi releases. The current
procedure supports installation on systems derived from Debian or Fedora although only a
limited number of distributions have been tested (see README.DECnet).
This new release is available at:
<https://github.com/JohnForecast/LinuxDECnet>
and should be considered to be in Beta test at this time. See README.DECnet in the top level directory
for more information and installation instructions.
Hey folks. I've gotten a Pro380 running at LSSM, and have just
gotten a DECNA board installed. Can anyone point me to any docs for
Pro/DECnet? I don't see much online. I'd like to get it talking to the
rest of the DECnet machines at the museum and on HECnet. And, ideally,
LAT if possible.
Thanks,
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
I've seen/heard of various stories about how people update their
nodename databases on their machines, hacking together scripts, and
processing files. So I figured I should write a small mail about the
topic (I should create a web-page with this information as well).
The main/basic point is that people are creating work for themselves
they really don't need.
Exactly how you update your nodename database on your machine depends on
what OS you are running, but there are basically prepared tools and
scripts already existing for pretty much any scenario. And if you happen
to have a system or need not currently covered, I can easily create one
for you as well.
But before going into the solutions, let me explain a bit about the
source of the data here.
DECnet phase IV do not have a centralized nodename system like DNS. Each
node in the DECnet network has its own nodename database, and every
machine can have its own name for another machine, independent of what
that other machine thinks its own nodename is.
However, in order to make it easier for multiple people and machines to
talk, it helps if everyone have a somewhat similar database. And here is
where the nodename database in MIM comes it. The nodename database that
I have on MIM is not the regular DECnet nodename database. Instead I'm
using DATATRIEVE to maintain a nodename database, which contains more
information than just the number and name. It contains the owner,
information about the software and hardware of the node, the location,
and when things were updated. This database is what is queried when
someone goes to http://mim.stupi.net/nodedb . And that page is generated
by just making queries in DATATRIEVE. If someone have a host with
DATATRIEVE on it, it is even possible to remotely access this DATATRIEVE
database over DECnet (you'll only have read-only access).
I have been considering possibly adding a web interface for people to
possibly be able to update their own information remotely, but so far
that's been a low priority thing. Maybe one day...
From this DATATRIEVE database I can then generate the DECnet nodename
database on MIM. This is a simple makefile actually. Whenever I run it,
it will create a bunch of different files (I'll get to that in a
moment), and detect if any changes have happened on the DECnet level of
things. If so, it will send a mail to people who have requested it,
informing them that the nodename database have been updated, and they
should update the nodename database of their own machines.
I hope this makes it apparent that creating various files based on the
nodename database is actually very simple. This is in a sense what
DATATRIEVE is good at. Creating reports is sortof what all these output
files are.
So - what files do I create today? Well, here is a short list:
FIX.CMD - This is a script file suitable for RSX systems using CFE.
However, it's sortof specially tailored for MIM, so it's not a file I
would recommend anyone else to use.
FIX.COM - This is a script for VMS systems using phase IV.
FIX.PHV - This is a script for VMS systems using phase V.
FIX.IMP - This is a script for VMS for anyone using DECdns.
FIX.T20 - This is a script for TOPS-20.
HECNET.PY - This is a definition file for PyDECnet.
FIX.RST - This is a script for RSTS/E.
NODENAMES.DAT - This is basically just the basic information is a simple
output form from DATATRIEVE. It exist mostly for historical reasons, but
I understand that lots of people actually take this file, and then write
code to process, extract and apply information from this file.
In addition, some systems can directly import nodenames from another
machine on DECnet, meaning you do not have to fetch and run any scripts
at all.
So here is the actioins you need to do on each system in a summarized form:
RSX:
In RSX, there is a tool called NNC which copies definitions from another
node. Copy over MIM::HECNET:NNC.BAT which is a batch file you can use
which does all the work of importing the latest definitions from MIM and
updating your local system. All you need to do is just "SUBMIT NNC.BAT"
and you are done.
VMS:
With phase IV, the node copy capability is build into NCP. All you need
to do is: "NCP COPY KNOWN NODES FROM MIM TO BOTH" and you are done.
With phase V, copy over FIX.PHV and run it, or just directly run it from
MIM like this: "@MIM::HECNET:FIX.PHV"
If you run DECdns, grab FIX.IMP, and run it with whatever tool is used
to manage this (sorry that I can't help more, I don't really have any
experience with DECdns).
TOPS-20:
Grab MIM::HECNET:FIX.T20 and run in in the NCP submode of OPR (if I
remember the setup correctly).
RSTS/E:
Grab MIM::HECNET:FIX.RST, and run it with "@FIX.RST".
PyDECnet:
Fetch hecnet.py by doing "wget mim.stupi.net/hecnet.py". Place that
where you have configured PyDECnet to get the nodenames from, and you
are good (not sure if you need to restart PyDECnet).
Now. If you have some other system with some specific format you need,
just let me know, and I'll create such a file as well. It's trivial for
me to do this from DATATRIEVE. If you spot something wrong/bad in some
file created today, let me know, and we'll fix it. If you see any errors
or omissions in the information in this mail, let me know, and I'll get
it corrected. I will create a web page with this information as well.
If you want to get a mail whenever the nodename database is updated,
just let me know and I'll add you to the list.
And HECnet is slowly growing. Occasionally a completely new person/site
gets connected. Occasionally people add more nodes. The online presence
seems pretty constant. At the moment 19 areas are online. In area 1,
currently there are 19 machines online. Looking at Paul's HECnet map
(http://akdesign.dyndns.org:8080/map), there are machines online in
quite different locations, covering a large part of the world. I find
this cool, and even though there isn't a lot being done, it's still fun.
Well. Have a nice weekend everyone, and I hope some people find this
information useful.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Hi Everyone,
To everyone that has a GRE tunnel to A12RTR, the IP address has changed!
It is now 103.46.213.236, alternatively you can also use either of the
following names:
* tim.sneddon.id.au
* cmkrnl.io
There has been some disruption to my IPv6 config too, but I am
investigating that.
Regards, Tim.
I just found out about this from Terry Kennedy.
A MOP server for RSTS/E, free to use:
https://www.glaver.org/ftp/tmk-software/mop-server/
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
We could definitely make use of that! Can you spare it?
-Dave
On 9/2/23 06:38, Peter Lothberg wrote:
> Dave,
>
> Maybe you need a KS10 repair tool?
>
>
> -P
> ----- Original Message -----
> > From: "Dave McGuire" <mcguire(a)neurotica.com>
> > To: "The Hobbyist DECnet mailing list" <hecnet(a)lists.dfupdate.se>
> > Sent: Monday, August 21, 2023 6:09:58 PM
> > Subject: [HECnet] Re: pssst...
>
> > Hahaaaa, thank you Fred! You really need to come back for a visit,
> > it has been a while. The guys and I have been very busy; we have a lot
> > more hardware up and running now.
> >
> > -Dave
> >
> > --
> > Dave McGuire, AK4HZ
> > New Kensington, PA
> >
> > _______________________________________________
> > HECnet mailing list -- hecnet(a)lists.dfupdate.se
> > To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
>
> _______________________________________________
> HECnet mailing list -- hecnet(a)lists.dfupdate.se
> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
--
Dave McGuire, AK4HZ
New Kensington, PA
