Content deleted Content added
m →History: copyedits. Removed cyclic reference to the same page. |
m →Description: copyedits |
||
Line 12:
OSF and its projects eventually became part of [[The Open Group]], which released DCE 1.2.2 under a [[free software license]] (the [[GNU Lesser General Public License|LGPL]]) on [[12 January]] [[2005]]. DCE 1.1 was available much earlier under the OSF BSD license, and resulted in [http://freedce.sf.net|FreeDCE] being available since [[2000]]. FreeDCE contains an implementation of DCOM.
==
The largest unit of management in DCE is a '''cell'''. The highest privileges within a cell are assigned to a role called ''cell administrator'', normally assigned to the "user" ''cell_admin''. Note that this need not be a real OS-level user. The cell_admin has all privileges over all DCE resources within the cell. Privileges can be awarded to or removed from the following categories : user_obj, group_obj, other_obj, any_other for any given DCE resource. The first three correspond to the owner, group member, and any other DCE principal respectively. The last group contains any non-DCE principal. Multiple cells can be configured to communicate and share resources with each other. All principals from external cells are treated as "foreign" users and privileges can be awarded or removed accordingly. In addition to this, specific users or groups can be assigned privileges on any DCE resource, something which is not possible with the traditional UNIX filesystem, which lacks ACLs.
Major components of DCE within every cell are:
There are three major components of DCE within every cell: (1) the security server (which is responsible for authentication) (2) The Cell Directory Server (CDS) (which is the respository of resources and ACLs) and (3) The Distributed Time Server which provides an accurate clock for proper functioning of the entire cell. Modern DCE implementations such as IBM's are fully capable of interoperating with Kerberos as the security server, LDAP for the CDS and the [[Network Time Protocol]] implementations for the time server.▼
#the '''security server''' that is responsible for authentication
#The '''Cell Directory Server''' (CDS) that is the respository of resources and ACLs and
▲
While it is possible to implement a distributed file system using the DCE underpinnings by adding filenames to the CDS and defining the appropriate ACLs on them, this is not user-friendly. DCE/DFS is a DCE based application which provides a distributed filesystem on DCE. DCE/DFS can support replicas of a fileset (the DCE/DFS equivalent of a filesystem) on multiple DFS servers - there is one read-write copy and zero or more read only copies. Replication is supported between the read-write and the read-only copies. In addition, DCE/DFS also supports what are called "backup" filesets, which if defined for a fileset are capable of storing a version of the fileset as it was prior to the last replication.
DCE/DFS is believed to be the world's only distributed filesystem that correctly implements the full POSIX filesystem semantics, including byte range locking. DCE/DFS was sufficiently reliable and stable to be utilised by [[IBM]] to run the back-end filesystem for the [[1996]] [[Olympics]] web site, seamlessly and automatically distributed (and edited!) worldwide in different timezones.
==External links==
| |||