Allison <ajp166 at bellatlantic.net> skrev:
Did I hear someone say "RSX"? :-)
HALP!
I just decided to attack a micro-11 system I had not attendded to.
Good news is it's pristine and complete:
BA23, 11/23BH, 512k (M8057), DEQNA, RQDX2(late firmware).
The RD52 has RXS11 and boots.
It's been a long time since I used RSX and longer since
I've administered it. So some procedures for doing things
I need to know or a pointer to.
TO shut down I do?
"RUN SHUTUP" usually does it, since by default SHUTUP is installed in the
system.
If it isn't, "RUN $SHUTUP" will do the same deal.
As others mentioned, LB:[1,2]SHUTUP.CMD is invoked as a part of the shutup
procedure, and shouldn't be invoked by hand.
TO change admin password how, and which account again?
"RUN ACNT" if ACNT is installed. Otherwise "RUN $ACNT" will do it.
The "SET PASSWORD" command is something that only exists in RSX-11M-PLUS, but if
so, then it works just as fine from MCR as from DCL by default.
ACNT is the general account management program. From a privileged terminal, you
can change any account. In 11M, you can only change your own password with ACNT.
In 11M-PLUS, ACNT is not usable by non-prived terminals.
And there isn't any explicit admin account in RSX. The closest would be [1,54],
if it exists. It does by default, which is why I mention it. But there are no
problems with just deleting that account if you want to.
Any account with a group number <= 10 is a privileged account. What this means
is that when logged in, the terminal will have the PRIV bit set. Other users
will have it cleared. Most things go on the terminal info bit when checking for
privs.
Run ACNT, and you can list all accounts, and see which exists with privs.
If I add a 8line mux (DHV or DZV) what the procedure
to get
system to install and recognise it.
Phew, big question. In short, you have two ways:
1) Do a full sysgen, which includes all the devices you want, and you'll have
it. This will take a couple of hours, and literally hundreds of questions. A
manual is almost neccesary.
2) Just build the device driver and load it. This requires that your system have
been generated with loadable device drivers. You still need to figure out how to
build the device driver. There are commands scripts that do these things, but
they expect to be called as a part of SYSGEN, so doing it by hand will require
some hands on fiddling.
If you want a device driver to be abailable each time you boot, you need to add
it to the system image you're booting. That is done by VMR. VMR is done as a
part of SYSGEN as well, but if you build stuff yourself, you'll have to either
add them in VMR as well, or load them at boot time in the startup script.
On line DOCs to refresh memory from?
I think I saw that SRI now have some RSX manuals online, and of course, we also
have bitsavers.
There is a whole manual just on the SYSGEN process. Read it. :-)
I'm most comfortable with VMS, Ultrix and RT-11
but never
bothered with RSX for a home system.
VMS knowledge can be of some help, but not much of anything else.
RSX is so much fun. Welcome to the asylum. :-)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol