search

PDP-10 / its

Incompatible Timesharing System
Other
834 stars 80 forks source link

Add support for XGP user in INQUIR database. #2287

Closed eswenson1 closed 3 months ago

eswenson1 commented 4 months ago

This PR changes the way that the INQUIR database is installed into ITS. Previously, we included a binary INQUIR;LSR 1 database on the tape we load. Now, we build the INQUPD program (and INQUIR;DIRS BIN) database, which is required by INQUPD, when run in LSRINI mode. LSRINI mode, invoked by a JNAME of LSRINI for INQUPD, generates an empty .TEMP.;LSR1 EMPTY database for INQUIR. The build scripts generate this empty database and copy it to the appropriate plact (INQUIR;LSR 1).

Then, the INQUPD program is run in "normal" mode, such that it processes files in the INQUIR directory with FN1 = .UPD1., and we provide such a file with the XGP user defined. We can, of course add other users that we wish to be "pre-loaded" in the INQUIR database.

eswenson1 commented 4 months ago

@larsbrinkhoff I fully realize that adding an INQUIR entry for XGP (which you asked for) does NOT prevent GUNNER from gunning the XGP session. But I thought the current "binary-based" approach for creating the INQUIR database was hacky, given that we have a means of generating an empty one with INQUPD and given that we may wish to have an easy way to add more INQUIR entries (by editing the INQUPD script in future commits).

larsbrinkhoff commented 3 months ago

Right, I understand the GUNNER problem is something else. This is still a great enhancement. E.g. XGP can log in and automatically run the .XGPR.; XGP LOGIN script.

I updated the XGP information per a real LSR1 1 file. I will make a separate pull request to add various system users.

larsbrinkhoff commented 3 months ago

Verified that logging in as XGP runs .XGPR.;XGP LOGIN.