summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html10
1 files changed, 10 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html b/zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html
new file mode 100644
index 000000000..938f25325
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html
@@ -0,0 +1,10 @@
+<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 5, 2013 at 11:11 AM, Colin Guthrie <span dir="ltr">&lt;<a href="mailto:mageia@colin.guthr.ie" target="_blank">mageia@colin.guthr.ie</a>&gt;</span> wrote:<br>
+<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Anything that relies on ordering is just broken by design. We need to<br>
+handle things gracefully regardless of the order they are detected. This<br>
+is why UUIDs are the defacto method for filesystem identification these<br>
+days and why in mga4 we&#39;ll likely switch to a consistent naming scheme<br>
+for networking devices too.<br></blockquote><div><br>Yes, I understand that cryptic-looking UUIDs are the defacto identifiers but when mdadm reports that /dev/sdf1 has failed in a parity RAID
+setup, it will be good if a mere mortal can know which drive to replace. :o)<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
+Also &quot;modprobe ordering&quot; is increasingly not true either as many modules<br>
+are automatically loaded when the hardware is present.<span class=""><font color="#888888"><br></font></span></blockquote><div><br></div><div>Yes, but it is possible to override the automatic loading...which is why I like the modular approach.<br>
+<br></div><div>Now that I understand the reasons for going back to statically compiled drivers, I&#39;m OK with rolling my own.<br></div><div><br></div><div>Thanks -- RJ<br><br></div></div></div></div>