blob: 4a58dbc9b83a37203a063dc8c035ea11c28ec24c (
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
|
<!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=%3C5138C97A.7040803%40earthlink.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023355.html">
<LINK REL="Next" HREF="023304.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Why is AHCI statically compiled into kernel?</H1>
<B>Felix Miata</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=%3C5138C97A.7040803%40earthlink.net%3E"
TITLE="[Mageia-dev] Why is AHCI statically compiled into kernel?">mrmazda at earthlink.net
</A><BR>
<I>Thu Mar 7 18:08:10 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023355.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023304.html">[Mageia-dev] Freeze push: phoronix-test-suite
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23356">[ date ]</a>
<a href="thread.html#23356">[ thread ]</a>
<a href="subject.html#23356">[ subject ]</a>
<a href="author.html#23356">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 2013-03-07 17:52 (GMT+0100) Johnny A. Solbu composed:
><i> R James wrote:
</I>
>><i> After the installation, you can edit /boot/grub/menu.lst replacing each
</I>>><i> UUID=<blahblahblah> with LABEL=<DEFANGED_label>. For example:
</I>
>><i> root=LABEL=mgaroot (and) resume=LABEL=swap
</I>
>><i> Similarly in /etc/fstab, you can have entries like:
</I>
>><i> LABEL=mgaroot / ext4 relatime 1 1
</I>>><i> LABEL=swap swap swap defaults 0 0
</I>
><i> The problem with that is in those situations where one have two partitions with the same label, such as when one install into a new and bigger disk and keeps the old disk installed. A friend of mine does that quite often.
</I>
><i> I still prefer UUID, as those are unique.
</I>
As there are something like 16 or more characters available for volume labels
on native partitions, there's no need in the vast majority of situations for
them to be non-unique. Even after cloning operations it's a simple enough
matter in most cases to alter the copies' and/or originals' labels and UUIDs.
I use labels liberally with native partitions in cmdlines and fstabs, UUIDs
never. Volume labels can be readily remembered and typed as circumstances
dictate, unlike UUIDs.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** <A HREF="http://fm.no-ip.com/">http://fm.no-ip.com/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023355.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
<LI>Next message: <A HREF="023304.html">[Mageia-dev] Freeze push: phoronix-test-suite
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23356">[ date ]</a>
<a href="thread.html#23356">[ thread ]</a>
<a href="subject.html#23356">[ subject ]</a>
<a href="author.html#23356">[ 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>
|
