blob: 70ecc5747f60f5a1b646b3466656f6c6a36a94fa (
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
113
114
115
|
<!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=%3C51362750.7010101%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023309.html">
<LINK REL="Next" HREF="023303.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Why is AHCI statically compiled into kernel?</H1>
<B>Colin Guthrie</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=%3C51362750.7010101%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] Why is AHCI statically compiled into kernel?">mageia at colin.guthr.ie
</A><BR>
<I>Tue Mar 5 18:11:44 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023309.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023303.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23301">[ date ]</a>
<a href="thread.html#23301">[ thread ]</a>
<a href="subject.html#23301">[ subject ]</a>
<a href="author.html#23301">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and R James at 05/03/13 16:20 did gyre and gimble:
><i> I remember when PATA (IDE) drivers were statically compiled into the
</I>><i> kernel, then we went to modular IDE which I liked because modprobe
</I>><i> ordering could be controlled. (When dealing with parity RAID, its nice
</I>><i> to have logical drive enumeration because SATA ports don't have UUID
</I>><i> labels.)
</I>
Anything that relies on ordering is just broken by design. We need to
handle things gracefully regardless of the order they are detected. This
is why UUIDs are the defacto method for filesystem identification these
days and why in mga4 we'll likely switch to a consistent naming scheme
for networking devices too.
Also "modprobe ordering" is increasingly not true either as many modules
are automatically loaded when the hardware is present.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023309.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023303.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23301">[ date ]</a>
<a href="thread.html#23301">[ thread ]</a>
<a href="subject.html#23301">[ subject ]</a>
<a href="author.html#23301">[ 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>
|
