[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi

Mon Nov 19 01:07:47 CET 2012

'Twas brillig, and Pascal Terjan at 18/11/12 23:52 did gyre and gimble:
+> 
+> On 18 Nov 2012 22:13, "Colin Guthrie" <mageia at colin.guthr.ie
+> <mailto:mageia at colin.guthr.ie>> wrote:
+>>
+>> 'Twas brillig, and Thierry Vignaud at 18/11/12 16:40 did gyre and gimble:
+>> > On 18 November 2012 17:37, Colin Guthrie <mageia at colin.guthr.ie
+> <mailto:mageia at colin.guthr.ie>> wrote:
+>> >
+>> >> This package, when installed will add a new menu option to your
+>> >> bootloader. Simply install this package, reboot, select the "Mageia 3
+>> >> Upgrade Preparation" entry boot, wait while your FS is converted and
+>> >> then perform a urpmi upgrade as you would normally.
+>> >>
+>> >> I've not specifically tested the upgrade part, only the
+> installation and
+>> >> creation of the initrd and bootloader entries in grub. I've also not
+>> >> done this on an mga2 machine yet but will do soon enough.
+>> >>
+>> >> I just wanted to get this package "out there" for anyone wanting to
+>> >> update their mga2 machines to mga3 a3 but not wanting to use the
+> installer.
+>> >>
+>> >> At present there are a few limitations:
+>> >>
+>> >> 1. It requires kernel 3.3.8-2.mga2 to be installed (any flavour should
+>> >> work). A specific kernel version is not really 100% necessary but it
+>> >> does mean I can add hard requires to the package. This is only
+> desirable
+>> >> to prevent the situation where users install this upgrade package
+> but do
+>> >> not run it and later remove the kernel used to generate the initrd for
+>> >> the bootloader menu item, thus breaking it. Any smarter ideas on how to
+>> >> manage this welcome.
+>> >
+>> > Cannot you just made dracut/mkinitrd always include it and just
+>> > rebuild initrds so
+>> > that any kernel with work
+>>
+>> Well yes, this package installs a dracut config snippet that does always
+>> include the module. The rebuilding of the initrd is just that - a
+>> rebuild under the same name as is always used for the normal kernel -
+>> just with the extra convertfs module added.
+>>
+>> However, it requires special kernel command line to trigger the change
+>> and thus the bootloader entry adds the needed params for you.
+>>
+>> I'm not sure it would be a good idea to make any boot silently do the
+>> conversion.
+> 
+> But you can have the new entry pointing to the non versionned symlinks
+
+Yup, that would work I guess. Dunno why I didn't think of that :p
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+