diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020695.html')
-rw-r--r-- | zarb-ml/mageia-dev/2012-December/020695.html | 138 |
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020695.html b/zarb-ml/mageia-dev/2012-December/020695.html new file mode 100644 index 000000000..1bb838377 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020695.html @@ -0,0 +1,138 @@ +<!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=%3CCAONrEtaici8EG10YqgOF9m2oNCV7W9ajK8CZF%3DP7b6nZ8QwWOA%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="020679.html"> + <LINK REL="Next" HREF="020697.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi</H1> + <B>Thierry Vignaud</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=%3CCAONrEtaici8EG10YqgOF9m2oNCV7W9ajK8CZF%3DP7b6nZ8QwWOA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi">thierry.vignaud at gmail.com + </A><BR> + <I>Sun Dec 9 19:48:07 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020679.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020697.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20695">[ date ]</a> + <a href="thread.html#20695">[ thread ]</a> + <a href="subject.html#20695">[ subject ]</a> + <a href="author.html#20695">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 9 December 2012 13:18, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: +>>><i> So I've just pushed the package mageia-prepare-upgrade to mga2 +</I>>>><i> core/updates_testing. +</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 and +</I>>>><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 installer. +</I>>>><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 desirable +</I>>>><i> to prevent the situation where users install this upgrade package but do +</I>>>><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> 2. If you have /usr in a separate partition and have it mounted ro in +</I>>>><i> your fstab, you will have to manually change the fstab to rw for the +</I>>>><i> upgrade boot. +</I>>>><i> +</I>>>><i> +</I>>>><i> Happy testing. Let me know if it kills any kittens. Please keep a backup +</I>>>><i> etc. etc. +</I>>>><i> +</I>>>><i> Col +</I>>><i> Thanks Colin. +</I>>><i> The conversion works. But then the problem shows, we have no network. +</I>>><i> doing a urpmi --download-all --auto-update only downloads the fist 120+ rpms (the ones needed before +</I>>><i> restart-urpmi +</I>>><i> +</I>>><i> What is needed is to add some directories and then the network will start +</I>>><i> /var/run/netreport +</I>>><i> /var/lock/subsystem/network +</I>>><i> +</I>>><i> I will check after the upgrade if they can be deleted +</I>><i> +</I>><i> Hmm, yes, I guess after doing the upgrade the various /var/run and +</I>><i> /var/lock folders would be nuked. In mga3 they will be created by +</I>><i> tmpfiles but not with a simple reboot on mga2... +</I>><i> +</I>><i> Hmm, I wonder how best to do this... perhaps we could ship updated +</I>><i> packages for each of the packages which absolutely *need* this to do the +</I>><i> download... or perhaps we could just ship some essential config tweaks +</I>><i> in the this mageia-prepare-upgrade file. It shouldn't do any harm to do +</I>><i> the latter and it's a bit easier on the QA folk. +</I> +Humm we could just package mageia-prepare-upgrade in mga3 and add +it to urpmi priority list. +Thus it would also work for people who never apply updates... +My 2 cents +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020679.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI>Next message: <A HREF="020697.html">[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20695">[ date ]</a> + <a href="thread.html#20695">[ thread ]</a> + <a href="subject.html#20695">[ subject ]</a> + <a href="author.html#20695">[ 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> |