26 Jul
2025
26 Jul
'25
11:37 a.m.
No. If it works now, it will continue to work.
Johnny
On 2025-07-26 11:24, Rob Jarratt wrote:
I still reference hecnet-1-1023.stupi.net, but should
I change to something
else to access the bridge?
Regards
Rob
--
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
-----Original Message-----
From: Johnny Billquist <bqt(a)softjar.se>
Sent: 25 July 2025 17:35
To: 'The Hobbyist DECnet mailing list' <hecnet(a)lists.dfupdate.se>se>;
[PiDP-11]
<pidp-11(a)googlegroups.com>om>; simh(a)groups.io;
Info-PDP11(a)dbit.com
Subject: [HECnet] MIM move...
As some people have noticed the last few months, MIM have been difficult
to
reach.
It has come to the point where I just have to move the machine to a new
place, as I'm not having much success solving the current situation.
For people who maybe don't know, Mim is a PDP-11/74 (simulated) which
runs RSX-11M+. It is kindof a hub for Hecnet, as well as a resource for
anyone
who wants to find documentation or information
about RSX, and also to find
various software for RSX.
I will move Mim this weekend, and so it will be down for a while.
Hopefully this will be a fairly smooth operation, but I'll let people know
when
it's going on, and my expectation is that it
shouldn't be more than a
couple of
hours.
Mim will also change address and name because of this. The new address to
reach Mim on will be Mim.SoftJAR.SE. This name should be stable for the
forseeable future. Physically Mim will move from Sweden to the US east
cost,
and be living at LSSM. A big thank you to LSSM
and Dave McGuire in
particular for helping out with resources for this.
In practice, for everyone else, once the move is done, it means that:
. Any reference to Mim.Stupi.NET needs to be changed to Mim.SoftJAR.SE.
. Any multinet circuits connecting to Mim should adjust their costs. See
the
HECnet information page on Mim about this.
. I will also create a new PyDECnet node at LSSM to act as another
connection
point for people who might not be able to connect
to hecnet-1-
1023.stupi.net, but which are still in area 1.
. hecnet-1-1023.stupi.net will still be around, and will still be possible
to
use.
This do mean that area 1 will be more geographically spread out. Not
ideal, but I'm not expecting this to cause any major issues. Performance
for some might get a bit better or worse, depending on various aspects
and conditions. But in general, if people just keep costs aligned with
recommendations, things should work well.
Best regards,
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
_______________________________________________
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