By default, NetWare Traditional volumes support DOS naming conventions. To store non-DOS files on a Traditional volume, you must load the appropriate name-space NetWare Loadable Module™ (NLM™) program and add the name-space support to that volume. The following NLM programs are available with NetWare:
mac.nam (Macintosh*)
long.nam (IBM* OS/2*, Windows)
nfs.nam (NFS)
An FTAM name space module is available from third-party providers.
Each name space you add to a Traditional NetWare volume requires additional server memory. If you add name-space support to a volume and do not have enough memory, that volume cannot be mounted.
If you have insufficient memory to mount a Traditional volume with a long name space, you might want to convert the volume to an NSS volume. For information, see Upgrading Legacy NSS and NetWare Traditional Volumes
in the NW 6.5 SP8: NSS File System Administration Guide.
This section discusses the following:
Use the following formula to calculate the name space memory requirement for Traditional NetWare non-DOS volumes:
0.032 x volume_size (in MB) / block_size (in MB)
Round the size up to the highest number.
For example, adding Macintosh name space to a 100 MB volume with a block size of 4 MB would require 1 MB of additional memory:
0.032 x 100 MB / 4 = 0.8 MB
You must add name spaces only once, not each time you start the server.
A mounted Traditional volume
Sufficient memory
To load the appropriate name space: At the server console prompt, enter:
load [path]name_space
For example, to load the name space module for Macintosh support, enter:
load mac.nam
To add name-space support to the volume: At the server console prompt, enter:
add name space name to volume_name
In this example, name is the name space NLM and volume_name is the name of the volume that stores the non-DOS files.
To verify that the name space loaded: At the server console prompt, enter:
volumes
This displays a list of all name spaces for the server.
You can remove the name space by deleting the volume and re-creating it, or by using the Vrepair utility. For instructions, see Section 4.20, Repairing a Traditional Volume.