Difference between revisions of "Zfec"
(Created page with "{{Entry |Name=Zfec |Short description=an "erasure code", or "forward error correction code". |Full description=The most widely known example of an erasure code is the RAID-5 algo...") |
(fixing dead links) |
||
| Line 3: | Line 3: | ||
|Short description=an "erasure code", or "forward error correction code". | |Short description=an "erasure code", or "forward error correction code". | ||
|Full description=The most widely known example of an erasure code is the RAID-5 algorithm which makes it so that in the event of the loss of any one hard drive, the stored data can be completely recovered. The algorithm in the zfec package has a similar effect, but instead of recovering from the loss of only a single element, it can be parameterized to choose in advance the number of elements whose loss it can tolerate. This package is largely based on the old "fec" library by Luigi Rizzo et al., which is a mature and optimized implementation of erasure coding. The zfec package makes several changes from the original "fec" package, including addition of the Python API, refactoring of the C API to support zero-copy operation, a few clean-ups and optimizations of the core code itself, and the addition of a command-line tool named "zfec". | |Full description=The most widely known example of an erasure code is the RAID-5 algorithm which makes it so that in the event of the loss of any one hard drive, the stored data can be completely recovered. The algorithm in the zfec package has a similar effect, but instead of recovering from the loss of only a single element, it can be parameterized to choose in advance the number of elements whose loss it can tolerate. This package is largely based on the old "fec" library by Luigi Rizzo et al., which is a mature and optimized implementation of erasure coding. The zfec package makes several changes from the original "fec" package, including addition of the Python API, refactoring of the C API to support zero-copy operation, a few clean-ups and optimizations of the core code itself, and the addition of a command-line tool named "zfec". | ||
| + | |Homepage URL=http://allmydata.org/trac/zfec | ||
|User level=intermediate | |User level=intermediate | ||
| − | |||
| − | |||
| − | |||
|VCS checkout command=darcs get --partial http://allmydata.org/source/zfec/trunk | |VCS checkout command=darcs get --partial http://allmydata.org/source/zfec/trunk | ||
|Computer languages=C,Python | |Computer languages=C,Python | ||
| − | |Documentation note= | + | |Documentation note=https://tahoe-lafs.org/trac/zfec/browser/trunk/README.rst |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Keywords=backup,system administration,archive,backup archive,erasure code,RAID-5 | |Keywords=backup,system administration,archive,backup archive,erasure code,RAID-5 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Version identifier=1.4.4 | |Version identifier=1.4.4 | ||
|Version date=2009-01-05 | |Version date=2009-01-05 | ||
|Version status=stable | |Version status=stable | ||
|Version download=http://pypi.python.org/packages/source/z/zfec/zfec-1.4.4.tar.gz#md5=c7c5d5c1dd634a054bcd36fd01617fe6 | |Version download=http://pypi.python.org/packages/source/z/zfec/zfec-1.4.4.tar.gz#md5=c7c5d5c1dd634a054bcd36fd01617fe6 | ||
| + | |Last review by=Donaldr3 | ||
| + | |Last review date=2016/10/07 | ||
| + | |Submitted by=Database conversion | ||
| + | |Submitted date=2011-04-01 | ||
| + | |Status= | ||
| + | |Is GNU=No | ||
| + | |License verified date=2009-06-08 | ||
| + | }} | ||
| + | {{Project license | ||
| + | |License=GPLv2orlater | ||
| + | |License verified by=Kelly Hopkins | ||
| + | |License verified date=2009-06-08 | ||
| + | }} | ||
| + | {{Project license | ||
| + | |License=BSD_2Clause | ||
| + | |License verified by=Kelly Hopkins | ||
|License verified date=2009-06-08 | |License verified date=2009-06-08 | ||
| − | |||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=Zooko O'Whielacronx | ||
|Role=Maintainer | |Role=Maintainer | ||
| − | |||
|Email=zooko@zooko.com | |Email=zooko@zooko.com | ||
|Resource URL= | |Resource URL= | ||
| Line 49: | Line 52: | ||
|Use=system-administration | |Use=system-administration | ||
}} | }} | ||
| − | {{ | + | {{Featured}} |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | }} | ||
Revision as of 13:01, 7 October 2016
Zfec
http://allmydata.org/trac/zfec
an "erasure code", or "forward error correction code".
The most widely known example of an erasure code is the RAID-5 algorithm which makes it so that in the event of the loss of any one hard drive, the stored data can be completely recovered. The algorithm in the zfec package has a similar effect, but instead of recovering from the loss of only a single element, it can be parameterized to choose in advance the number of elements whose loss it can tolerate. This package is largely based on the old "fec" library by Luigi Rizzo et al., which is a mature and optimized implementation of erasure coding. The zfec package makes several changes from the original "fec" package, including addition of the Python API, refactoring of the C API to support zero-copy operation, a few clean-ups and optimizations of the core code itself, and the addition of a command-line tool named "zfec".
Download
http://pypi.python.org/packages/source/z/zfec/zfec-1.4.4.tar.gz#md5=c7c5d5c1dd634a054bcd36fd01617fe6
Categories
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
| Contact(s) | Role |
|---|---|
| Zooko O'Whielacronx | Maintainer |
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Python (Ref) | https://pypi.org/project/zfec | |
| Debian (Ref) | https://tracker.debian.org/pkg/zfec | |
| Developer | Mailing List Subscribe | http://allmydata.org/cgi-bin/mailman/listinfo/zfec-dev |
Software prerequisites
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.