K. Thompson R. Pike et al. Plan 9 from bell labs. Computing Systems, Vol 8(3):221--254, Summer 1995. 12  Home/Search   Document Details and Download   Summary   Related Articles   Check

....le systems. All existing solutions provide a global view of the le system at the cost of decreasing reliability (all le servers must be up for any le to be accessible) and or increasing interdependence (the le servers must be up for the cluster to be up) We are currently implementing a Plan 9 [9] style Private Name Spaces le system for our clusters called V9FS [6, 7] Private Name Spaces decouple les from the le system; users have access to les (Name Spaces) and not the entire le system that the les live on. In addition to bene ts with respect to security, Private Name Spaces ....

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221-254, 1995.

....all requiring some form of timely behaviour. Embedded system are controlled by computer systems running general purpose operating systems when possible or real time operating systems when needed. In this article we describe the metamorphosis of the general purpose operating system Plan 9 [6] to a real time operating system. Although other operating systems may also have real time support, we believe there are only few general purpose operating systems with a comparable native support for real time (RT) applications. This research is sponsored by the IBM Equinox Grant. Plan 9 is ....

Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221-- 254, Summer 1995.

....notion of support for group communications. Their behaviour with more than one sender or receiver is undefined and may be erratic. 3 specific communications resource, independent of endpoints. This decoupling provides a new degree of flexibility to concurrent applications. 2.1. 2 Plan 9 Plan 9 [28] is an operating system developed at AT T Bell Labs. The system carries the notion of named pipes further by treating every resource in the system as a file. All communication channels, including TCP streams, appear as files in the local file system. This is similar to the perspective presented by ....

R. Pike, D.L. Presotto, K. Thompson, and H. Trickey. Plan 9 from Bell Labs. In Proceedings of USENIX, 1990.

....in modules. Di#erent tasks communicate through channels that are supported by the Inferno kernel, which provide a facility for exchanging typed data. Inferno s security model protects the security of communication and provides control over logical resources accessible to a task. As in PLAN 9 [60], all resources in Inferno are named and accessed as files in multiple hierarchical file systems. These file systems are mapped into a hierarchical namespace that is private to each task. A communication protocol called Styx is used to access these resources in a uniform fashion. By restricting ....

Pike, R., Presotto, D., Dorward, S., Flandrena, B., Thompson, K., Trickey, H., and Winterbottom, P. Plan 9 from Bell Labs. Computing Systems 8, 3 (Summer 1995), 221--254.

