summaryrefslogtreecommitdiff
path: root/misc/parchive/DESCR
diff options
context:
space:
mode:
authorfredb <fredb>2002-01-04 21:02:30 +0000
committerfredb <fredb>2002-01-04 21:02:30 +0000
commitf46ad2edb82b8f75a96b57080de7c956d24e7a6a (patch)
tree831488981494d8733cebf41a00da05602db39173 /misc/parchive/DESCR
parentc6695af55143e42e47434e65c72ddde1f82152ff (diff)
downloadpkgsrc-f46ad2edb82b8f75a96b57080de7c956d24e7a6a.tar.gz
Initial import of parchive-1.1, an implementation of "Parity Volume Sets",
specification 1.0 (.PAR and .Pnn files). These commonly accompany Usenet binary postings, but the public domain format is sufficiently general to permit other applications as well.
Diffstat (limited to 'misc/parchive/DESCR')
-rw-r--r--misc/parchive/DESCR13
1 files changed, 13 insertions, 0 deletions
diff --git a/misc/parchive/DESCR b/misc/parchive/DESCR
new file mode 100644
index 00000000000..0e1066a80d9
--- /dev/null
+++ b/misc/parchive/DESCR
@@ -0,0 +1,13 @@
+"Parchive" implements a RAID-like system for multi-part archives. Such
+archives are commonly posted to Usenet binary newsgroups. Typically, a
+poster will construct 2 to 5 parity files for a multi-part archive
+consisting of somewhere in the neighborhood of 15 to 50 equal sized parts.
+These parity files contain a Reed-Solomon encoding of the original files.
+He'll then post all of them along with the original parts, so if any number
+of those original parts are lost or corrupted in transit (up to the number
+of parity files), a receiver may reconstruct them from only that number
+of parity files.
+
+Though quickly growing in popularity for it's intended application, the
+format of the parity files is sufficiently general to be useful for other
+applicatons as well. The format itself is in the public domain.