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 applications 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.

Create the auto_local map.

For more information about naming services, see Working With Oracle Solaris 11.4 Directory and Naming Services: DNS and NIS.
Choose a single, site-specific name for the shared name space.

This name makes the files and directories that belong to this space easily identifiable. For example, if you choose /usr/local as the name, the path /usr/local/bin is clearly a part of this name space.
Create an autofs indirect map and choose a path name to anchor it.
Mount this map at /usr/local. Set up the following entry in the NIS auto_master map:
```
/usr/local     auto_local     -ro
```
Notice that the -ro mount option means that clients cannot write to any files or directories.
Export the appropriate directory on the server.
Include a bin entry in the auto_local map.
Your directory structure resembles the following:
```
 bin     aa:/export/local/bin 
```
where, aa is the name of the server.
To serve clients of different architectures, change the entry by adding the autofs CPU variable.
```
bin     aa:/export/local/bin/$CPU
```
where, aa is the name of the server.
- For SPARC clients – Place executables in /export/local/bin/sparc.
- For x86 clients – Place executables in /export/local/bin/i386.