PDP-10
Machine name
Every now and the I stumble upon a place which hardcodes the ITS machine names. Those places should be recorded.
This is a great idea. Eventually we should centralize.
-- Eric
On Jan 18, 2017, at 13:13, Lars Brinkhoff [email protected] wrote:
SYSEN2; MAGFRM 17, label MCHNTB.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
SYSEN1; PWORD >, labels bltspc, mchtab, and nodflt.
SYSEN1; DDT >, labels KEXIST and mchtab.
SYSEN1; SENDER >, labels Create and SC4.
SYSEN2; FRETTY >, label GO.
SYSEN2; FIND >, label ITSTBL.
SYSEN2; DIRED >, label ACT2.
SYSENG; DIRDEV >, label OPEN10.
SYSENG; DEMAIL >, label Begin.
SYSNET; TELSER >, label CHTELE. <--- This one is especially funny!
SYSNET; SENDS >, label gotusr.
SYSEN1; NETIME >, label hosts.
INQUIR; INQUPD >, label NEWMAC.
SYSENG; RAYGUN >, label MCHNTB.
SYSENG; MODEMS >, label mchtab.
SYSENG; @DEV >, label machtb.
BAWDEN; 11LOAD >, label ackrfc.
SYSNET; COMSAT >, labels: bughst, domgat, and tcpgat. Currently, binary is patched rather than source modified.
SYSENG; DUMP >, macro MCOND.
SYSEN2; FUMP >, macro MCOND.
SYSTEM; CONFIG >, macro MCOND.
SYSTEM; TTYTYP >, macro MCONDX.
SYSTEM; IOELEV >, macro MCONDX.
SYSTEM; ITS >, macro MCOND.
SYSENG; LUSER >, macro MACTAB, label ITSTAB.
SYSTEM; SALV >, symbol MCHN.
KSHACK; NSALV >, symbol MCHN.
From @bictorv's http://its.victor.se/wiki/rename:
SYSEN2; MLDEV >, many places after symbol GO.
L; *LISP >, symbol UDIRSET.
L; STRUCT >, MRA [ITS ...
SYSEN2; CFTP >, symbol SavDev.
SYSEN2; NAME >, symbol hsits.
SYSEN2; INSTAL >, symbol ITS.
;;; INSUFFERABLE DEVICE NAME DISTINGUISHER
L; QIO >, symbol IDNTB. Read it and weep!
DECSYS; DECUUO >, symbol strtab.
INQUIR; DMUNCH >, the whole penultimate page.
SYSEN3; WHOJ >, symbol DEVTAB.
DB hasn't been added to a lot of those places, so it doesn't seem crucial.
We need a name for a KA10 configured to run in simulator. I'm thinking "KA".
SYSTEM; TTYTYP > needs to have three semicolons, space, and the system name. NAME looks for that string. Terminal entries must be marked with ;Tnn.
Minimal set of files to change to add a new name:
- SYSTEM; CONFIG
- SYSTEM; TTYTYP
- L; *LISP
- SYSEN1; PWORD
- SYSHST; H3TEXT
- SYSTEM; SALV or KSHACK; NSALV
- SYSENG; DUMP (KA10 and KL10: set NEWCOD==0)
This is a guess based on adding KA. Maybe @ams can check if he wants to allocate a name?
@hrlzm, see information in this issue about the ordeal to add a new ITS.
Yes. Doesn't this work?
https://github.com/PDP-10/its/blob/master/build/build.tcl#L456
@ams HOSTS3 is used to generate the binary host table form H3TEXT >. You asked about generating the H3TEXT file. Is that what you meant, or did you mean converting the text file to binary?
TJ6:
https://github.com/PDP-10/its/blob/master/src/tj6/tj6.29#L3803-L3808
https://github.com/PDP-10/its/blob/master/src/tj6/tj6.29#L4400-L4402
I think we found most places by now. Maybe we should add DB and KA to all those places.
DDT, label KVERS1. If you happen to have an LDS-1 attached, do what DM does.
Muddle's REOPN (in FOPEN) knows about AI:, ML: and DM: as network filesystems.
Isn't it better to hack all those programs to use .GETSYS on ITSNMS to find out, like e.g. NAME and INSTAL already do?
Even if you would still need to have an MCOND in CONFIG and an MCONDX in TTYTYP, it would be much easier than editing all these places, right? And the ITSIRP in CONFIG (which defines ITSNMS) could be auto-generated, using DNS + the current name.
(I agree that H3TEXT should be generated, using https://github.com/Chaosnet/config-files-from-dns.)
Isn't it better to hack all those programs
Quite possibly so. Although there probably some devils lurking in the details.
If someone finds this a fun activity, contributions are welcome. For now, this repository receives a rather minimal amount of maintenance to have it running at a "good enough" level. Occasionally things are added as they trickle out of MIT's archives.