[its-hackers] sys; atsign dragon
eric at swenson.org
Thu Nov 17 08:24:50 CET 2016
I suspect, even if KLH10 cannot boot directly from disk, as long as DDT/DSKDMP are loaded, you can load whatever ITS is stored in the FE file system, so we should be able to update the “its rp06” that you are currently storing in the FE file system and load/run that, right? I’m not altogether sure, and perhaps Ken can comment here, why the way KLH10 users boot ITS systems (they way it is documented) is to load an @.its-647es-u like image from the host file system rather than loading an ITS image from the ITS disk. This requires exporting a new ITS image from ITS to the host, running a conversion tool on it, and then updating a KLH10 INI file with the new ITS image. I’d just as soon just boot with DDT/NSALV and type “its<CR>$g” to start its (that way, if you have multiple ITS images in the “.;” directory, e.g. NITS, you can choose which one to boot.
> On Nov 16, 2016, at 23:18, Lars Brinkhoff <lars at nocrew.org> wrote:
> Eric Swenson wrote:
>> Ken Harrenstien wrote:
>> You're loading ITS into memory from the host filesystem, not from
>> the emulated ITS filesystem.
>> That’s what I thought.
> I should explain that so far, no rebuilt files are used to boot the
> system. I.e. ITS, EDDT, and NSALV are built, but they are not dumped
> into a new bootable ITS yet. It's on my todo list.
>> Are there step-by-step instructions for using KLH10 and starting with
>> NO disk, to create an ITS disk with the minimum file system required
>> for boot? I’ve only seen steps that start from a PI/MD file system —
>> never a MINSYS tape.
> As far as I know, KLH10 can't boot from tape (or disk). That may be why
> there are no such instructions. However, I emulate the KSHACK; BUILD
> DOC steps by loading NSALV and DSKDMP from the host file system and
> proceed from there.
More information about the its-hackers