From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-November/020062.html | 129 +++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-November/020062.html (limited to 'zarb-ml/mageia-dev/2012-November/020062.html') diff --git a/zarb-ml/mageia-dev/2012-November/020062.html b/zarb-ml/mageia-dev/2012-November/020062.html new file mode 100644 index 000000000..6be1cd1cd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-November/020062.html @@ -0,0 +1,129 @@ + + + + [Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi + + + + + + + + + +

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

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Nov 19 00:52:29 CET 2012 +

+
+ +
On 18 Nov 2012 22:13, "Colin Guthrie" <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> 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
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20121118/c7563479/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1