blob: 1a32075e24c8d1abf7cb937d1cae88ed85a51670 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Why is AHCI statically compiled into kernel?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Why%20is%20AHCI%20statically%20compiled%20into%20kernel%3F&In-Reply-To=%3CCABrUASmvci7%3DuX4JiOHioPhRm3EnQVE87Qq5T3btnXL9sP8bJg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023301.html">
<LINK REL="Next" HREF="023306.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Why is AHCI statically compiled into kernel?</H1>
<B>R James</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Why%20is%20AHCI%20statically%20compiled%20into%20kernel%3F&In-Reply-To=%3CCABrUASmvci7%3DuX4JiOHioPhRm3EnQVE87Qq5T3btnXL9sP8bJg%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Why is AHCI statically compiled into kernel?">upsnag2 at gmail.com
</A><BR>
<I>Tue Mar 5 18:53:12 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023301.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023306.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23303">[ date ]</a>
<a href="thread.html#23303">[ thread ]</a>
<a href="subject.html#23303">[ subject ]</a>
<a href="author.html#23303">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, Mar 5, 2013 at 11:11 AM, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>>wrote:
><i> Anything that relies on ordering is just broken by design. We need to
</I>><i> handle things gracefully regardless of the order they are detected. This
</I>><i> is why UUIDs are the defacto method for filesystem identification these
</I>><i> days and why in mga4 we'll likely switch to a consistent naming scheme
</I>><i> for networking devices too.
</I>><i>
</I>
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)
Also "modprobe ordering" is increasingly not true either as many modules
><i> are automatically loaded when the hardware is present.
</I>><i>
</I>
Yes, but it is possible to override the automatic loading...which is why I
like the modular approach.
Now that I understand the reasons for going back to statically compiled
drivers, I'm OK with rolling my own.
Thanks -- RJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20130305/2d3f7c1d/attachment.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023301.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023306.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23303">[ date ]</a>
<a href="thread.html#23303">[ thread ]</a>
<a href="subject.html#23303">[ subject ]</a>
<a href="author.html#23303">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
