summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-07-24 22:19:56 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-07-24 22:19:56 +0000
commitc82fd9a87b673d62605f79ae96b69c8015d4e86a (patch)
treeef04ac7ee54ca038528ae073fb2be7bd95e400d8
parent43eb24837af59620be921000a455aac08c80bb74 (diff)
* Add reference to BAARF to README.Debian and included the RAID5 vs RAID10
article from the BAARF website.
-rw-r--r--debian/README.Debian7
-rw-r--r--debian/changelog5
-rwxr-xr-xdebian/patches/99-raid5-vs-raid10-doc.dpatch16
3 files changed, 21 insertions, 7 deletions
diff --git a/debian/README.Debian b/debian/README.Debian
index 3cede48b..c0831b8c 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -32,6 +32,13 @@ Common recipes
Check /usr/share/doc/mdadm/README.recipes.gz for some simple examples of how
to do the most common stuff with mdadm.
+RAID5 or not to RAID5
+~~~~~~~~~~~~~~~~~~~~~
+See http://www.miracleas.com/BAARF/BAARF2.html . The package maintainer could
+not possibly come up with so much emotion over such a technical topic.
+
+See also the RAID5_versus_RAID10.txt.gz document included with this package.
+
Upstream
~~~~~~~~
For completeness: The upstream repository is available from
diff --git a/debian/changelog b/debian/changelog
index 6b181912..61deb244 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,12 +9,13 @@ mdadm (2.5.2-8) unstable; urgency=low
* Removed the code writing auto-detected devices to /var, which was silly
since /var isn't necessarily mounted yet by the time mdadm-raid is called.
Thanks to Mau for pointing this out.
- * Added questionable RAID5-vs-RAID10.txt document.
+ * Add reference to BAARF to README.Debian and included the RAID5 vs RAID10
+ article from the BAARF website.
* Updated debconf translations:
- Japanese by Hideki Yamane, thanks!
- French by Florentin Duneau, thanks! (closes: #379511)
- -- martin f. krafft <madduck@debian.org> Mon, 24 Jul 2006 23:07:33 +0100
+ -- martin f. krafft <madduck@debian.org> Mon, 24 Jul 2006 23:14:29 +0100
mdadm (2.5.2-7) unstable; urgency=low
diff --git a/debian/patches/99-raid5-vs-raid10-doc.dpatch b/debian/patches/99-raid5-vs-raid10-doc.dpatch
index 8ce253de..d3de418f 100755
--- a/debian/patches/99-raid5-vs-raid10-doc.dpatch
+++ b/debian/patches/99-raid5-vs-raid10-doc.dpatch
@@ -7,13 +7,19 @@
@DPATCH@
diff -urNad trunk~/RAID5_versus_RAID10.txt trunk/RAID5_versus_RAID10.txt
--- trunk~/RAID5_versus_RAID10.txt 1970-01-01 01:00:00.000000000 +0100
-+++ trunk/RAID5_versus_RAID10.txt 2006-07-24 23:06:52.373326792 +0100
-@@ -0,0 +1,171 @@
++++ trunk/RAID5_versus_RAID10.txt 2006-07-24 23:18:32.250326974 +0100
+@@ -0,0 +1,177 @@
+# from http://www.miracleas.com/BAARF/RAID5_versus_RAID10.txt
++# also see http://www.miracleas.com/BAARF/BAARF2.html
+#
-+# note: I, the Debian maintainer, do not agree with much of what's written
-+# here, but it's a good argument the author is putting forth. In the end, the
-+# RAID level you choose depends on your needs only.
++# Note: I, the Debian maintainer, do not agree with some of the arguments,
++# especially not with the total condemning of RAID5. Anyone who talks about
++# data loss and blames the RAID system should spend time reading up on Backups
++# instead of trying to evangelise, but that's only my opinion. RAID5 has its
++# merits and its shortcomings, just like any other method. However, the author
++# of this argument puts forth a good case and thus I am including the
++# document. Remember that you're the only one that can decide which RAID level
++# to use.
+#
+
+RAID5 versus RAID10 (or even RAID3 or RAID4)