From: szabo_p@maths.su.oz.au (Paul Szabo) Newsgroups: comp.sys.apollo Subject: FAQ: install from tape (updated 12 Feb 96) Date: 8 Jul 1996 21:40:55 GMT Organization: Mathematics, University of Sydney Message-ID: <4rrv97$bip@metro.usyd.edu.au> Reply-To: szabo_p@maths.su.oz.au (Paul Szabo) The question of how to install Domain/OS from tape has come up several times lately. The following may help. (Use at your own risk, but please let me know if you find problems with any of this.) Paul Szabo - System Manager // School of Mathematics and Statistics szabo_p@maths.su.oz.au // University of Sydney, NSW 2006, Australia ----- How to install Domain/OS from tape (plagiarized from several comp.sys.apollo articles) (0) Find a copy of "Installing Domain Software" (current Apollo part number 008860-A03, older ones are 008860-A0n). They were shipped with every system, all the info will be in there. If you cannot find it, read on. (1) Put the machine in SERVICE mode (toggle switch on the back in the down position) and power up. See the MD (Mnemonic Debugger) prompt '>' showing; if not hit [RETURN] a few times. (2) Hit [RETURN] several times (first '>' prompt after reset may not work), then type 'DI C' to boot from cartridge. Insert the boot tape (with a legend something like CRTG_STD_SFW_BOOT) in the cartridge drive. (3) You may want to run 'EX CONFIG' (on DN[345]xxx machines that have it) to set correct configuration (memory, disk types) data, and also 'EX CALENDAR' to set correct date (answer 'N' even though you have a disk). You may want to run 'EX DEX' (Domain Executive eXerciser) to test the machine. (Some DEX versions prompt for a password, use 'service'.) At the 'DEX>' prompt type AUTO to run all tests, or run each test separately (e.g. 'RUN CPU'). Type 'HELP' for info. (BEWARE: the cartridge test may overwrite the tape in the drive: use a blank tape.) After each EX-ed program (back at the '>' prompt), it is a good idea to type 'RE' (reset), hit [RETURN] several times, and type 'DI C' if needed. (4) Type 'DI C', then run 'EX INVOL'. On totally blank disks you may need option 7 (initialize physical badspot list, this surely destroys all data), then option 1 (initialize virgin physical volume) and option 8 (create or modify an os paging file). When prompted for the disk, you will need just W (for DN[345]xxx machines) or W6:0 (for DN2500 and 400 series with SCSI disks). (5) Put the machine in NORMAL mode (toggle switch on the back in the up position). (6) Type 'DI C', then run 'EX DOMAIN_OS'. This will ask if to overwrite the disk (answer Y). If you boot (run 'EX DOMAIN_OS') with the machine in SERVICE mode, the booting process will stop at the PhaseII shell with a ')' prompt. You can then complete the booting process by typing 'go' ('help' for more info). (7) When the DM (Display Manager) displays a 'Login:' prompt, log in as 'user' (any password should work, you may want '-apollo-' for safety; in fact you may get logged on as user regardless of what username you type). (8) You will be prompted about how/where to install the operating system. Follow the instructions, read all docs available. You will be asked what you want to load (what template to use). This is going to depend on your disk size, maybe you should load only the environment (bsd or sys5) that you need. This creates an AA (authorized area) on your disk, the system then installs from there. Probably you should choose to install with hard links. When prompted (after the installation completes), shut the system down by positioning the cursor in the DM 'Command:' window (e.g. by pressing the [CMD] key) and type 'shut'. Back at the '>' prompt, type 'RE', then 'EX DOMAIN_OS' to boot from the disk. Now the OS is installed, you should be able to log on as 'user'. You will not have any layered products installed (no C compiler). To install any layered products (from tape), use the command /install/tools/minst and/or /install/tools/install++ and follow the prompts. (Help files are in /install/help/*.hlp.) (9) Since your Apollo is probably stand-alone (no other Apollos on the network), you may want to use the command '/etc/rtsvc -dev ring -off' to prevent it from spending too much time trying to talk on the network. (Use just 'rtsvc' to show name of device and current setting, particularly if you have an ethernet card instead of token ring.) You may want to put that rtsvc command into /etc/rc. Since your Apollo is probably your single-user toy, you do not need to build and maintain a registry, you can do just about anything as 'user'. If you need security and real accounts then you can build a registry as follows. Unlike "real UNIX", there is no /etc/passwd file that you can edit. The read-only object /etc/passwd is provided for backwards compatibility only, the type manager will ask the rgy daemon for all the information. (10) Run /install/tools/rgy_create to create a registry database. (11) Start the NCS and rgyd daemons (check the man pages): /etc/ncs/rpcd (possibly with option 'ncadg_dds'; was /etc/ncs/llbd at older versions of Domain/OS) /etc/ncs/glbd (the first time with '-first -create -family dds -listen dds', thereafter with '-listen dds') /etc/rgyd You must start the daemons in this order. You may want to start each daemon as '/etc/server daemon opt &', e.g. '/etc/server /etc/ncs/rpcs ncsag_dds &'. (12) Create (touch) the files /etc/daemons/rpcd /etc/daemons/glbd /etc/daemons/rgyd so the daemons will be started at reboot from /etc/rc. (Check your /etc/rc file; you may want to add the options above to the invocations.) (13) Reboot, so the daemons run with the 'final' options, and so they run as root. If any of the daemons dies, check for error messages in files in the directory /usr/adm (/sys/node_data/system_logs). (14) The default password for all default accounts (including root) is '-apollo-' (without the quotes). To change/add/delete registry entries use the /etc/edrgy command. Change the passwords on all accounts, maybe also disable most of them (-pnv -anv). Change the ownership of all registry entries, as well as the default ownerships (properties, use the edrgy command 'prop' to list or change). Ensure all the owners are root, not %.%.% (i.e. world) or anyone could create new entries, even new root accounts. (15) Set sensible permissions on your files. The default Apollo permissions (even when choosing 'closed' ACLs at install) are far too open. Look at some scripts I have available from ftp://ftp.maths.su.oz.au/protect . (16) Get a cup of coffee or a beer, and relax...