Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual page 164

The Traditional Novell Access Control Model
NetWare is known for its rich access control. OES makes these controls available on Linux through
NSS volume support. In addition, some of the controls are available on Linux POSIX file systems
through NCP volume creation. NCP volumes are limited because Linux POSIX systems offer only a
subset of the directory and file attributes that NSS offers.
In the Novell access control model, eDirectory objects, such as users and groups, are assigned File
System Trustee Rights to directories and files on NSS and NCP volumes. These trustee rights
determine what the user or group can do with a directory or file, provided that the directory or file
attributes allow the action.
This is illustrated in
Figure 16-2
Overview of SVN, Help Development, and Localization
Example Work Area (Doc SVN)
https://svn.provo.novell.com/svn/
documentation/Open_Enterprise
_Server/oes2_sp3/help
Writers
Localization picks up the help files to be localized
based on the instructions in the DPP.
Table 16-2
164 OES 2 SP3: Planning and Implementation Guide
Figure 16-2.
Directory and File Access under the NetWare Access Control Model
Help development-related checkins and checkouts
happen only in the documentation SVN repository.
The documentation SVN repository is the only official
repository of documentation source files.
CM
Example Build Area (Build SVN)
Localization
https://svn.provo.novell.com/svn/
some_component
Localization negotiates the handoff of localized help
files with the engineering teams.
Writers are never to be involved with handling
localized help files.
explains the effective access rights illustrated in
Writers negotiate help handoff specifics with their
assigned develoment teams. Some send files in
e-mail; others check directly into the component
build area.
The handoff processes vary, but they should always
be documented for transition purposes.
Writers specify localization handoff details in the DPP,
such as languages required and handoff filenames
and locations.
Figure 16-2.