For all those who have tunnels to my Cisco 1841, I have switched ISPs and
as such my static IP address has changed. In my configuration I have the
following endpoints configured:
David Moylan (Area 35)
Tomas Prybil (Area 34)
Supratim Sanyal (Area 31)
Brian Hechinger (Area 52)
Ian McLaughlin (Area 42)
Cory Smelosky (Area 9)
Dave McGuire (Area 61)
Peter Lothberg (Area 59)
Mark Darvill (Area 22)
Mark G Thomas (Area 23)
If you are on that list could you please update your tunnel to use my new
address, which is 163.47.57.118.
Mark Berryman, my IPv6 address is unchanged, for the moment.
Regards, Tim.
As some of you may have just heard, LCM+L are suspending operations "for now" due to the effects of the current crisis. We'll discover what'll be happening to online access to their systems shortly. It's a sad day but hopefully not permanently so.
Keith
Good afternoon everyone,
What are you guys doing to get something like OPC$CRASH invoked when a UPS signals it is on battery?
I have serial connectivity to TTAx ports on a Microvax 3100-80 running OVMS 7.3. Recommendations on a UPS?
Generally how do you get a VAX to shut down immediately on UPS going on battery?
Thanks in advance
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
Nice functionality to arrive so easily at a well-kept updated environment!
Big question now obviously appearing: will TCP/IP follow suit or is that not so suitable concerning the host machine?
Thanks,
Reindert
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Sunday, 31 May, 2020 02:24
To: Mark Matlock <mark at matlockfamily.com>; hecnet at update.uu.se
Cc: Info-PDP11 at dbit.com; SIMH <simh at trailing-edge.com>; [PiDP-11] <pidp-11 at googlegroups.com>
Subject: Re: [PiDP-11] Re: [HECnet] Announcing RPM, a software packet manager for RSX-11M-PLUS
On 2020-05-30 22:04, Mark Matlock wrote:
>
>> On May 30, 2020, at 10:38 AM, Johnny Billquist <bqt at softjar.se> wrote:
>>
>> Since I'm on a roll today, I figure I should announce the availability of a new tool for RSX, which I think most hobbyists will find rather useful.
>>
>> RPM is a packet manager for RSX (it has nothing to do with the Red Hat Packet Manager, except the name).
>
> Johnny,
> I love not only the new RPM software repository tool but also all the updated software tools. A few of the software packages that RPM listed were even new to me!
You're welcome. And have have *lots* of more software. It will just take a lot of time to work through it all and create packages for it.
> Also, I was behind in getting the latest versions of your NEMA, MKE and several others. This will make it very easy to stay current.
Similar problem to my own... What version did I now have on that machine? Did I do any updates since I last installed there? What software do I actually have? And where is it...?
> Thanks for this and also thanks for the latest version of your TCP/IP system.
Happy to provide it. And it looks like it has already seen some action, based on the ftp logs at MIM... :-)
Johnny
--
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
Since I'm on a roll today, I figure I should announce the availability
of a new tool for RSX, which I think most hobbyists will find rather useful.
RPM is a packet manager for RSX (it has nothing to do with the Red Hat
Packet Manager, except the name).
Over the years, I have found it becoming an ever growing hassle to
manually download, build and install all the different tools that I am
used to have on different systems. Not to mention the headaches when
trying to help others and providing software for them as well.
RPM is an attempt at automating this, and making more software available
for all people with a small effort. I hope it will also help in getting
more people on to the actual latest version of various tools.
Historically, much software like this was distributed through DECUS, and
the various symposium tapes tried to distribute updates, but it was a
very fragmented world, where parallel development often happened, based
on different versions. RPM will now allow people to see what is the
actual latest version around, and if they want to work on something,
they can do that based on this.
RPM is by no means perfect, and in fact are missing a whole bunch of
things, but it is now at a stage where it is actually usable and useful,
so therefore I'm doing this announcement now.
RPM is essentially a tool to track what software is available and what
software is installed. It can install and remove software, and it can
update it to new versions when new versions become available.
It can also be involved as a part of the boot process to automatically
install any tasks that are part of installed packages.
It can fetch information both over DECnet and TCP/IP, and is written in
IND, and uses cleartext configuration and status files, and packages are
universal libraries.
Feel free to contact me about any issues, problems, wishes, or whatever.
I can't guarantee that anything gets down, but there is always a bigger
chance if I know about it. The software is also freely available, and
contributions from others are also very welcome.
So, with that presentation done, here are the practical details:
To use RPM, you need to fetch one file to your machine:
RPM.PKG.
It can be found at:
HECnet: MIM::LB:[RPM]RPM.PKG
Inetnet: ftp://rpm at mim.update.uu.se/rpm.pkg
Once you have downloaded that file, you need to extract two files, using
the following commands:
LBR RPM=RPM.PKG/EX:RPM
LBR CONFIG=RPM.PKG/EX:CONFIG
After that, edit CONFIG.CMD using your favorite editor. The file should
contain enough explanation and examples for what you need to setup.
After you've done that editing, give the command:
@RPM FETCH
this will setup the list of what packages are available.
After that, you can do
@RPM LIST
to show what packages there are.
It's not necessary, but I would recommend the next thing is:
@RPM INSTALL RPM
this moves the RPM package manager itself under control of RPM, so that
you automatically get new improvements installed when they are available.
Of course, you can then download packages (@RPM FETCH pkg), get
information about packages (@RPM INFO pkg), install packages (@RPM
INSTALL pkg), or just update them (@RPM UPDATE pkg).
However, apart from the INSTALL option, to just install those packages
you really would like to have, the most used option will probably be
"ALL", which does a fetch of the latest package list, and then updates
any packages that should be updated. You could in fact just place that
in a batch file to be run once in a while, and have your software
updated all the time without having to think about it.
Or else, just once in a while do a
@RPM FETCH
@RPM LIST
to see which packages have new updates available, and then you can just
update the ones you want to.
Finally, it is possible to run without giving any option/command at all,
in which case RPM goes into interactive mode, with a menu showing what
you can do.
It is also possible to run from the command line with multiple commands.
Each command should be separated from the others using "+" in that case.
For example:
@RPM FETCH+LIST
As for what packages are available - I have started making some
available that I have been using and working on for many years. I have
plenty more software that I will make available. If anyone else have
software they would like to make available, I can provide some quick
information on how you create your own packages as well, and I can also
host packages from other people at Mim.
Also, for the time being, I have mostly focused on binary packages with
executables. I can certainly see that eventually I would also do
packages for the sources of things. It's mostly a case of priorities.
Even though creating a package is now a fairly easy task, it do grow
with the number of files and stuff you want to put in there. If anyone
wants sources for some specific software for which I have made a
package, the sources are also on Mim, and are usually readable by
anyone. Ask me if you have any questions, and for the most part, all of
the software is freely available in sources as well.
Also, the binaries are built for RSX-11M-PLUS. While some might work on
11M as well, I have not tried this, nor am I going to try and handle it.
There could also be an issue with some software if installed on older
versions of RSX-11M-PLUS (before V4.0). I would think it should mostly
work, but will not make any guarantees about that either. (If anyone
really is running such old versions, they should update to a newer
version of RSX instead).
Johnny
--
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
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
Highlights:
. Improvements to TCP performance.
. Bugfixes and improvements for DNS/mDNS.
. RSX security improvement.
Detailed information on things that have been done since the last release:
TCP:
. Bugfix in longword arithmetic condition code setup. This affected
performance and stability of TCP communication.
. Improved TCP retransmit logic. TCP now better handles when
retransmitting, and getting an acknowledge of parts of the data.
previously, this could lead to very long retransmit times.
DNS/mDNS:
. Bugfix in DNS resolver. Possible stack corruption in some situation.
. Added MDNS as a separate resolver type.
. Bugfix in resolver. mDNS reverse lookups were not responded to.
. Bugfix in resolver. Resolver could fail to join multicast group at
startup.
. Improved DNS timeout handling. If trying to resolve an ambiguous name
only do local lookup if global lookup fails.
FTP:
. Bugfix in FTP. If user failed to log in, FTP client got out of sync
with server.
. Improve FTP client. Exit with status reflecting state in FTP session.
MAILD:
. Added a possibility to have an SMTP relay for all outgoing mail.
Installation:
. Improved installation process, and added IP configuration for mDNS and
UTC offset for NTP.
RSX:
. Bugfix in RSX. INS did not properly set uic if /UIC was given.
Some additional notes:
As usual, I would recommend people to update as soon as possible.
The changes are not critical, but will lead to a much better experience.
For the RSX fixes to be applied, it is necessary to answer yes to the
question about installing RSX patches. Otherwise those fixes will not
be installed. This does not lead to any failures, but it might lead to
some components running exactly the way you might be expecting (such as
daemons running under the wrong user).
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
(As an additional note, I have become aware of that there is some device
proxying access to the ftp service at Mim. This might lead to failure to
transfer large files. If you observe such problems, try connecting to
Mim at port 10021 instead, which is an alternative port for the ftp
server, and which circumvents the proxy.)
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
I hope people find this update useful.
Johnny
--
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
hi
hecnet-list
here it is, make ranks drop instantly
http://www.mgdots.co/detail.php?id=66
Checkout the pricelist attached
NEW: Option to delete domain
Regards
Mindi Abbe ?
Unsubscribe option is available on the footer of our website
Dear all,
Following the announcement of the VSI "community licence" program, and
the fact that VAX software will *not* be licensed by VSI, I have
downgraded my VAXcluster to V4.6
I even implemented Adventure (both the "350" and the "551" version).
Check my article on LinkedIn
https://www.linkedin.com/pulse/almost-back-future-wilm-boerhout/
I will be taking requests for guest accounts on VAX046. You *will* be
**in a twisty maze of little passages.
*Wilm*