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