Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 481 — #507
i
i
i
i
i
i
i
i
21
Linux in the Network
inetOrgPerson inetOrgPerson
(person-related
data for the
intranet or
Internet)
Geeko Linux sn and cn
Example 21.17 shows an excerpt from a scheme directive with explana-
tions.
Example 21.17: Excerpt from schema.core
(line numbering for explanatory reasons)
#1 attributetype (2.5.4.11 NAME ( ’ou’ ’organizationalUnitName’)
#2 DESC ’RFC2256: organizational unit this object belongs to’
#3 SUP name )
...
#4 objectclass ( 2.5.6.5 NAME ’organizationalUnit’
#5 DESC ’RFC2256: an organizational unit’
#6 SUP top STRUCTURAL
#7 MUST ou
#8 MAY (userPassword $ searchGuide $ seeAlso $ businessCategory
$ x121Address $ registeredAddress $ destinationIndicator
$ preferredDeliveryMethod $ telexNumber
$ teletexTerminalIdentifier $ telephoneNumber
$ internationaliSDNNumber $ facsimileTelephoneNumber
$ street $ postOfficeBox $ postalCode $ postalAddress
$ physicalDeliveryOfficeName
$ st $ l $ description) )
...
The attribute type organizationalUnitName and the corresponding ob-
ject class organizationalUnit serve as an example here. Line 1 features
the name of the attribute, its unique OID (object identifier) (numerical), and
the abbreviation of the attribute.
Line 2 gives brief description of the attribute with DESC. The corresponding
RFC on which the definition is based is also mentioned here. SUP in line 3
indicates a superordinate attribute type to which this attribute belongs.
The definition of the object class organizationalUnit begins in line 4,
like in the definition of the attribute, with an OID and the name of the ob-
ject class. Line 5 features a brief description of the object class. Line 6, with
its entry SUP top, indicates that this object class is not subordinate to an-
other object class.
481
SUSE LINUX Enterprise Server