| 1 |
On Wednesday, April 6, 2016 4:58:05 PM CEST, M. J. Everitt wrote: |
| 2 |
> What, if any, is the benefit of squashing /usr out of the equation? I |
| 3 |
> happen to have a few workstations that load their /usr off an NFS share |
| 4 |
> presently, |
| 5 |
|
| 6 |
|
| 7 |
This is precisely one case where I see benefits: no need to correlate / and |
| 8 |
/usr. |
| 9 |
|
| 10 |
With the current way, this setup is broken if you don't pay attention: |
| 11 |
glibc is not backwards compatible (that is, stuff built for glibc 2.22 is |
| 12 |
not guaranteed to work with 2.21 and less), but you have glibc in /lib and |
| 13 |
stuff in /usr linking and dynamically loading it. If your nfs server |
| 14 |
updates glibc, you have to update every / on every of your workstations or |
| 15 |
fear the consequences of running binaries built for 2.22 but running |
| 16 |
against an older version. |
| 17 |
|
| 18 |
|
| 19 |
See https://fedoraproject.org/wiki/Features/UsrMove for a more complete |
| 20 |
discussion. |
Archives