'Twas brillig, and Nicolas Lécureuil at 22/07/12 11:58 did gyre and gimble: > Le dimanche 22 juillet 2012 12:56:42 Claire Revillet a écrit : >> Le 22/07/2012 02:12, Colin Guthrie a écrit : >>> OK, so the packages have now all been uploaded. >>> >>> You should see several packages now that you cannot install on Cauldron. >>> This is intended behaviour. >>> >>> Here is how to update your cauldron systems: >>> 1. Run "urpmi --auto-update" install everything that can be installed. >>> 2. Ensure that latest dracut is installed. Run "urpmi dracut" to make >>> >>> sure (it may have been excluded in the --auto-update if it was in a >>> transaction with other packages that could not be installed). >>> >>> 3. Ensure that you do not have zapata or dpkg installed (rpm -e zapata; >>> >>> rpm -e dpkg) >>> >>> 4. Generate a new initrd and include the conversion script: dracut -f >>> >>> -a convertfs >>> >>> 5. If you have /usr on a separate partition >>> >>> - Ensure there is enough free space to hold /bin, /sbin, /lib and >>> >>> /lib64 content. >>> >>> - If your /usr is mounted readonly, change your /etc/fstab to mount >>> >>> it rw. >>> >>> 6. Reboot. >>> 7. At the bootloader prompt, edit the command line and append: "rw >>> >>> rd.convertfs" (without the quotes) to your command line and then boot. >>> >>> That should be all that is needed :) >>> >>> If you are extra paranoid, or want to see what is going on, then you can >>> remove the "splash" and "quiet" options from the kernel too. >>> >>> If you want to see things in more depth, you can also add >>> rd.break=pre-pivot to the kernel. You will be dumped into a shell with >>> your / mounted as /sysroot. This shell is *before* conversion. If you >>> type "exit" the conversion will be done, and you'll be dumped to another >>> shell afterwards. Typing exit once more here will boot the system as >>> normal. >>> >>> >>> >>> All the best and good luck!!! >>> >>> Col >> >> Hi >> What append if we decide not to make the step on our machine ? >> Will it still be possible to update ? to package ? > > filesystem rpm won't install anymore so you won't be able to update your > cauldron anymore
Yes exactly. This is a necessary step to continue using Cauldron really. It's also something that will need to be done in the mga2 -> mga3 upgrade although I will ensure that a nice packaged solution exits for users doing this change so as to be a bit more user friendly. 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/
