I bin 1
I
aI
I f l 1 etc II I I 1 I 1 I I
+-
-+-+-
-+---+- -+-+- -+\ root \
1 micronix, finstall, badblocks
I
\ I
+-
-+-+-
-+-+--+---+-
-+1 1
I
'llost+11
I~_\ dev I 1 tmp 1 1 found \ I spool usr adm I +---+ +---+ +---+
---1 1---- .
__ I
I~_1 upm bin I
---1
1---+---+~ -+---+
I
manI
+-+- -+-+-
-+-+--+-+-
-+-t--+-+
I I I I I I I I I \ 1 I
I mana 1 I manl\ I man21 I man3\ I man41 I manS \ +---+ +---+ +---+ +---+ +---+ +---+
You can add new files and directories where you like to the root, or any other directory. The initial path ways to these directorie.s are important, however, so don't go renaming "man" to
"manuals", or "bin" to "commands" because you will make these directories impossible to find for the.prQgrams that;know where they are now.
4.4 ADDING A PASSWORD FOR ROOT
You are now approaching a momentous occasion: you are about to add some security' to your Micro~ix system. As the system stands,' anyone can become the root by resetting the system and booting Micronix. The root is also known as the superuser because there is absolutely no protection from the person logged in as root. The root user can examine any file, or remove any file. The reason for the root's power of unlimited access is that a user must exist that cart access all the files for backup, or to use fsck.
You can easily prevent this unlimited access by using the passwd command to install a password for the root. Once you have installed a password, you will have to remember what it is because you will use it every time you reset the system or log in as root. If you ever forget or lose the root password, you will have . to "operate" on the passwd file from the Standalone Micronix disk and remove the root's password. Okay. Let's choose a password for root.. You should probably write it down, and keep it someplace safe. Suggested passwords are nonsense words, or, even better, combinations of letters and numbers at least eight characters long. As an example, let's use
"az804me2".
1/ passwd
New Password (or RETURN fQr no password):
Once again to be sure:
1/ []
The characters "az804me2" were typed after both colons in the example. The passwords you use will never appear on the 'screen for security reasons. The reason for typing the password twice is to check that you typed it correctly the first time.
4.5. GOING MULTIUSER
The transition from single-user to multi-user Micronix is very simple. Just type
1/ exit
and press <RETURN). Micronix will then automatically make the changes necessary to become multi-user. After going multi-user, the Micronix banner will be displayed, and a log-in name requested, as in
Name:'
Since this is still, presumably, . your first use of Micronix, you should use the name "root". Next, you will be asked for a password. Type in the password that you added for root in the last section. The message of the day will then be displayed; and the' "/!"prompt. After you have added other user names, you will be able to log-in using names other than the root.
Even if you plan to be the only user on your ,system, you should probably bring your Micronix system up multi-user. Until your system is multi-user, only the console can be used. If you have a program crash while you are working at the console, the console could still be under the control of the crashed program.
Then, the only way to regain control is to reset the system, risking possible data loss and damage to the file system. But, if you are operating in multi-user mode, you can plug your terminal into the second serial port, log-in, and kill the offending program that has captured the console. See the section named Desparate Measures in Maintenance and Administration.
The other important advantage of going multi-user is the waking up of the update daemon. The update daemon sleeps in the background, and wakes up every thiry seconds to execute the sync command. The periodic and automatic syncs by the update daemon serve to keep the disk current with memory without any intervention on your own part. This can be a file system saver if the system goes down unexpectedly.
The update daemon is started during execution of the script in the /etc/rc file. If you have other commands that you want to
execute routinely while going multi-user, you can edit /etc/rc and add the commands here. For example, you could run fsck as part of this routine without actually ever keying in the command.
See edit in the Programs section of the Reference Manual, and rc in the Files section.
4.6. 'rUINING YOUR MICRONIX SYSTEM' ON AND OFF
We are sure that you understand that you can't turn Micronix on and off like a desk lamp. As we have mentioned, improper shutdowns are a prime cause of file system damage. Since your system is currently on and running multi-user, let's turn it off the right way.
The software command for bringing down your Micronix system is named "down". The down command first calls the sync command to synchronize the disks with memory. Then, down goes out and kills any processes that are still alive. When it is finished, the message
Micronix is down
is d~splayed on the console. After this message has _appeared, you can turn the power off to your hard disk, (if it is in a' separate cabinet),' and then turn the power off to the Decision and other peripherals (terminals, printers, modems, etc.).
The down command can only be used by the superuser. You are the superuser when you are logged in as root, and have the superuser prompt,
"/I".
This is because only. the superuser has permission to kill all active processes. Before typing "down" as superuser, you should certainly inform everyone else who is using the system that you intend to bring it down. If the other users aren't in the same room as you, you can use the.wall (write all) command to send them a warning:/I wall
I am turning the system off in 1 minute!!!
<CONTROL-D)
/I I am turning the system off in 1 minute!!!
[ ]
The <CONTROL-D) means hold down the control key and type Control-d is used to signal end of file to Micronix, in case, end of message.
a d.
this
To turn your system on, you start by turning the power on to the hard disk, if it is in a separate cabinet from the Decision, then turn on the Decision. After you turn on the hard disk, you will hear its drive motor come up to speed, and possibly the sound of the stepper after several seconds.
Insert the CP/M Cold Boot Loader diskette and press Reset or flick the keyswitch to the Reset position. If the system passes its startup diagnostics tests,. the CP/M prompt (A» and sign-on message appear on the console. There are other possiblities that indicate a hardware problem, which were discussed back in section 2.7.2. When CP/M presents its prompt, you need to type the name of the loader program for your system:
m5boot ml0boot m16boot 'hdboot
for 5 megabyte hard disks for 10 megabyte hard disks for 16 megabyte hard disks for hard disks with the HDC
controller
For example, to load Micronix on a 10 megabyte hard disk, you should type
A>ml0boot<return>
and Micronix will begin loading from the 10 megabyte hard disk.
If you have installed a password on the root, you will be required to log-in as root and use the password. After logging in, there are two thing.s to do:
o run fsck on the /dev/root device, and o set the date.
Both fsck and date have been explained previously.
It is possible to load Micronix without using CP/M. Reading the section in MAINTENANCE AND ADMINISTRATION about' the SYSGEN command will explain how to create a diskette that loads Micronix directly.