| 1 |
> On Apr 6, 2016, at 4:55 AM, James Le Cuirot <chewi@g.o> wrote: |
| 2 |
> |
| 3 |
> On Wed, 06 Apr 2016 09:42:04 +0200 |
| 4 |
> Alexis Ballier <aballier@g.o> wrote: |
| 5 |
> |
| 6 |
>>> This was invented in Solaris and copied by RHEL. The upgrade |
| 7 |
>>> path for the /usr merge on those systems is a complete |
| 8 |
>>> reinstall. Upgrading from RHEL6 to RHEL7 this Solaris 10 to |
| 9 |
>>> Solaris 11 is not supported. The reason being that there are |
| 10 |
>>> ways of configuring the system boot process with the original |
| 11 |
>>> layout that break if you try using scripts to migrate to the new |
| 12 |
>>> one. A USE flag for the /usr merge that is off by default would |
| 13 |
>>> allow us to have both worlds without putting any systems at |
| 14 |
>>> risk. |
| 15 |
>> |
| 16 |
>> that's what i'm actually more worried about: the fact they failed to |
| 17 |
>> have a proper upgrade path doesnt mean it is impossible, just that it |
| 18 |
>> is not easy. |
| 19 |
> |
| 20 |
> What about Fedora? This system I'm on now started as Fedora 16 and has |
| 21 |
> been upgraded step by step to 23. /bin, /lib, /lib64, and /sbin are |
| 22 |
> symlinks but I'm pretty sure it didn't start out that way. I knew the |
| 23 |
> change was coming but when it actually happened, I didn't notice for |
| 24 |
> quite a while. |
| 25 |
|
| 26 |
The common case can be done by automated scripts. The case where the system is configured to mount /usr after init has started is not. In Fedora's case, they tell users to expect upgrades to break things, so the people bitten by it at least had been warned of breakage before they installed Fedora. |
| 27 |
> |
| 28 |
> -- |
| 29 |
> James Le Cuirot (chewi) |
| 30 |
> Gentoo Linux Developer |
| 31 |
> |
Archives