Lines Matching refs:system
37 First, the operating system they run, UNIX, is itself an old timesharing system and
49 an old timesharing operating system to run those personal machines
53 ways: to build a system that was centrally administered and cost-effective
55 The idea was to build a time-sharing system out of workstations, but in a novel way.
64 not a system out of a lot of little UNIXes.
67 brought along. The best was its use of the file system to coordinate
73 system that lets people and their computing agents build customized views
80 and file-system-like resources were extended throughout
81 the system\(emto processes, graphics, even the network itself.
83 By 1989 the system had become solid enough
97 The distinction between operating system, library, and application
98 is important to the operating system researcher but uninteresting to the
100 By building a complete new system,
103 system.
107 Most important, though, the test of a system is the computing
112 the architecture of the underlying system encourage a more effective way of working.
114 running POSIX commands, it is a backwater of the system.
116 of system software is developed in the `native' Plan 9 environment.
118 There are benefits to having an all-new system.
121 we want a system that is available in source form
126 C compilers for our system, but even had we overcome the problems with
130 This paper serves as an overview of the system. It discusses the architecture
138 The view of the system is built upon three principles.
139 First, resources are named and accessed like files in a hierarchical file system.
184 When someone uses the system, though,
187 one's view of the system provided by the software.
227 hierarchy of the file system provided by the server.
229 the client's name space is held by the client system alone, not on or with the server,
233 A paper by Welch compares Sprite, NFS, and Plan 9's network file system structures [Welc94].
240 the window system,
243 One example is the process file system,
249 The file system model is well-understood, both by system builders and general users,
256 so services built this way are ready-made for a distributed system.
264 the window system.
266 the bare system is rudimentary, but once the window system, 8½ [Pike91],
283 to substitute files from the dump file system when debugging.
303 that is not the style of the system.
318 system and text editor on the terminal and to run computation- or file-intensive
352 Compatibility was not a requirement for the system.
360 The server is a stand-alone system, accessible only over the network,
383 The addressable data in the file system can be larger than the size of the
392 of the file system occurs automatically.
393 The file system is frozen and
399 file system appears in a
403 is the root directory of an image of the file system
408 There are two ways the dump file system is used.
410 dump file system directly or attach pieces of
422 There is no backup system as such;
434 The other (very rare) use is complete system backup.
436 the active file system can be initialized from any dump by clearing the
438 the active file system to be a copy
442 results in a very slow system.
445 The file system takes a few days to reload the working
452 The dump file system is read-only, though,
483 Perhaps the most remarkable file server in Plan 9 is 8½, the window system.
596 translating 9P requests into system calls to the Plan 9 kernel.
639 the terminal's window system) visible in the server's
654 which does nothing to reproduce the local name space on the remote system,
663 to start a window system in a window running a
671 A single laptop PC can function as a stand-alone Plan 9 system;
677 The system software is portable and the same
678 operating system runs on all hardware.
679 Except for performance, the appearance of the system on, say,
685 a user could sit in front of any machine and see the same system. In the modern
689 although the system itself can be used this way.
695 In fact, one server is the main server, holding all system files; other servers provide
696 extra storage or are available for debugging and other special uses, but the system
713 need to manage a distributed naming system or keep parallel files up to date.
723 the automated dump file system frees all users from the need to maintain
753 from our research UNIX system [UNIX85].
766 Each system library has an associated header file, declaring all
797 in the system are in low-level routines in the graphics library.
876 several architectures: perhaps the window system running on
878 resident on a SPARC system.
901 through a file system interface,
903 For example, the system clock is represented by a decimal number in the file
909 system call) reads the file and converts it to binary.
917 file system associated with each process.
1007 a simple process model and a few carefully designed system calls for
1020 feasible approach in Plan 9 because the kernel has an efficient system
1030 system call.
1065 A system with just two types of processes\(emregular processes and threads\(emcould
1077 system call; such a segment
1082 system call provides a way for processes to synchronize.
1109 system call.
1111 A Plan 9 process in a system call will block regardless of its `weight'.
1136 system call:
1159 careful operating system support can reduce the difficulty of writing
1165 User processes construct name spaces using three system calls:
1172 system call attaches a tree served by a file server to
1184 system call, on the other hand, duplicates some piece of existing name space at
1188 system call allows components to be removed.
1229 system call applied to an existing file succeeds normally.
1274 system call; its
1296 system call: in Plan 9, devices are controlled by textual messages,
1302 distributed system.
1317 All operations on files supply a fid to identify an object in the remote file system.
1321 a file system hierarchy, copy fids, perform I/O, change file attributes,
1343 message moves a fid through a single level of the file system hierarchy.
1387 A system call such as
1405 The mount driver is the sole RPC mechanism employed by the system.
1581 is a file system mounted in a known place.
1637 the system assumes that each read from a communication channel will
1783 It disconnects guest users from system programs, such as the contents of
1836 group traditionally has all the system programmers,
1837 and system files are accessible
1880 is the dump file system, which is not only served by the same file
1883 file system;
1886 and read-protected, once it is in the dump file system it is still owned by
1889 Also, since the dump file system is immutable, the file cannot be changed;
1904 so the only variables are the operating system and libraries.
1911 a trivial system call
1948 the system's novelty lies in the pieces outside the kernel and the way they interact.
1950 of the system together, solving problems where the solution fit best.
1967 of the system;
1972 influence on the system [Nee89].
1976 while naming everything like a file makes the system easy to understand, even for
1978 Consider the dump file system, which is trivial to use for anyone familiar with
1984 with any other part of the system to build unusual applications;
1996 Converting every resource in the system into a file system is a kind of metaphor,
2034 (It was exploited, however, in the research UNIX system for which
2044 and weaker portability of the file system code.
2046 as a variant of the regular operating system, with no user processes and
2049 Another improvement to the file system would be a change of internal structure.
2051 it holds the metadata of the file system, it must be present in order to serve files.
2052 The system could be restructured so the WORM is a backup device only, with the
2053 file system proper residing on magnetic disks.
2069 It has matured into the system that supports our research,
2075 Attention is now focusing on using the system to build distributed applications.
2078 Active use forces us to address shortcomings as they arise and to adapt the system