....tertiary storage: all of the updates that are made throughout the day are copied to, for example, a CD. The backups can be made available in the best effort file system s secondary storage name space to allow users to access old files by themselves, much like the Plan 9 tertiary storage facilities [77]. Continuousmedia files are stored on tertiary storage once they are not used frequently anymore to free up expensive secondary storage. Playback from tertiary storage is usually still possible by either caching the data on secondary storage again (promotion of data [104] or by directly sending ....

....the last backup contain a pointer to the last backup of the file or directory. The backup itself is then made available again for clients. The backup utility itself does not yet exist for Clockwise and the backup mechanism itself is not new: Plan 9 from Bell Labs uses a similar backup approach [77]. Current disk technology can, when it is used in parallel, easily outperform current (PC) architectures. A single Quantum Atlas II disk, for example, outperforms a Fast SCSI 2 bus and three Seagate Cheetahs outperform Ultra Wide SCSI bus. Also, when more than six Seagate Cheetahs are used that ....

Rob Pike, Dave Presotto, Ken Thompson, and Howard Trickey. Plan 9 from Bell Labs. Proceedings of Summer UKUUG Conference, pages 1--9, July 1990.

....and close up security holes, while each pod maintains its own configuration, allowing pods to point to log files and web pages anywhere on their file system. In addition to network accessible files and private pod files, Zap must also consider special file systems such as the proc file system [27] in proo and devices in d, We briefly discuss proc here and defer devices to Section 4.4. Each pod is given its own proc by creating a special per pod directory, specifically proc zap pods pod id proc, under the proc file system of the host machine and loopback mounting that area as proc in ....

R. Pike, D. Presotto, K. Thompson, and H. Trickey, Plan 9 from Bell Labs, Proceedings of the Summer 1990.

....area networks to world wide internetworks the logistics of discovering resources of interest have become correspondingly more complex. The growing complexity of finding information information in one such large network, the Internet, has motivated a wide variety of new tools for naming support [2, 7, 9, 4]. For example, the Archie system [1] provides an on line index of the files that are available at over 200 public FTP sites. The Alex system [3] provides a uniform naming system along with caching services that span all of the hosts in the Internet, and interoperates with an underlying file system ....

R. Pike, D. Presotto, K. Thompson, and H. Trickey. Plan 9 from Bell Labs. In Proceeding of UI( UUG, 1990.

....interface it o ers, means that there is less need for something like a FiST translator to provide vnode like code translation for the HURD. Nevertheless, the HURD o ers an interface that is comparable to the vnode one and more. 6. 2 Plan 9 Plan 9 was developed at Bell Labs in the late 1980 s [Pike90, Pike91, Presotto93]. The Plan 9 approach to le system extension is similar to that of Unix. The Plan 9 mount system call provides a le descriptor that can be a user process or remote le server. After a successful mount, operations below the mount point are sent to the le server. Plan 9 s equivalent of the vnode ....

R. Pike, D. Presotto, K. Thompson, and H. Trickey. Plan 9 from Bell Labs. Proceedings of Summer UKUUG Conference, pages 1-9, July 1990.

....tool, which reads a textual input file and produces PostScript output. A web interface (written using ca. 350 lines of PHP code) is also available at http: wwwes.cs.utwente.nl feas and produces PostScript and PDF output. Current work The RTT protocol is currently working under RT Plan 9 [8], RT Linux [10] and LinuxRTAI [9] Because the implementation of the protocol itself as well as the feasibility analysis is straight forward, we also use the protocol for the RT communication in the network of the At Home Anywhere project. RTT is also a good candidate for our video server ....

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, P. Winterbottom, Plan 9 from Bell Labs, Computing Systems, 8(3):221--254, 1995, http: //www.cs.bell-labs.com/sys/doc/

....to the specific needs of the HRS. These tools include hardware performance counters such as those available on Pentium processors [14] standard system calls [15] the performance monitoring objects available in Windows based systems [16] and the proc file system available in Unix based systems [17, 18], all of which can be readily accessed in user level programs. To further reduce the increase in load due to server load monitoring, one needs to adopt randomized sampling approaches that balance the processing expense against the algorithm s accuracy. The main decision parameter is selecting an ....

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from bell labs. Computing Systems, 8(3), 1995.

No context found.

R. Pike, D. Presotto, K. Thompson, H. Trickey, ##Plan 9 from Bell Labs##, UKUUG Proc. of the Summer 1990 Conf., London, England, 1990.

No context found.

K. Thompson R. Pike et al. Plan 9 from bell labs. Computing Systems, Vol 8(3):221--254, Summer 1995. 12

No context found.

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

R. Pike, D. Presotto, K. Thompson and H. Trickey, Plan 9 from Bell Labs, EUUG Newsletter 10, 3 (Autumn 1990), 2-11.

No context found.

Rob Pike, Dave Presotto, Ken Thompson, and Howard Trickey. Plan 9 from Bell Labs. In Proceedings of the UKUUG Summer Conference, London, England, 1990.

No context found.

Rob Pike, Dave Presotto, Ken Thompson, and Howard Trickey. Plan 9 from Bell Labs. In Proceedings of the Summer 1990 UKUUG Conference, pages 1--9, London, England, July 1990.

No context found.

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

Rob Pike, Dave Presotto, Ken Thompson, and Howard Trickey. Plan 9 from Bell Labs. In Proceedings of the UKUUG Summer Conference, London, England, 1990.

No context found.

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221--254, Summer 1995.

No context found.

R. Pike, D. Presotto, K. Thompson, and H. Trickey. Plan 9 From Bell Labs. In Proc. of the Summer UKUUG Conference, 1990.

No context found.

Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson, Howard Trickey, and Phil Winterbottom. Plan 9 from Bell Labs. Computing Systems, 8(3):221-254, 1995.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC