| 1 |
Hi, |
| 2 |
|
| 3 |
-- large trim -- |
| 4 |
>> For what it's worth. All of my systems are installed with a fixed- |
| 5 |
>> size |
| 6 |
>> 512MB / with everything else (including /usr) on separate LVs. |
| 7 |
>> |
| 8 |
>> Whilst sbin vs bin is just a matter of what's available, to me it |
| 9 |
>> makes |
| 10 |
>> sense to keep these split. To me it's always been logical to keep |
| 11 |
>> administrative type (root) tools under sbin, and stuff that's |
| 12 |
>> generally |
| 13 |
>> useful for users under bin. |
| 14 |
>> |
| 15 |
>> Keeping / and /usr split (or the ability to keep it split) is rather |
| 16 |
>> crucial for me. It's for historic installations a matter of space |
| 17 |
>> constraints on /. For new installations it's a matter of keeping / |
| 18 |
>> as |
| 19 |
>> small as possible in order to have a smallish bootable system which |
| 20 |
>> can |
| 21 |
>> be used for recovering the rest of the system, ideally without an |
| 22 |
>> initrd |
| 23 |
>> (which also works to an extent). |
| 24 |
>> |
| 25 |
>> Kind Regards, |
| 26 |
>> Jaco |
| 27 |
>> |
| 28 |
> For the umpteenth time time: nothing will change. You can keep your |
| 29 |
> (albeit broken) separate / and /usr partitions. *NOTHING* will change |
| 30 |
> for anyone. There are no plans to change the defaults. This is *MERELY* |
| 31 |
> about giving people the chance to opt in to the /usr-merge. |
| 32 |
Thanks for the confirmation. As long as it's an OPTION I'm happy. And |
| 33 |
no, other than on my desktop machine a split /usr is working very well, |
| 34 |
and even in that case a split off /lib/firmware actually caused me much, |
| 35 |
much more problems (for i915 and amdgpu firmware) than a split /usr. |
| 36 |
Unfortunately /lib/firmware grew over the years and so I had no choice |
| 37 |
other than to split it off after the fact. |
| 38 |
> |
| 39 |
> That said, the idea of using / as a "recovery" filesystem in general is |
| 40 |
> broken: |
| 41 |
> https://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken/ |
| 42 |
> And no, this is not systemd breaking your system, or Lennart, it's |
| 43 |
> distros and userlands not being careful to have things in / never |
| 44 |
> depend on things in /usr. |
| 45 |
|
| 46 |
It's saved my butt more than once when the (extremely) limited tools in |
| 47 |
the initrds on those same systems failed to do so. Mostly these cases |
| 48 |
weren't Gentoo. Yes RHEL, I'm looking at you. Gentoo I generally |
| 49 |
recover crazy faults without the use of system rescue CDs (probably |
| 50 |
required it 10 times over 15 years). Can't say the same for those |
| 51 |
distro's pushing for "recovery systems in initrd", and I'm running |
| 52 |
probably 3x more Gentoo systems than all other distro's combined. |
| 53 |
|
| 54 |
The only stuff so far I really wished worked without /usr was editors |
| 55 |
such as vim and/or nano (sed sufficed in those cases). |
| 56 |
|
| 57 |
Would contributing a script that's able to check which binaries in /bin |
| 58 |
(and /sbin) depend on libs not also on / be useful here? Perhaps as a |
| 59 |
QA check somehow? |
| 60 |
|
| 61 |
And I get that that's a completely different rabbit hole ... |
| 62 |
|
| 63 |
1. What about non-lib files, eg, /usr/share/zoneinfo? |
| 64 |
2. Should such binaries be moved to /usr or should the libraries be |
| 65 |
moved to /? |
| 66 |
X. a gazillion things I haven't even started to think about. |
| 67 |
|
| 68 |
Kind Regards, |
| 69 |
Jaco |
| 70 |
|
| 71 |
|
| 72 |
> |
| 73 |
> |
Archives