1. Binary Packages
See UsersGuide/InstallingBinaryPackages on how to install prebuilt packages from the network or from the installation CD.
2. Recompiling the system from source
3. Set the Root Password
You should set a password for the root account. Type:
Then enter the new password in the prompts (No characters or *'s will appear as you type your password but it IS being entered).
4. Set the Timezone
Unix systems always run the clock using UTC time (sometimes named as Greenwich time). You should adjust the timezone setting to have the dates shown by utilities to be like your wall clock. Type:
echo export TZ=Europe/Amsterdam > /etc/rc.timezone
echo export TZ=America/New_York > /etc/rc.timezone
The timezone will be set when you log in again.
Of course, you should adjust Europe/Amsterdam according to your location. You can look into the /usr/share/zoneinfo hierarchy to find the correct name. The general principle is continent/city or ocean/city, where city is the English name of the biggest city in the same timezone as you. The city would ideally be in your country, since timezone rules have a strong tendency to vary according to national rules.
5. Adding Users
Always logging in as root is usually a bad idea, so it is highly recommended to set up at least one other user as soon as possible. For directions on how to do that please see: Managing User Accounts
6. Setting the Host Name
You can use the hostname(1) command to manually set the system hostname. For example:
# hostname minix.example.com
When DHCP is enabled, your settings will be overriden by the DHCP client when renewing the lease.
By default, MINIX runs a DHCP client at boot time, to request an IP address from your DHCP server.
In this case, typically you will not know what the IP address will be and so providing a host name for the system has no functional purpose. But, if you arrange for your DHCP server to always assign the same address to your MINIX system, based on the machine's MAC address, then naming the MINIX host has a real purpose, e.g., you can SSH to it from another machine on your network.
The same is true if you disable the running of the DHCP client at system initialization time and instead manually assign a static IP address (see boot(8) for more information). So if you know what the IP address will be and wish to assign a name to your MINIX host, enter the address/name pair into /etc/hosts (see hosts(5) for specific information about the format of that file).
7. Changing Keyboard Layouts
Several keyboard layouts are available. These layouts are loaded from files called "keymaps."
For example, here's how to enable the Swapped Caps & Ctrl U.S. keymap:
To make the keymap the default:
cp /usr/lib/keymaps/us-swap.map /etc/keymap
For details, see keymap(5). This contains the complete documentation on how to create and configure keymaps. The keymap source code is in /usr/src/drivers/tty/keymaps.
The PKGSRC OpenSSH package contains both the client (ssh) and the daemon (sshd). To install it after you have done pkgin update, type: pkgin install openssh. Then type: reboot to start the daemon.
We recommend installing this, as it allows ssh access from another host, which improves greatly the user experience in the absence of X11.
If you installed MINIX in a virtual machine, please refer to the Virtualization chapter for your virtual machine monitor of this user guide for further instructions on how to enable network access to the MINIX guest.
8. Running the test sets
After installing MINIX, you can check the status of your system by running different tests.
8.1. MINIX POSIX (and more) tests
To run the MINIX tests do the following:
# cd /usr/tests/minix-posix # ./run
Warning: This test suite is extremely extensive, and my take up to several hours to complete, depending on your hardware. The usual run time on current computer (about 2GHz Intel CPUs) is about half an hour.
You might see some warning, those are fine as long as the test prints "ok" at the end.
After all the tests have been run, a summary will be printed.
8.2. KYUA tests
We have imported the KYUA test suits. At this moment we have not yet spent much time trying to get all tests to pass. It is expected that some are marked as broken, and / or failed.
Also not everything which is tried is relevant on MINIX, for example we do not have quota support, which is why all the related tests fail.
Anyway, to see how much MINIX is NetBSD-compatible, you can run the kyua tests as follow:
# cd /usr/tests # kyua test
To see the report, you can use on of
# kyua report # text-only report # kyua report-html # HTML report # kyua report-tap # TAP report
Note: The KYUA tests are not yet supported on MINIX/arm.