1 |
What, if any, is the benefit of squashing /usr out of the equation? I |
2 |
happen to have a few workstations that load their /usr off an NFS share |
3 |
presently, with some bodgery-workarounds I did pre the udev notification |
4 |
about initramfs's which I have never got around to implementing |
5 |
(although I'm pretty sure I have the tools now to do, along with UUIDs |
6 |
for boot media). |
7 |
Whilst these aren't currently scheduled for upgrade, I don't personally |
8 |
see any merit, given discussions here about work needed to 'shore up' a |
9 |
change to match some particular use case. I would therefore definitely |
10 |
agree with those that have proposed that this is an Option and not a |
11 |
standard gentoo install item unless there are some specific caveats that |
12 |
this solves. |
13 |
|
14 |
Michael/veremit. |
15 |
|
16 |
On 05/04/16 02:19, William Hubbs wrote: |
17 |
> All, |
18 |
> |
19 |
> I thought that since the usr merge is coming up again, and since I lost |
20 |
> track of the message where it was brought up, I would open a |
21 |
> new thread to discuss it. |
22 |
> |
23 |
> When it came up before, some were saying that the /usr merge violates |
24 |
> the fhs. I don't remember the specifics of what the claim was at the |
25 |
> time, (I'm sure someone will point it out if it is still a concern). |
26 |
> |
27 |
> I don't think creating usr merged stages would be that difficult. I |
28 |
> think it would just be a matter of creating a new version of baselayout |
29 |
> that puts these symlinks in place: |
30 |
> |
31 |
> /bin->usr/bin |
32 |
> /lib->usr/lib |
33 |
> /lib32->usr/lib32 |
34 |
> /lib64->usr/lib64 |
35 |
> /sbin->usr/bin |
36 |
> /usr/sbin->bin |
37 |
> |
38 |
> Once that is in place in a new baselayout, I think portage's colission |
39 |
> detection would be able to catch files that had the same names and were |
40 |
> originally in different paths when building the new stages. |
41 |
> |
42 |
> I put some thought also in how to nigrate live systems, and I'm not sure |
43 |
> what the best way to do that is. I wrote a script, which would do it in |
44 |
> theory, but I haven't tested because I only have one system and if |
45 |
> it breaks it the only way back would be to reinstall. |
46 |
> |
47 |
> The script is attached. |
48 |
> |
49 |
> |
50 |
> Thoughts on any of this? |
51 |
> |
52 |
> William |
53 |
> |