Next | Query returned 16 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2008-03-03 20:31:31 by Johnny C. Lam | Files touched by this commit (7)
Log message:
Mechanical changes to add DESTDIR support to packages that install
their files via a custom do-install target.
   2007-03-16 09:21:16 by Antti Kantee | Files touched by this commit (2)
Log message:
use open() instead of mknod() to create regular files.  avoids having
to run the file server as root for most uses.
   2007-03-15 23:55:21 by Alistair G. Crooks | Files touched by this commit (6)
Log message:
Fix up CATEGORIES for filesystem
   2007-03-08 06:14:38 by Antti Kantee | Files touched by this commit (2)
Log message:
make pwd work
   2007-02-21 07:08:30 by Thomas Klausner | Files touched by this commit (4)
Log message:
aspell.
   2007-02-21 00:00:08 by Juan Romero Pardines | Files touched by this commit (6) | Imported package
Log message:
Initial import of fuse-lzofs-20060306.

LZOlayer Filesystem is a filesystem 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,
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
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,
because it has extremely low compression/decompression time. However,
currently it supports LZO and ZLIB (but only one at the run-time!)
compression algorythms.


Next | Query returned 16 messages, browsing 11 to 20 | previous