summaryrefslogtreecommitdiff
path: root/filesystems/fuse-lzofs
diff options
context:
space:
mode:
authorwiz <wiz@pkgsrc.org>2007-02-21 06:08:30 +0000
committerwiz <wiz@pkgsrc.org>2007-02-21 06:08:30 +0000
commitd1304464bb83bddbdedc2bd48229f0c82438416e (patch)
treeb3feea565b915ebcab4f35c63575ae81200d52be /filesystems/fuse-lzofs
parentb9211a69aa810a6ae1a14aa55aa62bb8df64b196 (diff)
downloadpkgsrc-d1304464bb83bddbdedc2bd48229f0c82438416e.tar.gz
aspell.
Diffstat (limited to 'filesystems/fuse-lzofs')
-rw-r--r--filesystems/fuse-lzofs/DESCR10
1 files changed, 5 insertions, 5 deletions
diff --git a/filesystems/fuse-lzofs/DESCR b/filesystems/fuse-lzofs/DESCR
index fe56c45324f..c3145899e15 100644
--- a/filesystems/fuse-lzofs/DESCR
+++ b/filesystems/fuse-lzofs/DESCR
@@ -1,16 +1,16 @@
-LZOlayer Filesystem is a filesystem which allows you to use transparently
+LZOlayer File System is a file system which allows you to use transparently
compressed files, just as they would be normal files.
Both read and write operations are possible, along with other most common
system calls. It consumes little memory in my opinion, because files are
-divided into blocks, which can be decompressed separetly. In other words,
+divided into blocks, which can be decompressed separately. In other words,
if you (or an application) would like to read byte 4,500,000 in a file
-sized 5,000,000 bytes, it only decompresses a block which constain wanted
+sized 5,000,000 bytes, it only decompresses a block which contain wanted
data. Write operation is based on a packet gathering and after reaching its
limit it 'syncs' the data. It allows it's user to write/modify files pretty
fast, despite the fact it's block divided.
-LZOlayer FileSystem was meant to support only LZO compression algorythm,
+LZOlayer File System was meant to support only LZO compression algorithm,
because it has extremely low compression/decompression time. However,
currently it supports LZO and ZLIB (but only one at the run-time!)
-compression algorythms.
+compression algorithms.