Carlos E. R. wrote:
Because that's the solution the devs here implemented, that's why. If you want a different solution you will have to make a very sound case to convince them (and a year after!) or implement it yourself. Otherwise it is not going to change.
I was told at the time that systemd no longer had this requirement and that it could mount /usr as an initial step. That's why I didn't complain for 'a year after'.. as I trusted those who lied. Now I find out that this was a lie and they were just going to hide systemd's flaws in initd. That's NOT a solution, that was a deliberate fabrication. It could have been solved a year ago -- but they didn't want it solved, they wanted it there way and lied to get it. That's why it is how it is... you can just roll with them lying to your face to surreptitiously sneak this hack into the code, or you can realize that they'll do it again and again, and that there is nothing "Open" about Open Suse, and participation of the user community is only at the sufferance and as slaves doing the bidding of those behind the scenes, who will use the community to do their work, and when it doesn't suit them, will like to the community and implement solutions against the community behind their back -- and THEN expect there will be a large enough number of people who are apathetic who will just throw up their hands and say "what's done is done"... Yet I will say this. Even talking about this as a patch back into 12.2. A post install script can be run to determine and broken dependencies of /root on /usr. and switch them. I.e. put the real files on /root and the soft links on /usr, allowing root to boot, mount /usr, then invoke either initd or systemd as per desire. But it obvious now, that systemd can't handle this -- we were told it could, but we were lied to. So The patch will also eliminate booting directly to systemd and insert initd as that remains compatible behavior -- and it can start the "startup" program of the user's choice. I see no reason why this can't be pushed as a patch to 12.2. For 12.3, it would be better if the patch wasn't needed, but it can run automatically after any install to ensure /root doesn't depend on /usr -- specifically it will ensure that /bin and /sbin don't depend on anything off of the device (there are also deps in /etc/alternatives, but I don't believe those are used as part of boot). Each of the binaries can be scanned with 'ldd' for any libs that have been moved off of root, and the script can also move those to root. It isn't clear that links in /usr would be necessary for those, as /lib , /lib64 are in the ldpath the same as their /usr counterparts -- the only requirement is that libs necessary for boot reside in /lib[64], with no links in /usr required. links in /usr/bin & /usr/sbin will be provided back to the the root images, so applications and systemd that use hard-coded paths to /usr, will be happy. MINIMALLY, this could have been done if we had not been lied to -- and the 15-25 packages that have been modified to move their files off of /bin to /usr/bin, would not have needed to have been modded. For 12.3, they can be modded back so the patch won't be necessary -- and put links where needed from /usr/bin -> /bin. Alternatively, we can go with statically linked objects in /bin and not worry about libs. At runtime, EVERYTHING that is statically linked in /bin can be duplicated in /usr/bin with a non-static version that does what cygwin does -- and after initial boot, mounts /usr/bin on top of /bin as a duplicate mount point -- making them the same and making all future program starts use the shared library. This would also provide (in /bin) a set of programs necessary for creating an emergency boot disc. There are many solutions that could have been thought of and implemented that would have worked for everyone if conversation had not been cut short by us being lied to and told it was no longer a problem or requirement for systemd...
And I'm not saying I like it.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iF4EAREIAAYFAlCjEWUACgkQja8UbcUWM1xGqQEAln8DUcOlIWwr2Fcq5TJHX7I9 P6y4d1zxv7Jjm4zaCvYA/RYjPclpD66lyzMlFP/v7LNwHm/nTZuwsMXGvZFRYJ5+ =Q6wn -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org