Organization Names

The binding of an FNS orgunit is determined by the underlying naming service:

• Under NIS+, an organizational unit corresponds to an NIS+ domain or subdomain. For example, assume that the NIS+ root domain is doc.com. and sales is a subdomain of doc.com. Then, the FNS names org/sales.doc.com. and org/sales both refer to the organizational unit corresponding to the NIS+ domain sales.doc.com. (Note the trailing dot in sales.doc.com.which is required for fully qualified NIS+ names.)

• Under NIS, an organizational unit is the NIS domain which is always identified by the FNS name org// or org/domainname where domainname is a fully qualified domain name such as doc.com. Under NIS, there is no hierarchy in organizational unit names.

• Under a files-based naming system, the organizational unit is the system which is always identified by the FNS name org//.

The types of objects that may be named relative to an organizational unit name are: user, host, service, fs, and site. For example:

• org/sales/site/conference1.bldg-6 names a conference room conference1 located in building #6 of the site associated with the organizational unit sales. In this example, if org/sales corresponds to sales.doc.com, another way to name this object would be: org/sales.doc.com./site/conference1.bldg-6 (note the trailing dot in sales.doc.com.)

• org/finance/user/mjones names a user mjones in the organizational unit finance.

• org/finance/host/inmail names a machine inmail belonging to the organizational unit finance.

• org/accounts.finance/fs/pub/reports/FY92-124 names a file pub/reports/FY92-124 belonging to the organizational unit accounts.finance.

• org/accounts.finance/service/calendar names the calendar service of the organizational unit accounts.finance. This might manage the meeting schedules of the organizational unit.