Warning:
JavaScript is turned OFF. None of the links on this page will work until it is reactivated.
If you need help turning JavaScript On, click here.
The Concept Map you are trying to access has information related to:
chapter 8 distributed file systems, 2. a file system must manage files, including their various attributes, and properly authorize access, 3. a distributed file system includes a directory service. a directory service must provide a user interface and an overall structure to the files., 8.2.4 file replication -when file replication is supported by a distributed file systen, the reliability and efficiency of the file service are greatly enchanced. -solution to file replication in a distributed system may be centralized or distributed., 8.4.2 nfs directory service -nfs assumes a hierarchical structured directory system but does support the creation of soft links to files as are common in unix., 8.4.1 the nfs file service -the nfs file service is a stateless file service and is based on block caching, 8.1.2 location transparency -the second piece of information that can be communicated by the name of a file is the file's location., distributed file systems, 8.3.2 directory management -directory management is concerned with maintaining a proper list of active directories and their respective files., notification on transaction completion, 8.4.3 nfs name service -nfs name service support is based on the mounting of a file or directory. nfs does not support one global name space., summary -a distributed file system has three primary responsibilities., immutable -modification are not allowed, 8.1 distributed name service -focuses on the issues related to file names, 1. provide a method for naming files and managing file names through a name service., notification on close, 8.2.3 file service implementations -file service implementations may be based on remote access or remote copy and may be stateful or stateless., 8.3 distributed directory service -the distributed directory service of the distributed file system is responsible for the overall file organization., 8.4 nfs, immediate notification, 8.3.1 directory structures -the first is that of a hierarachical directory structure, 8.1.1 file types -various operating systems allow different types of files and support file types differently., 8.1.3 global naming and name transparency -for a distributed file system to support location transparency, it must support global naming. a global name space requires one or both of the following types of resolution. -name resolution -location resolution, 8.2 distributed file service -is responsible for operations on a particular file, mutable -modifications are allowed, 8.2.1 file variations -files may also vary in terms of how they are stored, the various attributes assigned to files, as well as the mode of protection utilized by the base operating system., 8.5 x.500 -is an international standard defined by the ccitt currently known as itu-t and the iso. this directory service is designed to provide the internet equivalence of telephone companies white and yellow pages as well as mail and e-mail address lookup., 8.5.2 x.500's directory service the directory model -x.500's directory service is defined in terms of what it refers to as the directory model, which is designed with the assumption that there will be significantly more queries versus updates., 8.2.2 file modification notification -when multiple locations access shared files, every participant must agree upon a method for notifying other participants regarding modification to files also commonly referred to as file access semantics., 8.5.1 x.500 file and name service the information model -x.500's file and name service is defined in terms of what it refers to as the information model. the information model is responsible for how the information is stored and arranged.