upgrading f16 (32bit) to F17 (64bit) when /usr is is a partition

[Joel Rees]

On Sat, Dec 29, 2012 at 7:52 AM, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>
> Am 28.12.2012 23:43, schrieb Joel Rees:
>> I'm wondering if anyone has ventured to move /usr after the install.
>> If so, how badly does it bite?
>
> if selinux is disabled it should be quite easy to move anything
> with a livecd and also create the symlinks, what is more a problem
> in your subject is upgrade 32bit to 64bit
>
>
> lrwxrwxrwx    1 root root    7 2012-10-05 13:20 bin -> usr/bin
> lrwxrwxrwx    1 root root    7 2012-10-05 13:20 lib -> usr/lib
> lrwxrwxrwx    1 root root    9 2012-10-05 13:20 lib64 -> usr/lib64
> lrwxrwxrwx    1 root root    8 2012-10-05 13:20 sbin -> usr/sbin

Solved by a fresh minimal install of FC17 64 bit and starting over
from scratch, rebuilding my package set.

That is, those are soft links, aren't they? So crossing volume
boundaries should be possible? Maybe? Or is there something else that,
say, doing a selinux relabel wouldn't resolve?

Yeah, using the netinstall CD image (live on USB because this netbook
has no CD and I have no USB CD drive) to update from 32 bits to 64
bits at the same time as updating from F16 to F17 was a good way to
shoot myself in the foot. I did it because I realized, worst case, I'd
be left with the option of re-installing F17 from scratch and
rebuilding my set of packages as I go, and that was the only other
option any way. Lost a day to the gambit, but no data lost (yet).

I don't know what all it missed. It seemed to handle the links into
the /usr merge and the additional links to the 64 bit stuff okay. Near
as I could tell, the only thing missing was the kernel and associated
files. But I couldn't figure out how to only install the kernel set,
and I guess I don't trust myself to know nothing else was missing. So
it was a bad gamble from the outset.

So, now I'm doing what I should have been doing yesterday.

--
Joel Rees