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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANNOUNCE%3A%20The%20/usr%20move%20cometh%21%20%3C----%20Instructions&In-Reply-To=%3C501BCACF.8050608%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="017919.html">
<LINK REL="Next" HREF="017916.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANNOUNCE%3A%20The%20/usr%20move%20cometh%21%20%3C----%20Instructions&In-Reply-To=%3C501BCACF.8050608%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions">mageia at colin.guthr.ie
</A><BR>
<I>Fri Aug 3 14:57:51 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="017919.html">[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions
</A></li>
<LI>Next message: <A HREF="017916.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17926">[ date ]</a>
<a href="thread.html#17926">[ thread ]</a>
<a href="subject.html#17926">[ subject ]</a>
<a href="author.html#17926">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Pascal Terjan at 03/08/12 11:32 did gyre and gimble:
><i> On Fri, Aug 3, 2012 at 11:27 AM, Christiaan Welvaart
</I>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">cjw at daneel.dyndns.org</A>> wrote:
</I>>><i> On Fri, 3 Aug 2012, Colin Guthrie wrote:
</I>>><i>
</I>>>><i> 'Twas brillig, and Pascal Terjan at 03/08/12 00:40 did gyre and gimble:
</I>>>>><i>
</I>>>>><i> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">pterjan at gmail.com</A>> wrote:
</I>>>>>><i>
</I>>>>>><i> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>>
</I>>>>>><i> wrote:
</I>>>>>>><i>
</I>>>>>>><i> OK, so the packages have now all been uploaded.
</I>>>>>>><i>
</I>>>>>>><i> You should see several packages now that you cannot install on
</I>>>>>>><i> Cauldron.
</I>>>>>>><i> This is intended behaviour.
</I>>>>>>><i>
</I>>>>>>><i> Here is how to update your cauldron systems:
</I>>>>>>><i>
</I>>>>>>><i> 1. Run "urpmi --auto-update" install everything that can be installed.
</I>>>>>>><i> 2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
</I>>>>>>><i> sure (it may have been excluded in the --auto-update if it was in a
</I>>>>>>><i> transaction with other packages that could not be installed).
</I>>>>>>><i> 3. Ensure that you do not have zapata or dpkg installed (rpm -e
</I>>>>>>><i> zapata;
</I>>>>>>><i> rpm -e dpkg)
</I>>>>>>><i> 4. Generate a new initrd and include the conversion script: dracut -f
</I>>>>>>><i> -a convertfs
</I>>>>>>><i> 5. If you have /usr on a separate partition
</I>>>>>>><i> - Ensure there is enough free space to hold /bin, /sbin, /lib and
</I>>>>>>><i> /lib64 content.
</I>>>>>>><i> - If your /usr is mounted readonly, change your /etc/fstab to
</I>>>>>>><i> mount
</I>>>>>>><i> it rw.
</I>>>>>>><i> 6. Reboot.
</I>>>>>>><i> 7. At the bootloader prompt, edit the command line and append: "rw
</I>>>>>>><i> rd.convertfs" (without the quotes) to your command line and then boot.
</I>>>>>>><i>
</I>>>>>>><i> That should be all that is needed :)
</I>>>>>><i>
</I>>>>>><i>
</I>>>>>><i> How to update a chroot?
</I>>>>><i>
</I>>>>><i>
</I>>>>><i> Answering to myself:
</I>>>>><i>
</I>>>>><i> chroot $chroot urpmi dracut
</I>>>>><i> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
</I>>>>><i>
</I>>>>><i> That did the conversion, but I still can't update, probably because my
</I>>>>><i> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
</I>>>>><i> it before the conversion (it pulls filesystem).
</I>>>><i>
</I>>>><i>
</I>>>><i> Yeah in this case if the conversion is done, I'd just recommend
</I>>>><i> installing filesystem --nodeps and the rest should flow. It's not ideal
</I>>>><i> certainly, but there is still time to polish this a bit before upgraders
</I>>>><i> get hit by this (and as there will be updated rpm packages in the stable
</I>>>><i> releases, it should mitigate this specific problem, but we should still
</I>>>><i> see if we can do things better)
</I>>><i>
</I>>><i>
</I>>><i> Polish this a bit? It is not at all ready, and as I said earlier rpmlib is
</I>>><i> broken. Please don't upload broken rpm packages to stable releases.
</I>>><i>
</I>>><i> Maybe the instructions should be:
</I>>><i> - install dracut and kernel-desktop-latest from mga3
</I>>><i> - reboot, make sure the "usrmove filesystem update"
</I>>><i> kernel entry is chosen in the bootloader
</I>>><i> - upgrade to mga3 as usual
</I>>><i>
</I>>><i> But that means a lot of things are still missing:
</I>>><i> - dracut automatically including the conversion script
</I>>><i> (only when needed?)
</I>>><i> - automatic generation of the bootloader entry mentioned above
</I>><i>
</I>><i> I would vote to also force the reboot into this entry at next boot
</I>
Yeah I was intending to have a new package that would be pushed into
mga2 that ensures dracut is installed (as opposed to mkinitrd - not sure
why you're suggesting kernel-desktop-latest here).
This new package would take care to install an initrd and add bootloader
entry for (probably) the newest currently installed kernel and probably
ensure it was the default entry until the boot was complete at which
point it would be automatically removed.
TBH I'm less worried about the "broken" rpmlib issue than Christiaan.
While I can't argue against him technically, I think practical
pragmatism is such that it's not going to be an issue for all but a
handful of people, in which case it's likely not worth me spending
several days working on a more elegant and technically correct solution.
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="017919.html">[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions
</A></li>
<LI>Next message: <A HREF="017916.html">[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17926">[ date ]</a>
<a href="thread.html#17926">[ thread ]</a>
<a href="subject.html#17926">[ subject ]</a>
<a href="author.html#17926">[ 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>
|
