There is another use case for MOP downline load: VAXeln.
The ePascal build system on VMS produces VAXeln system images (*.SYS files)
that are available for download (either remote network boot from the VAXeln
systems, or via NCP TRIGGER on a VMS host).
I have such a setup available for testing. HECnet node PIRTVX is served from
node PIVAX0 in this way.
/Wilm
-----Original Message-----
From: Johnny Billquist <bqt(a)softjar.se>
Sent: Sunday, October 16, 2022 6:20 PM
To: hecnet(a)lists.dfupdate.se
Subject: [HECnet] Re: RPM (was: APL help needed)
On 2022-10-16 16:42, Paul Koning wrote:
> On Oct 15, 2022, at 9:06 PM, Johnny Billquist <bqt(a)softjar.se> wrote:
>
> On 2022-10-15 20:39, Paul Koning wrote:
>>> On Oct 15, 2022, at 10:32 AM, Dave McGuire <mcguire(a)neurotica.com>
wrote:
>>>
>>> ...
>>> LSSM has a big Itanium2 VMS machine that's our always-on HECnet node.
It also provides MOP services for our DECserver terminal servers, etc.
Because the transatlantic links can sometimes be a bit slow, and there are
several RSX-11M-PLUS systems between LSSM and my place, I maintain a local
copy of the RPM repository on that system, that I copy periodically from
MIM:: and all local instances of rpm are configured to point at that.
>> One of these days I hope to add MOP load/dump
to PyDECnet. For that
some network traces of how VMS loads a terminal server would
be helpful,
along with a copy of the image it uses.
>
> You can find most all images on MIM::DU:[5,54]*ENG*.SYS
>
> Also, if I remember right, the DELUA manual (or if it was the DEUNA one),
do
contain a lot about MOP, and you also have the free mopd which you can
find in the NetBSD distribution among other places.
Thanks. I have the MOP spec, of course (and since I wrote it I should
remember
it...) What I was looking for is a trace of what VMS does, since
reality doesn't always match the spec. That, and an understanding of what
loadable files look like, that's an implementation specific detail not give
in the DECNet specs.
Hmm. I see that I conflated MOP with microcode updates a bit when trying to
remember this.
Anyway, the mopd in NetBSD can boot both DECservers as well as actual VAXen
(I've done it *lots* of times). The DELUA manual gives a good start, and the
mopd code should give enough to get it all running in PyDECnet, I would
expect.
The actual file format of the system images for the DECservers that I have
is actually the same as the RSX task image format. But it is images without
a task header (if you dive into it, you'll understand).
.tin du:[5,54]pr0801ENG.SYS
TIN V1.8
Task name: DS2$WR Date: 10-DEC-90 Pri=0. Start=013000. EXTTSK=000000.
Label block revision: 0.
Task addresses - Low: 013000, W0 high: 177777, High: 177777 Load size:
00570200 Max size: 00570200 # of window blocks: 1.
Task flags (040100): -HD -CHK
Partition: SYSTEM Offset: 000000
System ID: RSX-11M.
.
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