21 ;;Quote: Helix provide services by registering taskid and descriptive text string with name server; clients can then use LOCATE service primitive

24 ;;Quote: a commit (snapshot) in Helix colors all blocks red; must write them to new addresses

26 ;;Quote: a Helix server provides 96-bit capabilities which encrypt access rights to an object with 40 bits padding

26 ;;Quote: when a Helix server receives an invalid capability, it should report and log the problem

26 ;;Quote: Helix capabilities will not be regenerated in about twenty years

26 ;;Quote: a Helix client collects a set of capabilities needed for a user session

26 ;;Quote: in Helix, clients can only access objects which they create or were given capabilities for

27 ;;Quote: Helix uses two-phase commit and file sets to implement transactions (large-scale atomic actions)

27+ ;;Quote: access lists are stored with an object; difficult to add users since may require modification of many lists

27 ;;Quote: capabilities are stored in user directories; difficult to revoke access rights

27+ ;;Quote: Helix access mode consists of type (read, write) and a lock (copy, original, exclusive);

27 ;;Quote: a Helix object can have one committable instance, i.e., write-original or write-exclusive access mode; other modes allow sharing and concurrency

28+ ;;Quote: if a Helix application program fails, all resources in its file set are released

28 ;;Quote: if a Helix application program succeeds, its file set is committed

28 ;;Quote: Helix allocates disk blocks sequentially from a bit map; write-with-move ensures clustered writes

29 ;;Quote: Helix supported almost 1000 workstations, 50 file servers, and 15 LANs in 1984

29 ;;Quote: commitment works well in Helix; no shut-down command is provided; take down file servers by pressing reset or turning off