@InProceedings{broom:cap,
  author = {Bradley M. Broom and Robert Cohen},
  title = {Acacia: A Distributed, Parallel File System for the {CAP-II}},
  booktitle = {Proceedings of the First Fujitsu-ANU CAP Workshop},
  year = {1990},
  month = {November},
  keywords = {distributed file system, multiprocessor file system, pario-bib},
  comment = {See also broom:acacia, broom:impl, lautenbach:pfs, and
  mutisya:cache. This describes the semantic model for their file system.
  Modelled a lot after Amoeba, they have capabilities that represent immutable
  files. There are create, destroy, read, and write operations, but the read
  and write can affect only part of the file, if desired. They also have an
  atomic ``copy'' operation, which creates a snapshot of the current state of
  the file. They also have ``spawn'' and ``merge'' operations, which are
  essentially begin and end a transaction, a set of changes that are atomically
  merged into the file later. These seem to be addressing issues of concurrency
  more than of parallelism. They also discuss implementation somewhat,
  mentioning the use of distributed caches and log-structured disk layout.
  Prototype in Linda (!).}
}