Release Notes
Chapter 2, Read this after installation
Installing NetWare Loadable Modules (NLMs) on NetWare

Installing NetWare Loadable Modules (NLMs) on NetWare

The new NUC.NLM for NetWare 4.x is now supported.

NOTE: The installation procedure for these new NLMs differs considerably from the procedure for earlier versions. The UNISTART.NCF file must now specifically name each volume you want to load. In addition, extra steps are required to load the NLMs on a 3.11 or 4.x NetWare server.

The NUC and NFS NLMs run on NetWare versions 3 and greater. When a NetWare filesystem is mounted from a UNIX system, the loaded NUC and NFS NLMs give the NetWare filesystem UNIX semantics such as long filenames, mixed case letters in filenames, symbolic links, and support for owners and groups.

To take advantage of these features, install the NLMs on all NetWare file servers version 3 and above, that will be mounted by an SCO OpenServer system running the SCO Gateway for NetWare.

Ensure that the SCO Gateway for NetWare is installed on the UNIX system before proceeding.



Step 1: 3.11 only: Install NetWare patch and load other NLMs

If you are installing on NetWare 3.11, you must install a server patch. The patch is available from ftp.novell.com, as /pub/updates/nwos/nw312/libup5.exe.

After installing the patch, and before installing the new NLMs, enter:

load nwsnut
load bcastlib

You might see the message: unable to find load file BCASTLIB. This message can safely be ignored. If you see it, however, you will also see the message: Could not load module PKERNEL for configuration during step 4. This message may also safely be ignored; press <Esc> to continue. The missing bcastlib NLM file will then be installed on your system. 

Step 2: Cut two floppy disks containing the NLMs

The NLMs must be installed from two floppies. Images of the required DOS floppies were stored on the SCO OpenServer CD-ROM, in the /images/nuc directory. Copy the images to two double-sided, high density, 3.5-inch floppy disks. 

Step 3: Copy NLMs from the floppies to the NetWare file server

  1. From the NetWare server, press <Ctrl><Esc> simultaneously to start the Current Screens menu. This menu displays the currently loaded options. Start the Install Screen option in one of two ways:

  2. From the Installation Options menu, select Product Options.

  3. When the Currently Installed Products window appears, press <Insert>.

  4. Insert the first NLM floppy in the NetWare server floppy drive.

  5. At the prompt, select the drive in one of two ways:

  6. At the prompt, select the drive you are using to boot NetWare. The most common choices are drive A: for the 3.5-inch floppy drive and drive C: for the hard drive. Select the drive in one of two ways:

  7. If you are booting the NetWare server from a floppy disk, the system prompts for the volume name of the NetWare boot floppy. After you enter the volume name, the system prompts you to insert the NLM floppies and the boot floppy disk several times to transfer the required data.


Step 4: Add UNIX name space support to NetWare volumes

To add UNIX filesystem name space to NetWare volumes, you must reserve space on the volumes that will be mounted by UNIX clients to hold the extra UNIX filesystem semantic information.

From the NetWare file server:

  1. If you are not already at the Current Screens menu, press <Ctrl><Esc> simultaneously to start the Current Screens menu.

  2. Select the number corresponding to System Console.

  3. At the system console prompt (:) enter:

    load nfs
    add name space nfs to volume volume_name

    where volume_name is the name of the NetWare volume to be mounted.

    This takes several minutes. During this time, you are informed of disk space requirements for this operation.

  4. Repeat the add name space nfs to volume volume_name command for each NetWare volume that requires UNIX filesystem semantics.

    The commands load nfs and add name space are done once per NUC NLM installation. These commands do not need to be added to AUTOEXEC.NCF.



Step 5: Edit the NFSUSERS, NFSGROUP, and PASSWD files

  1. Log in to the NetWare server as supervisor.

  2. Create the group EVERYONE on NetWare if it does not already exist. Add all users to this group. This facilitates an automatic mapping between the UNIX system others category and the NetWare EVERYONE group.

  3. Edit the SYS:\ETC\NFSUSERS and SYS:\ETC\NFSGROUP files, which were created when the NLMs were installed.

    The NFSUSERS file contains lines with the format:

    UnixUid <Tab> NetWareLogin

    and the NFSGROUP file contain lines with the format:

    UnixGid <Tab> NetWareGroup

    UnixUid
    is the UNIX system user identification number

    NetWareLogin
    is the NetWare login name

    UnixGid
    is the UNIX system group identification number

    NetWareGroup
    is the NetWare group name

    Add entries for all the UNIX system users and groups that will to use the NetWare file server.

  4. Update the SYS:\ETC\PASSWD file to contain entries identical to those in the /etc/passwd file on the UNIX system.



Step 6: Edit the UNISTART file

Edit or create the file SYS:\SYSTEM\UNISTART.NCF. This file must contain the lines:

load tsaproxy
load nuc all

If you want only some of your NetWare volumes to support NFS name space, you must name each one separately:

load nuc volume_name_1 volume_name_2

NOTE: This is different from the previous installation procedure. The file may already contain the line load nuc. It must be changed to read load nuc all.



Step 7: 3.11 only: Add a first line to start bcastlib

If you are installing on NetWare 3.11, add the following as the first line of the UNISTART file:

load bcastlib



Step 8: Edit the UNISTOP file

Edit or create the file SYS:\SYSTEM\UNISTOP.NCF. This file must contain one unload line for each load line in UNISTART. For example:

unload nuc



Step 9: 4.x only: Load inetdb

If you are installing on NetWare 4.x, run the command:

load inetdb admin_login password

where admin_login is the fully-qualified NDS administrative login for this server, and password is the password for this account.

Run this command only once. It does not need to be repeated after subsequent reboots. 

Step 10: Start the NLM manually

To start the NUC NLM now without rebooting:

  1. Press <Ctrl><Esc> simultaneously to start the Current Screens menu.

  2. Select the number corresponding to System Console.

  3. At the system console prompt (:), enter unistart.

NOTE: To stop the NLM at any time, enter unistop at the system console prompt (:).



Step 11: Configure the system to start the NLM automatically

To ensure the NLMs are started when the server is booted, edit the AUTOEXEC.NCF file. From the NetWare server:

  1. Press <Ctrl><Esc> simultaneously to start the Current Screens menu. This menu displays the currently loaded options. Start the Install Screen option in one of two ways:

  2. Select System Options.

  3. Select Edit AUTOEXEC.NCF.

  4. Near the end of the AUTOEXEC.NCF file, add the command:

    unistart.ncf

    This should usually be placed just before the line with the load monitor command.

  5. Delete the command load nuc if it is present in the file.

  6. Press <Esc> when done.

  7. Select Yes to save the modified file or <Esc> to cancel this edit.


Step 12: 4.x only: Set up NDS mappings

On NetWare 4.x, for the owner and group mappings to work, you must create NDS (NetWare Directory Services) users and groups for every user and group referenced. NDS users and groups are created using the NWADMIN command from a Windows client, or the NETADMIN command from a DOS client.