diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121118/c7563479/attachment-0001.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20121118/c7563479/attachment-0001.html | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121118/c7563479/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121118/c7563479/attachment-0001.html new file mode 100644 index 000000000..dd594ea15 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121118/c7563479/attachment-0001.html @@ -0,0 +1,44 @@ +<p dir="ltr"><br> +On 18 Nov 2012 22:13, "Colin Guthrie" <<a href="mailto:mageia@colin.guthr.ie">mageia@colin.guthr.ie</a>> wrote:<br> +><br> +> 'Twas brillig, and Thierry Vignaud at 18/11/12 16:40 did gyre and gimble:<br> +> > On 18 November 2012 17:37, Colin Guthrie <<a href="mailto:mageia@colin.guthr.ie">mageia@colin.guthr.ie</a>> wrote:<br> +> ><br> +> >> This package, when installed will add a new menu option to your<br> +> >> bootloader. Simply install this package, reboot, select the "Mageia 3<br> +> >> Upgrade Preparation" entry boot, wait while your FS is converted and<br> +> >> then perform a urpmi upgrade as you would normally.<br> +> >><br> +> >> I've not specifically tested the upgrade part, only the installation and<br> +> >> creation of the initrd and bootloader entries in grub. I've also not<br> +> >> done this on an mga2 machine yet but will do soon enough.<br> +> >><br> +> >> I just wanted to get this package "out there" for anyone wanting to<br> +> >> update their mga2 machines to mga3 a3 but not wanting to use the installer.<br> +> >><br> +> >> At present there are a few limitations:<br> +> >><br> +> >> 1. It requires kernel 3.3.8-2.mga2 to be installed (any flavour should<br> +> >> work). A specific kernel version is not really 100% necessary but it<br> +> >> does mean I can add hard requires to the package. This is only desirable<br> +> >> to prevent the situation where users install this upgrade package but do<br> +> >> not run it and later remove the kernel used to generate the initrd for<br> +> >> the bootloader menu item, thus breaking it. Any smarter ideas on how to<br> +> >> manage this welcome.<br> +> ><br> +> > Cannot you just made dracut/mkinitrd always include it and just<br> +> > rebuild initrds so<br> +> > that any kernel with work<br> +><br> +> Well yes, this package installs a dracut config snippet that does always<br> +> include the module. The rebuilding of the initrd is just that - a<br> +> rebuild under the same name as is always used for the normal kernel -<br> +> just with the extra convertfs module added.<br> +><br> +> However, it requires special kernel command line to trigger the change<br> +> and thus the bootloader entry adds the needed params for you.<br> +><br> +> I'm not sure it would be a good idea to make any boot silently do the<br> +> conversion.</p> +<p dir="ltr">But you can have the new entry pointing to the non versionned symlinks<br> +</p> |