1 |
Ian Stakenvicius posted on Tue, 03 Jan 2012 11:40:02 -0500 as excerpted: |
2 |
|
3 |
> Side note - if /lib is getting moved, does that mean /lib/modules is |
4 |
> moving to /usr/lib/modules too? So kernel modules are no longer on |
5 |
> root? |
6 |
|
7 |
Yes. Again, the whole thing is being designed from the perspective of a |
8 |
binary distro which already uses an initr* to handle loading the modules |
9 |
necessary for mounting real-root, and from that perspective, all they're |
10 |
doing is having it handle /usr in the same way, mounting it right after |
11 |
real-root in early-init, before control switches to it from the initr*. |
12 |
|
13 |
The set of folks behind this don't particularly care about anyone doing |
14 |
it a different way, which they consider Unix legacy, just as they |
15 |
consider the BSDs, etc, legacy, integrating Linux-only solutions and |
16 |
refusing to hold up "progress" (as they view it) just because someone |
17 |
else can't keep up. |
18 |
|
19 |
What we're really seeing now is the effect of letting RedHat with its |
20 |
paid developers be the core behind so many core Linux systems, forcing |
21 |
udev, systemd, /usr-as-the-new-root, etc, down everyone else's throats |
22 |
because they can, because the entire community is so dependent on RedHat |
23 |
(with Ubuntu and SuSE as well for some but not all of it) and its devs |
24 |
and its money that it's no longer feasible for anyone else to fork all |
25 |
the core programs RedHat devs lead on, and keep up. Sure, they could be |
26 |
forked, but the forks would be left with few enough resources it'd be |
27 |
like xfree86, they might still be there but in a few years they'd be |
28 |
forgotten about by the rest of the community... One project, not a |
29 |
problem, all of them together, just not feasible. |
30 |
|
31 |
What about when glibc also begins to assume everything's in /usr/? ... |
32 |
|
33 |
-- |
34 |
Duncan - List replies preferred. No HTML msgs. |
35 |
"Every nonfree program has a lord, a master -- |
36 |
and if you use the program, he is your master." Richard Stallman |