zarb-ml/mageia-dev/2013-March/023355.html


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

<!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=%3C201303071752.22484.cooker%40solbu.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="023366.html">
   <LINK REL="Next"  HREF="023356.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Why is AHCI statically compiled into kernel?</H1>
    <B>Johnny A. Solbu</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=%3C201303071752.22484.cooker%40solbu.net%3E"
       TITLE="[Mageia-dev] Why is AHCI statically compiled into kernel?">cooker at solbu.net
       </A><BR>
    <I>Thu Mar  7 17:52:18 CET 2013</I>
    <P><UL>
        <LI>Previous message: <A HREF="023366.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
        <LI>Next message: <A HREF="023356.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#23355">[ date ]</a>
              <a href="thread.html#23355">[ thread ]</a>
              <a href="subject.html#23355">[ subject ]</a>
              <a href="author.html#23355">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Thursday 7. March 2013 05.38, R James wrote:
&gt;<i> After the installation, you can edit /boot/grub/menu.lst replacing each
</I>&gt;<i> UUID=&lt;blahblahblah&gt; with LABEL=&lt;DEFANGED_label&gt;. For example:
</I>&gt;<i> 
</I>&gt;<i> root=LABEL=mgaroot (and) resume=LABEL=swap
</I>&gt;<i> 
</I>&gt;<i> Similarly in /etc/fstab, you can have entries like:
</I>&gt;<i> 
</I>&gt;<i> LABEL=mgaroot  /     ext4  relatime  1 1
</I>&gt;<i> LABEL=swap     swap  swap  defaults  0 0
</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 still prefer UUID, as those are unique.

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: &lt;/pipermail/mageia-dev/attachments/20130307/147a66d5/attachment.asc&gt;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="023366.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
	<LI>Next message: <A HREF="023356.html">[Mageia-dev] Why is AHCI statically compiled into kernel?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#23355">[ date ]</a>
              <a href="thread.html#23355">[ thread ]</a>
              <a href="subject.html#23355">[ subject ]</a>
              <a href="author.html#23355">[ 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>