Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109268
N. Hutchinson, L. Peterson, H. Rao
An operating system design that views a workstation as a portal through which users access Internet resources is proposed. Such a system should accommodate a variety of protocol suites yet present users with an integrated and uniform interface to all the protocols and, as a consequence, to all Internet resources. Toward this end, they have designed an operating system, called the x-kernel, that consists of three major components: a configurable kernel that provides uniform access to a wide array of protocols, a heterogeneous file system, and a customizable user interface. The central element in this design is the protocol. The kernel implements a library of useful protocols. The file system and user interface in turn, provide a per-user environment that translates a resource name into the protocol that should be used to access the resource. The authors describe the library of protocols, the file system and the user interface.<>
{"title":"The x-kernel: an open operating system design","authors":"N. Hutchinson, L. Peterson, H. Rao","doi":"10.1109/WWOS.1989.109268","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109268","url":null,"abstract":"An operating system design that views a workstation as a portal through which users access Internet resources is proposed. Such a system should accommodate a variety of protocol suites yet present users with an integrated and uniform interface to all the protocols and, as a consequence, to all Internet resources. Toward this end, they have designed an operating system, called the x-kernel, that consists of three major components: a configurable kernel that provides uniform access to a wide array of protocols, a heterogeneous file system, and a customizable user interface. The central element in this design is the protocol. The kernel implements a library of useful protocols. The file system and user interface in turn, provide a per-user environment that translates a resource name into the protocol that should be used to access the resource. The authors describe the library of protocols, the file system and the user interface.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124017928","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109274
B. C. Neuman
It is noted that users of the future will require access to objects and services that are scattered across large networks and that the workstation can mold these objects and services into complete systems. The author suggests that in order to talk about the role of the workstation in such systems, one must have an idea of how they will be organized. He describes one model for organizing such systems and shows how the workstation might fit in.<>
{"title":"Workstations and the virtual system model","authors":"B. C. Neuman","doi":"10.1109/WWOS.1989.109274","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109274","url":null,"abstract":"It is noted that users of the future will require access to objects and services that are scattered across large networks and that the workstation can mold these objects and services into complete systems. The author suggests that in order to talk about the role of the workstation in such systems, one must have an idea of how they will be organized. He describes one model for organizing such systems and shows how the workstation might fit in.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127719475","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109263
R. Cooper, K. Birman
The extension of the ISIS distributed programming system to support large-scale distributed applications by providing hierarchical process groups is discussed. The present version of ISIS is limited to relatively small-scale applications, containing fewer than 50 workstations. The principal idea is to incorporate hierarchy in the program structure and exploit this to limit the communication and storage required in any one component of the distributed program. This approach seeks to maintain the advantages of virtual synchrony, while controlling those costs that grow as the size of a distributed application increases.<>
{"title":"Supporting large scale applications on networks of workstations","authors":"R. Cooper, K. Birman","doi":"10.1109/WWOS.1989.109263","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109263","url":null,"abstract":"The extension of the ISIS distributed programming system to support large-scale distributed applications by providing hierarchical process groups is discussed. The present version of ISIS is limited to relatively small-scale applications, containing fewer than 50 workstations. The principal idea is to incorporate hierarchy in the program structure and exploit this to limit the communication and storage required in any one component of the distributed program. This approach seeks to maintain the advantages of virtual synchrony, while controlling those costs that grow as the size of a distributed application increases.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"96 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130370490","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109266
R. Hagmann
The current state and future development of virtual memory with particular reference to workstations, is discussed. The author considers the usefulness of virtual memory, exploring what has changed in software and hardware since virtual memory was introduced. Programs are loosely divided into three categories, and the usefulness of virtual memory is assessed for each category. The costs in speed, product development, space, and money are discussed. The author deals with the question of what piece of software should be responsible for virtual memory decisions. He concludes that the user, programmer, or programming environment are better suited to provide this function than the operating system.<>
{"title":"Comments on workstation operating systems and virtual memory","authors":"R. Hagmann","doi":"10.1109/WWOS.1989.109266","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109266","url":null,"abstract":"The current state and future development of virtual memory with particular reference to workstations, is discussed. The author considers the usefulness of virtual memory, exploring what has changed in software and hardware since virtual memory was introduced. Programs are loosely divided into three categories, and the usefulness of virtual memory is assessed for each category. The costs in speed, product development, space, and money are discussed. The author deals with the question of what piece of software should be responsible for virtual memory decisions. He concludes that the user, programmer, or programming environment are better suited to provide this function than the operating system.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127863910","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109261
R. Balter, D. Decouchant, A. Duda, A. Freyssinet, S. Krakowiak, M. Meysembourg, M. Riveill, C. Roisin, X. R. D. Pina, R. S. Garcia, G. Vandome
A brief description is given of how the issues of access to (possibly remote) services and cooperative distributed computing are treated in GUIDE (Grenoble universities integrated distributed environment), a distributed operating system under development at Grenoble on a local network of workstations. An overview of the project is given, and the computational model of the system is described. Remote computation is discussed. The current implementation status and experience with the system are examined.<>
{"title":"Experience with object-based distributed computation in the GUIDE operating system","authors":"R. Balter, D. Decouchant, A. Duda, A. Freyssinet, S. Krakowiak, M. Meysembourg, M. Riveill, C. Roisin, X. R. D. Pina, R. S. Garcia, G. Vandome","doi":"10.1109/WWOS.1989.109261","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109261","url":null,"abstract":"A brief description is given of how the issues of access to (possibly remote) services and cooperative distributed computing are treated in GUIDE (Grenoble universities integrated distributed environment), a distributed operating system under development at Grenoble on a local network of workstations. An overview of the project is given, and the computational model of the system is described. Remote computation is discussed. The current implementation status and experience with the system are examined.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"346 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132713612","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109279
M. Satyanarayanan, James J. Kistler, Puneet Kumar, Maria E. Okasaki, E. Siegel, D. Steere
A description is given of Coda, a file system for a large-scale distributed computing environment composed of Unix workstations. It provides resilience to server and network failures through the use of two distinct but complementary mechanisms. One mechanism, server replication, involves storing copies of a file at multiple servers. The other mechanism, disconnected operation, is a mode of execution in which a caching site temporarily assumes the role of a replication site. Disconnected operation is particularly useful for supporting portable workstations. The design of Coda optimizes availability and performance and provides the highest degree of consistency attainable. Measurements from a prototype show that the performance cost of providing high availability in Coda is reasonable.<>
{"title":"Coda: a highly available file system for a distributed workstation environment","authors":"M. Satyanarayanan, James J. Kistler, Puneet Kumar, Maria E. Okasaki, E. Siegel, D. Steere","doi":"10.1109/WWOS.1989.109279","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109279","url":null,"abstract":"A description is given of Coda, a file system for a large-scale distributed computing environment composed of Unix workstations. It provides resilience to server and network failures through the use of two distinct but complementary mechanisms. One mechanism, server replication, involves storing copies of a file at multiple servers. The other mechanism, disconnected operation, is a mode of execution in which a caching site temporarily assumes the role of a replication site. Disconnected operation is particularly useful for supporting portable workstations. The design of Coda optimizes availability and performance and provides the highest degree of consistency attainable. Measurements from a prototype show that the performance cost of providing high availability in Coda is reasonable.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130394608","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109271
B. Liskov, L. Shrira, J. Wroclawski
A novel message-passing protocol that guarantees at-most-once message delivery without requiring communication to establish connections, is described. The authors discuss how to use these messages to implement higher level primitives such as at-most-once remote procedure calls (RPC) and describe an implementation of at-most-once RPCs using their method. Performance measurements indicate that at-most-once RPCs can be provided at the same cost as less desirable RPCs that do not guarantee at-most-once execution. The method is based on the assumption that clocks throughout the system are loosely synchronized. Modern protocols provide good bounds on clock skew with high probability; the present method depends on the bound for performance but not for correctness.<>
{"title":"Efficient at-most-once messages based on synchronized clocks","authors":"B. Liskov, L. Shrira, J. Wroclawski","doi":"10.1109/WWOS.1989.109271","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109271","url":null,"abstract":"A novel message-passing protocol that guarantees at-most-once message delivery without requiring communication to establish connections, is described. The authors discuss how to use these messages to implement higher level primitives such as at-most-once remote procedure calls (RPC) and describe an implementation of at-most-once RPCs using their method. Performance measurements indicate that at-most-once RPCs can be provided at the same cost as less desirable RPCs that do not guarantee at-most-once execution. The method is based on the assumption that clocks throughout the system are loosely synchronized. Modern protocols provide good bounds on clock skew with high probability; the present method depends on the bound for performance but not for correctness.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"511 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123570063","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109258
R. Alonso, Daniel Barbará, Luis L. Cova
The issues that must be considered in structuring file storage for very large distributed systems are discussed. The authors describe the distributed file system they are developing, which is called FACE (file system for ACE). The first prototype of FACE consists of a series of enhancements to Sun's network file system (NFS) in order to add a stashing capability. User processes interact with the system call interface to perform file and stashing operations. These operations may be invoked directly by user processes or by the FACE user-level routines. The FACE user-level routines implement diverse facilities to allow users to select the files that will be stashed (or dropped from the stash). The first FACE prototype is being implemented on a Sun 3/50 computer running Suri's Unix 4.2 release 3.3.<>
{"title":"A file storage implementation for very large distributed systems","authors":"R. Alonso, Daniel Barbará, Luis L. Cova","doi":"10.1109/WWOS.1989.109258","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109258","url":null,"abstract":"The issues that must be considered in structuring file storage for very large distributed systems are discussed. The authors describe the distributed file system they are developing, which is called FACE (file system for ACE). The first prototype of FACE consists of a series of enhancements to Sun's network file system (NFS) in order to add a stashing capability. User processes interact with the system call interface to perform file and stashing operations. These operations may be invoked directly by user processes or by the FACE user-level routines. The FACE user-level routines implement diverse facilities to allow users to select the files that will be stashed (or dropped from the stash). The first FACE prototype is being implemented on a Sun 3/50 computer running Suri's Unix 4.2 release 3.3.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132741066","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109259
David P. Anderson
The DASH project which is concerned with the logical design of large-scale multimedia systems and in particular, with the design of operating system software for its nodes is discussed. The system requirements include support for multimedia communication (this may require real-time scheduling techniques throughout the system) and a naming and security architecture that scales to global size and that accommodates mutually distrustful groups and subgroups. A prototype distributed system design to address these requirements is being built. The author describes the goals of the DASH project and provides a sketch of the DASH design, with an emphasis on its network communication architecture.<>
{"title":"The workstation as global communication interface","authors":"David P. Anderson","doi":"10.1109/WWOS.1989.109259","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109259","url":null,"abstract":"The DASH project which is concerned with the logical design of large-scale multimedia systems and in particular, with the design of operating system software for its nodes is discussed. The system requirements include support for multimedia communication (this may require real-time scheduling techniques throughout the system) and a naming and security architecture that scales to global size and that accommodates mutually distrustful groups and subgroups. A prototype distributed system design to address these requirements is being built. The author describes the goals of the DASH project and provides a sketch of the DASH design, with an emphasis on its network communication architecture.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134399351","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1989-09-27DOI: 10.1109/WWOS.1989.109267
Andy Hisgen, A. Birrell, T. Mann, M. D. Schroeder, G. Swart
The use of server replication to increase the availability of remote servers in a system of workstations is discussed. Tradeoffs between consistency of replication and caching versus availability are considered for the Echo distributed file system which uses two different replication techniques, one at the upper levels of the hierarchical name space, the name service, and another at the lower levels of the name space, the file volume service. The two replication techniques provide different guarantees of consistency between their replicas and, therefore, different levels of availability. Echo also caches data from the name service and file volume service in client machines (e.g. workstations), with the cache for each service having its own cache consistency guarantee that mimics the guarantee on the consistency of the replicas for that service. The replication and caching consistency guarantees provided by each service are appropriate for its intended use.<>
{"title":"Availability and consistency tradeoffs in the Echo distributed file system","authors":"Andy Hisgen, A. Birrell, T. Mann, M. D. Schroeder, G. Swart","doi":"10.1109/WWOS.1989.109267","DOIUrl":"https://doi.org/10.1109/WWOS.1989.109267","url":null,"abstract":"The use of server replication to increase the availability of remote servers in a system of workstations is discussed. Tradeoffs between consistency of replication and caching versus availability are considered for the Echo distributed file system which uses two different replication techniques, one at the upper levels of the hierarchical name space, the name service, and another at the lower levels of the name space, the file volume service. The two replication techniques provide different guarantees of consistency between their replicas and, therefore, different levels of availability. Echo also caches data from the name service and file volume service in client machines (e.g. workstations), with the cache for each service having its own cache consistency guarantee that mimics the guarantee on the consistency of the replicas for that service. The replication and caching consistency guarantees provided by each service are appropriate for its intended use.<<ETX>>","PeriodicalId":342782,"journal":{"name":"Proceedings of the Second Workshop on Workstation Operating Systems","volume":"107 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1989-09-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123247371","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：