How to Set Up Different Architectures to Access a Shared Name Space

You need to assemble a shared name space for local executables, and applications, such as spreadsheet tools and word-processing packages. The clients of this name space use several different workstation architectures that require different executable formats. Also, some workstations are running different releases of the operating system.

1. Create the auto_local map with the nistbladm command.

   See the Solaris Naming Administration Guide.

2. Choose a single, site-specific name for the shared name space so that files and directories that belong to this space are easily identifiable.

   For example, if you choose /usr/local as the name, then the path /usr/local/bin is obviously a part of this name space.

3. For ease of user community recognition, create an autofs indirect map and mount it at /usr/local. Set up the following entry in the NIS+ (or NIS) auto_master map:

   /usr/local auto_local -ro

   Note that the ro mount option implies that clients will not be able to write to any files or directories.

4. Export the appropriate directory on the server.

5. Include a bin entry in the auto_local map.

   Your directory structure looks like this:

   bin aa:/export/local/bin

   To satisfy the need to serve clients of different architectures, you need references to the bin directory to be directed to different directories on the server, depending on the clients' architecture type.

6. To serve clients of different architectures, change the entry by adding the autofs CPU variable.

   bin aa:/export/local/bin/$CPU

   ---

   Note -

   For SPARCstation^TM clients, make executables available under /export/local/bin/sparc on the server. For x86 clients, use /export/local/bin/i386.

   ---