head 1.2; access; symbols pkgsrc-2023Q4:1.2.0.140 pkgsrc-2023Q4-base:1.2 pkgsrc-2023Q3:1.2.0.138 pkgsrc-2023Q3-base:1.2 pkgsrc-2023Q2:1.2.0.136 pkgsrc-2023Q2-base:1.2 pkgsrc-2023Q1:1.2.0.134 pkgsrc-2023Q1-base:1.2 pkgsrc-2022Q4:1.2.0.132 pkgsrc-2022Q4-base:1.2 pkgsrc-2022Q3:1.2.0.130 pkgsrc-2022Q3-base:1.2 pkgsrc-2022Q2:1.2.0.128 pkgsrc-2022Q2-base:1.2 pkgsrc-2022Q1:1.2.0.126 pkgsrc-2022Q1-base:1.2 pkgsrc-2021Q4:1.2.0.124 pkgsrc-2021Q4-base:1.2 pkgsrc-2021Q3:1.2.0.122 pkgsrc-2021Q3-base:1.2 pkgsrc-2021Q2:1.2.0.120 pkgsrc-2021Q2-base:1.2 pkgsrc-2021Q1:1.2.0.118 pkgsrc-2021Q1-base:1.2 pkgsrc-2020Q4:1.2.0.116 pkgsrc-2020Q4-base:1.2 pkgsrc-2020Q3:1.2.0.114 pkgsrc-2020Q3-base:1.2 pkgsrc-2020Q2:1.2.0.110 pkgsrc-2020Q2-base:1.2 pkgsrc-2020Q1:1.2.0.90 pkgsrc-2020Q1-base:1.2 pkgsrc-2019Q4:1.2.0.112 pkgsrc-2019Q4-base:1.2 pkgsrc-2019Q3:1.2.0.108 pkgsrc-2019Q3-base:1.2 pkgsrc-2019Q2:1.2.0.106 pkgsrc-2019Q2-base:1.2 pkgsrc-2019Q1:1.2.0.104 pkgsrc-2019Q1-base:1.2 pkgsrc-2018Q4:1.2.0.102 pkgsrc-2018Q4-base:1.2 pkgsrc-2018Q3:1.2.0.100 pkgsrc-2018Q3-base:1.2 pkgsrc-2018Q2:1.2.0.98 pkgsrc-2018Q2-base:1.2 pkgsrc-2018Q1:1.2.0.96 pkgsrc-2018Q1-base:1.2 pkgsrc-2017Q4:1.2.0.94 pkgsrc-2017Q4-base:1.2 pkgsrc-2017Q3:1.2.0.92 pkgsrc-2017Q3-base:1.2 pkgsrc-2017Q2:1.2.0.88 pkgsrc-2017Q2-base:1.2 pkgsrc-2017Q1:1.2.0.86 pkgsrc-2017Q1-base:1.2 pkgsrc-2016Q4:1.2.0.84 pkgsrc-2016Q4-base:1.2 pkgsrc-2016Q3:1.2.0.82 pkgsrc-2016Q3-base:1.2 pkgsrc-2016Q2:1.2.0.80 pkgsrc-2016Q2-base:1.2 pkgsrc-2016Q1:1.2.0.78 pkgsrc-2016Q1-base:1.2 pkgsrc-2015Q4:1.2.0.76 pkgsrc-2015Q4-base:1.2 pkgsrc-2015Q3:1.2.0.74 pkgsrc-2015Q3-base:1.2 pkgsrc-2015Q2:1.2.0.72 pkgsrc-2015Q2-base:1.2 pkgsrc-2015Q1:1.2.0.70 pkgsrc-2015Q1-base:1.2 pkgsrc-2014Q4:1.2.0.68 pkgsrc-2014Q4-base:1.2 pkgsrc-2014Q3:1.2.0.66 pkgsrc-2014Q3-base:1.2 pkgsrc-2014Q2:1.2.0.64 pkgsrc-2014Q2-base:1.2 pkgsrc-2014Q1:1.2.0.62 pkgsrc-2014Q1-base:1.2 pkgsrc-2013Q4:1.2.0.60 pkgsrc-2013Q4-base:1.2 pkgsrc-2013Q3:1.2.0.58 pkgsrc-2013Q3-base:1.2 pkgsrc-2013Q2:1.2.0.56 pkgsrc-2013Q2-base:1.2 pkgsrc-2013Q1:1.2.0.54 pkgsrc-2013Q1-base:1.2 pkgsrc-2012Q4:1.2.0.52 pkgsrc-2012Q4-base:1.2 pkgsrc-2012Q3:1.2.0.50 pkgsrc-2012Q3-base:1.2 pkgsrc-2012Q2:1.2.0.48 pkgsrc-2012Q2-base:1.2 pkgsrc-2012Q1:1.2.0.46 pkgsrc-2012Q1-base:1.2 pkgsrc-2011Q4:1.2.0.44 pkgsrc-2011Q4-base:1.2 pkgsrc-2011Q3:1.2.0.42 pkgsrc-2011Q3-base:1.2 pkgsrc-2011Q2:1.2.0.40 pkgsrc-2011Q2-base:1.2 pkgsrc-2011Q1:1.2.0.38 pkgsrc-2011Q1-base:1.2 pkgsrc-2010Q4:1.2.0.36 pkgsrc-2010Q4-base:1.2 pkgsrc-2010Q3:1.2.0.34 pkgsrc-2010Q3-base:1.2 pkgsrc-2010Q2:1.2.0.32 pkgsrc-2010Q2-base:1.2 pkgsrc-2010Q1:1.2.0.30 pkgsrc-2010Q1-base:1.2 pkgsrc-2009Q4:1.2.0.28 pkgsrc-2009Q4-base:1.2 pkgsrc-2009Q3:1.2.0.26 pkgsrc-2009Q3-base:1.2 pkgsrc-2009Q2:1.2.0.24 pkgsrc-2009Q2-base:1.2 pkgsrc-2009Q1:1.2.0.22 pkgsrc-2009Q1-base:1.2 pkgsrc-2008Q4:1.2.0.20 pkgsrc-2008Q4-base:1.2 pkgsrc-2008Q3:1.2.0.18 pkgsrc-2008Q3-base:1.2 cube-native-xorg:1.2.0.16 cube-native-xorg-base:1.2 pkgsrc-2008Q2:1.2.0.14 pkgsrc-2008Q2-base:1.2 cwrapper:1.2.0.12 pkgsrc-2008Q1:1.2.0.10 pkgsrc-2008Q1-base:1.2 pkgsrc-2007Q4:1.2.0.8 pkgsrc-2007Q4-base:1.2 pkgsrc-2007Q3:1.2.0.6 pkgsrc-2007Q3-base:1.2 pkgsrc-2007Q2:1.2.0.4 pkgsrc-2007Q2-base:1.2 pkgsrc-2007Q1:1.2.0.2 pkgsrc-2007Q1-base:1.2 pkgsrc-base:1.1.1.1 TNF:1.1.1; locks; strict; comment @# @; 1.2 date 2007.02.21.06.08.30; author wiz; state Exp; branches; next 1.1; 1.1 date 2007.02.20.23.00.08; author xtraeme; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2007.02.20.23.00.08; author xtraeme; state Exp; branches; next ; desc @@ 1.2 log @aspell. @ text @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 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 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 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 algorithms. @ 1.1 log @Initial revision @ text @d1 1 a1 1 LZOlayer Filesystem is a filesystem which allows you to use transparently d6 1 a6 1 divided into blocks, which can be decompressed separetly. In other words, d8 1 a8 1 sized 5,000,000 bytes, it only decompresses a block which constain wanted d13 1 a13 1 LZOlayer FileSystem was meant to support only LZO compression algorythm, d16 1 a16 1 compression algorythms. @ 1.1.1.1 log @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. @ text @@