Now that you know a little about NSS, you can start planning your NetWare 6.5 file system. Consider the following tips for creating a robust, accessible, and easy-to-manage file system:
You can have home directories created automatically when you create a new user , as explained in Chapter 6 .
These tips can help you effectively plan your file system. In addition, you should take into consideration the directories that NetWare creates automatically during installation, as well as plan for directories that will contain applications. These issues are described in the following sections.
NetWare System Directories
When you install a NetWare server for the first time, there are several directories created by the system with which you should be familiar. These directories contain most of the tools, utilities, and configuration files that you need to configure, monitor, and manage your NetWare 6.5 server. All NetWare system- related directories are created in volume SYS: , a few of which include the following:
Because the SYS volume contains many directories containing files required for running and managing your NetWare network, do not rename or delete any of them without making absolutely sure they're unnecessary in your particular network's situation. This is another good reason not to mix your business applications and data with the system files on SYS .
There are many other directories related to specific services that you can load on a NetWare 6.5 server, and you can create additional directories and subdirectories in volume SYS , if desired.
For files not directly related to NetWare, or your network environment, it makes more sense to create a separate file structure. That way there will be fewer chances for problems to be introduced into your core NetWare system through extraneous installation, configuration, or management activities.
You need to consider application and file placement when planning your NetWare file system. By doing so, you can create a file structure in which it is much easier to assign proper trustee rights so that users have access to what they need, but without granting them access to things they don't. For example, general-use applications can be organized in an APPS volume, each in its own subdirectory. That way, rights to these applications can be easily assigned high in the directory structure where they will flow down, through inheritance, to all subdirectories. For more information about file system rights, see Chapter 6.
If an application requires that it be installed at the root of a file system, NetWare gives you the flexibility of installing the application where it makes sense and then creating a root drive mapping to fool the application into thinking it is operating from a root location in the file system. Creating a root drive mapping requires the redirector capabilities of either the Novell client or the NetDrive client. See Chapter 2, "Novell Clients," for more information on the Novell client. See Chapter 10, "NetWare File Access," for more information on NetDrive.
You can create a map root from the client, but if it is needed for a large number of users, a much better way is to include the map command in the appropriate login script. That way the map operation will be performed automatically when each user logs in and you don't have to worry about making changes to every workstation. For example, you can add the following command to a container login script to map a root drive for all users within the container:
MAP ROOT S16:=VOL1:APPS\ABC
For more information about login scripts, see Appendix B.
If you decide to host an application from the NetWare server, you should flag the application's executable files as Shareable, Read-Only (S, Ro). This allows the application to be used by multiple users simultaneously , but prevents users from inadvertently deleting or modifying it. This is an additional layer of protection beyond that provided by restricting access to the files at the directory level. For more information on file system rights, see Chapter 6.