The NFS root file system to be mounted on the target is generated in the ChorusOS operating system build directory by the command:
% make root
This command populates the build directory with the root directory that contains binary and configuration files to be accessed by the target system.
At start-up, the
C_INIT daemon reads the sysadm.ini configuration file and executes all the commands. See sysadm.ini(4CC) for more information. This configuration file may contain instructions to mount the root file system. For example:
% mount hostaddr:chorus_root_directory /
If there are no root file system mount instructions in your sysadm.ini file, you must mount the root file system explicitly from the shell:
% rsh target mount hostaddr:chorus_root_directory /
where target is the name of the target, or its IP address, hostaddr is the IP address of the NFS host in decimal form (for example 184.108.40.206), and chorus_root_directory is the path of the target root directory on the NFS host (for example /home/chorus/root).
When the mount of the root file system is successful, the
C_INIT daemon displays, for example, the following message:
C_INIT: 220.127.116.11:/home/chorus/root mounted as root file system
The next message from
C_INIT depends on whether the /etc/security file exists in the target root directory /home/chorus/root. If /etc/security exists,
C_INIT: system in secured mode
If /etc/security does not exist,
C_INIT: notice - system not in secured mode
You can check that the root file system is mounted using:
% rsh target mount
Make sure that the file system containing the /home/chorus/root directory can be accessed by NFS from the remote ChorusOS target.