| 
|
QuoteRef: dorwSM1_1997
topics >
all references >
ThesaHelp:
references c-d
Topic:
file directory
Topic:
uniform reference to data
Topic:
hierarchical naming
Topic:
examples of file systems
Topic:
implementing distributed systems and applications
Topic:
communication protocols
Topic:
operating system kernel
Topic:
device driver
Topic:
remote procedure call
Topic:
synchronous communication through a channel
Topic:
synchronized processing
Topic:
process threads
Topic:
waitfor condition in parallel processing
Topic:
non-deterministic processing
Topic:
object code linkers and loaders
Topic:
deployable module or assembly
Topic:
intermediate representation of code
Topic:
interpreter
Topic:
load-time code generation
Topic:
operating system security
Topic:
security by seal
Topic:
initialization of data
Topic:
notation for declarations
Topic:
declaration through use
Topic:
separate a module's interface specification from its implementation
Topic:
interface between program modules
Topic:
sub-sequences
Topic:
attribute-value pairs as information
Topic:
failure returning functions and expressions
Topic:
tuples
Topic:
global declarations and variables
Topic:
defining a process
Topic:
managing shared memory
Topic:
user interface tool kits
Topic:
scripting language
Topic:
minimal language systems
Topic:
memory management by reference counting
Topic:
memory management by garbage collection
Group:
operating system
Topic:
software portability
Reference
Dorward, S.M., Pike, R., Presotto, D.L., Ritchie, D.M., Trickey, H.W., Winterbottom, P., , "The Inferno operating system", Bell Labs Technical Journal, 2, 1, pp. 5-18, Winter 1997. Google
7 ;;Quote: in Inferno and Plan 9, all resources have a hierarchical file name in a forest of file systems and in a private name space
7+;;Quote: the Styx communication protocol unifies local and remote resources
7 ;;Quote: Inferno applications use a fixed set of files for devices and system services
7+;;Quote: represent device drivers with a data file and a control file
7 ;;Quote: the Styx protocol implements local device drivers with procedure calls and remote devices with mount driver and remote procedure calls
8 ;;Quote: Limbo uses a channel to connect local and remote tasks; synchronous communication of any data structure
8+;;Quote: a channel may connect a local or remote task or file; implements communicating sequential processes
8 ;;Quote: Limbo includes multi-tasking with task initiation and coordination via the 'alt' statement
8+;;Quote: use 'alt' to randomly select an enabled block of statements for a communication expression
8 ;;Quote: Limbo programs load modules explicitly: simplifies garbage collection, provides better control, allows multiple implementations
8+;;Quote: the 'load' operator takes a module type and the filename of an implementation. It checks that the implementation matches the type
8 ;;Quote: Limbo programs are byte codes for the Dis virtual machine with garbage collection and task scheduling
8+;;Quote: Dis is a three-address machine similar to modern processors; on-the-fly compiler, internal format
9 ;;Quote: for security, Inferno provides message digests, encrypted channels, authenticated file names, and signed modules; based on CryptoLib
12 ;;Quote: provide implicit typing for initialized type declarations
14 ;;Quote: a Limbo program can load different implementations of a module; e.g., load a GIF implementation of an image file
14 ;;Quote: use 's[a:b]' for a slice or substring
15 ;;Quote: use '(a, b)' for a tuple or pair of values; used for multiple return values, error returns, simple data structures
15 ;;Quote: use 'spawn f(a, b)' to create a new process with shared, unsynchronized, global variables
15 ;;Quote: use strings and a mini language to control the graphics interface; e.g., Tk/Tcl or Limbo
17 ;;Quote: manage memory with reference counting and a sweep algorithm for circular structures; provides benefits of garbage collection at low cost
17 ;;Quote: Inferno provides a complete operating system with identical, distributed applications on a wide variety of machines
ThesaHelp: references c-d (337 items)
Topic: file directory (42 items)
Topic: uniform reference to data (34 items)
Topic: hierarchical naming (28 items)
Topic: examples of file systems (44 items)
Topic: implementing distributed systems and applications (41 items)
Topic: communication protocols (61 items)
Topic: operating system kernel (67 items)
Topic: device driver (15 items)
Topic: remote procedure call (44 items)
Topic: synchronous communication through a channel (28 items)
Topic: synchronized processing (35 items)
Topic: process threads (25 items)
Topic: waitfor condition in parallel processing (20 items)
Topic: non-deterministic processing (19 items)
Topic: object code linkers and loaders (29 items)
Topic: deployable module or assembly (10 items)
Topic: intermediate representation of code (29 items)
Topic: interpreter (59 items)
Topic: load-time code generation (13 items)
Topic: operating system security (17 items)
Topic: security by seal (16 items)
Topic: initialization of data (42 items)
Topic: notation for declarations (20 items)
Topic: declaration through use (4 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: interface between program modules (55 items)
Topic: sub-sequences (13 items)
Topic: attribute-value pairs as information (53 items)
Topic: failure returning functions and expressions (24 items)
Topic: tuples (17 items)
Topic: global declarations and variables (33 items)
Topic: defining a process (20 items)
Topic: managing shared memory (74 items)
Topic: user interface tool kits (31 items)
Topic: scripting language (27 items)
Topic: minimal language systems (12 items)
Topic: memory management by reference counting (22 items)
Topic: memory management by garbage collection (113 items)
Group: operating system (27 topics, 877 quotes)
Topic: software portability (43 items)