Installation

Extract crossmeta-nfs_1_0_3.zip file to a folder on local hard disk. The program comes with a setup program that will guide you through the installation. From the extracted files double-click on setup.exe program to launch the Crossmeta File System Installation Wizard. The installation involves several stages as described below.
After successfully completing installation proceed to installing Crossmeta Addon File Systems (ext2fs, xfs, and ReiserFS) from crossmeta-add_1_2.zip.

Stage 1:

Creating the following kernel mode services programs:
• cxvfs (Crossmeta VFS kernel driver)
• cxnfs (Crossmeta NFS kernel driver)
• ext2fs (Crossmeta Linux-ext2fs kernel driver)
• xfs (Crossmeta SGI-xfs kernel driver)
• reiserfs (Crossmeta Linux-reiserfs kernel driver)
Windows service programs
• cxvfsmgr.exe (Crossmeta manager service program)
• portmapd.exe (RPC portmapper service program)
• mountd.exe (NFS mount daemon)
The services are created to be started manually. Otherwise a faulty kernel mode driver will prevent you from booting the system into operational state.

Stage 2:

This stage is for setting up the root file system. Currently the installation program prepares an ordinary file into root file system image. Using loopdev driver interface this file is made available as block device /dev/loop0 for kernel to mount as root file system. This root file system will contain the /bin directory, where the command line programs will be copied to. The root file system will be available in the V: drive, after the services are started.

Stage 3:

This stage is for setting up another file system image called the INODES file. This file system is useful for NFS server operation with Windows native file systems FAT, NTFS or CDFS and is primarily for generating inode number and caching of directory contents. You may skip this if you are not planning to run NFS file server with Windows file systems.

Stage 4:

In this stage the preferred authentication mechanism is selected. The program can automatically map the UNIX uid/gid to Windows SID, provided the user name is same for both. The file /etc/passwd is the user database file for mapping and /etc/group is the group database file. For each user/group there has to be corresponding user/group in the Windows user profile. Otherwise uid/gid will be mapped to LOCAL SID. If user/group in Windows user profile is not present in /etc/passwd or /etc/group it will be mapped to uid/gid NOBODY (-2).

Tip:
Even though the administration commands are installed in V:\bin directory during installation, you may find it useful to keep a copy of them in local drive, by not deleting the extracted files.