| 1 |
On Mon, Aug 5, 2019 at 9:38 PM Grant Taylor < |
| 2 |
gtaylor@×××××××××××××××××××××.net> wrote: |
| 3 |
[...] |
| 4 |
> I don't have any current first hand experience with /usr being a |
| 5 |
> separate file system without using an initramfs / initrd. So I'm going |
| 6 |
> to have to take what you, and others, say on faith that it can't |
| 7 |
> /currently/ be done. But I've got to say, that I find that idea |
| 8 |
> disturbing and highly suspicious. |
| 9 |
|
| 10 |
If it's computable it can be done, of course. Therefore it can be done, |
| 11 |
currently. I don't think nobody has said it absolutely cannot be done. |
| 12 |
|
| 13 |
The thing is: |
| 14 |
|
| 15 |
1. How much work implies to get it done. |
| 16 |
2. Who is gonna do said work. |
| 17 |
|
| 18 |
The answer to 1 is "a lot", since (as someone mentioned in the thread) it |
| 19 |
involves changing not only the init (nevermind systemd; *ALL* init |
| 20 |
systems), but all applications that may require to use binaries in /usr |
| 21 |
before it's mounted. |
| 22 |
|
| 23 |
The answer to 2 is, effectively, "nobody", since it requires a big |
| 24 |
coordinated effort, stepping into the toes of several projects, |
| 25 |
significantly augmenting their code complexity for a corner case[1] that |
| 26 |
can be trivially be solved with an initramfs, which it just works. |
| 27 |
|
| 28 |
Arguing against this trivial (and IMHO, elegant) solution is tilting at |
| 29 |
windmills. Specially if it is for ideological reasons instead of technical |
| 30 |
ones. |
| 31 |
|
| 32 |
Regards. |
| 33 |
|
| 34 |
[1] I firmly believe that's the situation nowadays. |
| 35 |
-- |
| 36 |
Dr. Canek Peláez Valdés |
| 37 |
Profesor de Carrera Asociado C |
| 38 |
Departamento de Matemáticas |
| 39 |
Facultad de Ciencias |
| 40 |
Universidad Nacional Autónoma de México |
Archives