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
|
<!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=%3CCA%2BCX%2BbiX0WUcTtt%3DSZmUbomSDzH8xzwnohoepuaDtBeCkyUsOw%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="020059.html">
<LINK REL="Next" HREF="020063.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi</H1>
<B>Pascal Terjan</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=%3CCA%2BCX%2BbiX0WUcTtt%3DSZmUbomSDzH8xzwnohoepuaDtBeCkyUsOw%40mail.gmail.com%3E"
TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">pterjan at gmail.com
</A><BR>
<I>Mon Nov 19 00:52:29 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020059.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="020063.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20062">[ date ]</a>
<a href="thread.html#20062">[ thread ]</a>
<a href="subject.html#20062">[ subject ]</a>
<a href="author.html#20062">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 18 Nov 2012 22:13, "Colin Guthrie" <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
><i>
</I>><i> 'Twas brillig, and Thierry Vignaud at 18/11/12 16:40 did gyre and gimble:
</I>><i> > On 18 November 2012 17:37, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
</I>><i> >
</I>><i> >> This package, when installed will add a new menu option to your
</I>><i> >> bootloader. Simply install this package, reboot, select the "Mageia 3
</I>><i> >> Upgrade Preparation" entry boot, wait while your FS is converted and
</I>><i> >> then perform a urpmi upgrade as you would normally.
</I>><i> >>
</I>><i> >> I've not specifically tested the upgrade part, only the installation
</I>and
><i> >> creation of the initrd and bootloader entries in grub. I've also not
</I>><i> >> done this on an mga2 machine yet but will do soon enough.
</I>><i> >>
</I>><i> >> I just wanted to get this package "out there" for anyone wanting to
</I>><i> >> update their mga2 machines to mga3 a3 but not wanting to use the
</I>installer.
><i> >>
</I>><i> >> At present there are a few limitations:
</I>><i> >>
</I>><i> >> 1. It requires kernel 3.3.8-2.mga2 to be installed (any flavour should
</I>><i> >> work). A specific kernel version is not really 100% necessary but it
</I>><i> >> does mean I can add hard requires to the package. This is only
</I>desirable
><i> >> to prevent the situation where users install this upgrade package but
</I>do
><i> >> not run it and later remove the kernel used to generate the initrd for
</I>><i> >> the bootloader menu item, thus breaking it. Any smarter ideas on how to
</I>><i> >> manage this welcome.
</I>><i> >
</I>><i> > Cannot you just made dracut/mkinitrd always include it and just
</I>><i> > rebuild initrds so
</I>><i> > that any kernel with work
</I>><i>
</I>><i> Well yes, this package installs a dracut config snippet that does always
</I>><i> include the module. The rebuilding of the initrd is just that - a
</I>><i> rebuild under the same name as is always used for the normal kernel -
</I>><i> just with the extra convertfs module added.
</I>><i>
</I>><i> However, it requires special kernel command line to trigger the change
</I>><i> and thus the bootloader entry adds the needed params for you.
</I>><i>
</I>><i> I'm not sure it would be a good idea to make any boot silently do the
</I>><i> conversion.
</I>
But you can have the new entry pointing to the non versionned symlinks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20121118/c7563479/attachment.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020059.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI>Next message: <A HREF="020063.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20062">[ date ]</a>
<a href="thread.html#20062">[ thread ]</a>
<a href="subject.html#20062">[ subject ]</a>
<a href="author.html#20062">[ 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>
|
