blob: b7ce5da82f107202f2cd9ce1e731128dae31ee04 (
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
|
<!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=%3C5137489E.2080503%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023307.html">
<LINK REL="Next" HREF="023331.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Why is AHCI statically compiled into kernel?</H1>
<B>Anne Wilson</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=%3C5137489E.2080503%40kde.org%3E"
TITLE="[Mageia-dev] Why is AHCI statically compiled into kernel?">annew at kde.org
</A><BR>
<I>Wed Mar 6 14:46:06 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023307.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023331.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23320">[ date ]</a>
<a href="thread.html#23320">[ thread ]</a>
<a href="subject.html#23320">[ subject ]</a>
<a href="author.html#23320">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/03/13 17:11, Colin Guthrie wrote:
><i> Anything that relies on ordering is just broken by design. We need
</I>><i> to handle things gracefully regardless of the order they are
</I>><i> detected. This is why UUIDs are the defacto method for filesystem
</I>><i> identification these days and why in mga4 we'll likely switch to a
</I>><i> consistent naming scheme for networking devices too.
</I>
While I appreciate the intention, from a user PoV, those UUIDs mean
b***** all. It would be really nice if, when they are first named, it
was possible to allocate a "nickname" for want of a better term.
Anne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - <A HREF="http://www.enigmail.net/">http://www.enigmail.net/</A>
iEYEARECAAYFAlE3SJsACgkQj93fyh4cnBfIYQCfY2j4nJtmCeW+cmX7+EdQOfbq
nh8An39bHvwxaAnexSz1UwtbTBIogaHa
=cMEE
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023307.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023331.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23320">[ date ]</a>
<a href="thread.html#23320">[ thread ]</a>
<a href="subject.html#23320">[ subject ]</a>
<a href="author.html#23320">[ 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>
|
