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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Upgrading%20from%20Mageia%202%20via%20urpmi&In-Reply-To=%3C514F23A8.3040907%40ventoso.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023773.html">
<LINK REL="Next" HREF="023785.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi</H1>
<B>Luca Olivetti</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Upgrading%20from%20Mageia%202%20via%20urpmi&In-Reply-To=%3C514F23A8.3040907%40ventoso.org%3E"
TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">luca at ventoso.org
</A><BR>
<I>Sun Mar 24 17:02:48 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023773.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="023785.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23784">[ date ]</a>
<a href="thread.html#23784">[ thread ]</a>
<a href="subject.html#23784">[ subject ]</a>
<a href="author.html#23784">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Al 24/03/13 13:08, En/na Colin Guthrie ha escrit:
>><i>
</I>>><i> 0) In the "Mageia 3 Upgrade Preparation" NetworkManager stopped
</I>>><i> working, in its place the network applet was used (after the upgrade
</I>>><i> both worked).
</I>><i>
</I>><i>
</I>><i> Yeah, this is due to various folders disappearing... I guess I should
</I>><i> probably do something clever in that package. Perhaps I could look at
</I>><i> the folders in /var/run and their respective owners etc., then write a
</I>><i> file in /etc/tmpfiles.d with them detailed.
</I>><i>
</I>><i> Then when the package is removed again later (automatically as part of
</I>><i> the upgrade) this file would be removed. This should mask most of the
</I>><i> errors. It's not fool proof but it'll probably be enough to avoid
</I>><i> problems in this case. Will add to my TODO :)
</I>
Maybe it's just enough to put it in the wiki, so that one knows what to
expect.
>><i> Eventually I had to kill dbus-send to go on with the upgrade
</I>><i>
</I>><i> I guess I'll have to find a way to time this out... perhaps adding
</I>><i> --reply-timeout would work. It would be nice if your VM was in a state
</I>><i> to be able to test if this has any effect?
</I>
Sure, I have a snapshot before the update just for that (i.e., I want to
be absolutely sure that the upgrade to the final mageia 3 works smoothly
before even attempting to upgrade the real machine). The only problem is
that the update takes roughly 3 hours.
Ping me when you want me to test again.
>><i> 8) I had some problem rebooting (I was using a konsole in kde), the kde
</I>>><i> menu bar didn't work, trying to do an acpi shutdown didn't work, text
</I>>><i> console didn't work. Eventually I just pulled the virtual plug.
</I>><i>
</I>><i> Yeah one of the many problems related to online updates really :) the
</I>><i> "reboot" command should work, but.... :)
</I>
The problem is I already closed the working konsole (silly me) and at
that point I couldn't do anything but pull the plug
><i>
</I>>><i> 9) plymouthd complained but I hadn't time to write down the message, it
</I>>><i> eventually booted fine (but with no graphical menu, probably because the
</I>>><i> initrd was generated running the "Mageia 3 Upgrade Preparation" entry).
</I>><i>
</I>><i> It shouldn't really matter too much to be honest. The upgrade prep
</I>><i> option should be almost identical to a regular boot other than an
</I>><i> additional check will be done on each boot thereafter. But as
</I>><i> rpm-mageia-setup package is removed on upgrade and with it the menu
</I>><i> entry, it shouldn't get in the way too much.
</I>
I performed the update under the "Mageia 3 Upgrade Preparation" and,
since that had no graphical boot, the resulting new kernel also has no
graphical boot. To restore it I had to manually run dracut once booted
in mageia 3.
Maybe I should have performed the update rebooting into the regular
mageia 2? The wiki isn't clear about it.
Bye
--
Luca
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023773.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="023785.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23784">[ date ]</a>
<a href="thread.html#23784">[ thread ]</a>
<a href="subject.html#23784">[ subject ]</a>
<a href="author.html#23784">[ 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>
|
