[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

[Colin Guthrie]

'Twas brillig, and Shlomi Fish at 22/07/12 17:51 did gyre and gimble:
> Hi all,
> 
> On Sun, 22 Jul 2012 19:46:58 +0300
> Shlomi Fish <shlomif at shlomifish.org> wrote:
> 
>> Hi Colin,
>>
>> On Sun, 22 Jul 2012 01:12:58 +0100
>> Colin Guthrie <mageia at colin.guthr.ie> wrote:
>>
>>> 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 :)
>>>
>>
>> OK, I did all that and now I am getting:
>>
>> [QUOTE]
>> installing findutils-4.5.10-2.mga3.x86_64.rpm lib64plymouth2-0.8.6.1-2.mga3.x86_64.rpm filesystem-2.1.9-18.mga3.x86_64.rpm lib64ncursesw-devel-5.9-7.mga3.x86_64.rpm plymouth-plugin-script-0.8.6.1-2.mga3.x86_64.rpm lib64ncurses5-5.9-7.mga3.x86_64.rpm ncurses-5.9-7.mga3.x86_64.rpm plymouth-plugin-label-0.8.6.1-2.mga3.x86_64.rpm lib64dbjava5.1-5.1.29-4.mga3.x86_64.rpm lib64ncursesw5-5.9-7.mga3.x86_64.rpm lib64ncurses-devel-5.9-7.mga3.x86_64.rpm from /var/cache/urpmi/rpms
>> Preparing...                     #############################################
>>      1/69: filesystem            #############################################
>> error: unpacking of archive failed on file /var/lock: cpio: rename failed - Is a directory
>> error: filesystem-2.1.9-18.mga3.x86_64: install failed
>>      2/69: ncurses               #############################################
>>      3/69: lib64ncurses5         #############################################
>>      4/69: lib64plymouth2        #############################################
>>      5/69: plymouth-plugin-label #############################################
>>      6/69: lib64ncursesw5        #############################################
>>      7/69: lib64ncursesw-devel   #############################################
>>      8/69: plymouth-plugin-script
>>                                  #############################################
>>      9/69: lib64ncurses-devel    #############################################
>>     10/69: findutils             #############################################
>>     11/69: lib64dbjava5.1        #############################################
>> [/QUOTE]
>>
>> And the rest of the packages refuse to install.
> 
> OK, I figured out. After I ran as root:
> 
> # cd /var
> # mv lock lock.ol
> # mv run run.old
> 
> It was fixed and I was able to install the "filesystem" package and the rest
> of the packages. However, something like that should not happen.


Well, this should have been done for you. Did you already have
run.runmove~ and lock.lockmove~ folders in /var?

If so then I suspect something is killing the symlinks.

I did have this problem initially too because the
mandriva-clean-var-run-lock.service file would actually delete the
symlinks and then some other system (perhaps systemd-tmpfiles) actually
recreated the /var/run and /var/lock folders.

In the latest version of the dracut script I ensured that I disabled
that script by deleting the service file.

Can you double check that rebooting again doesn't "reconvert" the links
back to dirs for /var/run and /var/lock because if so, then there could
be some other "cleaning" config somewhere that I've missed.

Cheers

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/