31 May
2020
31 May
'20
5:41 p.m.
Yes, this do simplify things even more.
All you need to do is a one time install of whatever package you want.
Then maintenance of an RSX system is essentially just a question of "RPM
ALL". However, a possible additional complication is that if TCP/IP have
been updated, you will want to do a reboot. So you need to somehow
detect if that happened. I have some ideas on how you could check for
that after updating, so that it can all be a bit more automated, but for
a start, the simple "RPM ALL" is essentially doing almost all the work
for you.
Johnny
On 2020-05-31 17:05, Mark Matlock wrote:
Johnny,
This is a very interesting development!! As someone who is updating about 6 RSX
systems with your TCP/IP system on a roughly weekly basis this is of keen interest to me.
I like the idea of keeping the IPCONFIG separate from RPM since the network configuration
can be so customized especially with the HECnet over IP capabilities.
This is really a revolutionary way to handle RSX software installation and
maintenance!
Thanks,
Mark
--
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 May 31, 2020, at 9:54 AM, Johnny Billquist
<bqt at softjar.se> wrote:
Ok. Thanks for inspiring me.
I now also have TCP/IP as a package under RPM.
A couple of comments about it are in place:
1) It's *big* You'll need atleast about 25.000 free blocks to install or update.
So nothing for anyone with an RL02 as the system disk.
2) It will do the install/update, but it will not start TCP/IP. You will still need the
separate scripts for TCP/IP in LB:[1,2]STARTUP.CMD in order to start the whole thing. RPM
can only be used for the updating of the system.
3) Because of some issues, RPM will also not be able to automatically handle any updates
to your IP configuration as such. So after doing an update of TCP/IP, you might want to do
that by hand, which is done by running "LB:[IP]IPCONFIG UPD". If you are
downloading the distribution itself, things runs just like before.
4) Depending on your internet connection, updating this package might take a little
while. I have also observed some issues with some sneaky FTP proxy interfering with FTP
transfers from MIM. If you are getting errors and timeouts doing transfers over FTP, try
changing the source to be mim.update.uu.se:10021 instead.
Johnny
On 2020-05-31 10:04, R. Voorhorst wrote:
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:
--
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 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