diff -r pario/web/bibtex/krieger:hfs3.bib pario/web/new/krieger:hfs3.bib
7c7,10
<   note = {To appear},
---
>   month = {August},
>   volume = {15},
>   number = {3},
>   pages = {286--321},
9,10c12,14
<   keyword = {verify and update abstract, parallel I/O, parallel file system,
<   object-oriented, pario-bib},
---
>   URL =
>   {http://www.acm.org/pubs/citations/journals/tocs/1997-15-3/p286-krieger/},
>   keyword = {parallel I/O, parallel file system, object-oriented, pario-bib},
12c16
<   large-scale) shared memory multiprocessors. Its architecture is based on the
---
>   large-scale) shared-memory multiprocessors. Its architecture is based on the
15c19
<   structures, file system policies and I/O interfaces. Files in HFS are
---
>   structures, file system policies, and I/O interfaces. Files in HFS are
20,29c24,33
<   optimized for concurrent random-access write-only operations by ten
<   processes, something no other file system can do. Similarly, the prefetching,
<   locking, and file cache management policies can all be chosen to match an
<   application's access pattern. In contrast, most existing parallel file
<   systems support a single file structure and a small set of policies. \par We
<   have implemented HFS as part of the Hurricane operating system running on the
<   Hector shared memory multiprocessor. We demonstrate that the flexibility of
<   HFS comes with little processing or I/O overhead. We also show that for a
<   number of file access patterns HFS is able to deliver to the applications the
<   full I/O bandwidth of the disks on our system.}
---
>   optimized for concurrent random-access write-only operations by 10 threads,
>   something no other file system can do. Similarly, the prefetching, locking,
>   and file cache management policies can all be chosen to match an
>   application's access pattern. In contrast, most parallel file systems support
>   a single file structure and a small set of policies. We have implemented HFS
>   as part of the Hurricane operating system running on the Hector shared-memory
>   multiprocessor. We demonstrate that the flexibility of HFS comes with little
>   processing or I/O overhead. We also show that for a number of file access
>   patterns, HFS is able to deliver to the applications the full I/O bandwidth
>   of the disks on our system.}