[Mageia-dev] ANN: Upgrading from Mageia 2 via urpmi
shikamaru at shikamaru.fr
Tue Dec 11 20:27:23 CET 2012
On Sun, Dec 09, 2012 at 06:49:03PM +0000, Colin Guthrie wrote:
> 'Twas brillig, and Colin Guthrie at 09/12/12 12:14 did gyre and gimble:
> > 'Twas brillig, and Remy CLOUARD at 08/12/12 12:25 did gyre and gimble:
> >> I’ve followed the procedure and could upgrade my system from 2 to
> >> cauldron, but I still have an issue with the filesystem package.
> >> Somehow it seems like it fails to move /var/run to /run and /var/lock to
> >> /run/lock.
> >> I would be glad if there could be a workaround for this.
> >> The only way out I think would be to manually do the symlink from
> >> another install.
> >> Could you confirm that ?
> > Actually yes, there is still a problem at present with /var on a
> > separate partition... I need to look into that.
> So the latest package should mount /var in the initrd in much the same
> way it does with /usr (not exactly the same but I want to make the
> changes as unobtrusive as possible and ideally separate from the main
> dracut package for convenience of updating).
> I presume your setup is such that /var is indeed on a separate partition?
Yeah, I don’t see the point of having a separate usr so that one went
smoothly. However, having a separate /var is useful even on a desktop
for me, because of /var/cache/urpmi (I had aptitude fill my / on a
safe-upgrade that ended up not being that safe once so I kinda became
> In order to fix this, simply mv the folders out the way and just do the
> symlinks manually - it'll mess up the current boot, but a reboot should
> fix it.
That’s what I did indeed, then I could upgrade filesystem, thanks for
the answer ;)
> If the symlinks disappear and are replaced again by folders, then also
> make sure you disable mandriva-clean-var-run-lock.service as it
> helpfully nukes the symlinks (the update does this but perhaps it's
> somehow been run/re-enabled?)
Can’t answer for that, most of the time I never shutdown my laptop, only
I should also mention that each try at installing filesystem resulted in
a temporary symlink being created like: lock;50b68005. I assume these
symlinks can safely be removed, just thought I would point that out.
Thanks for your help !
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
More information about the Mageia-dev