Ken wrote:
On May 29, 2014 11:39:34 AM EDT, Andrey Borzenkov <arvidjaar@gmail.com> wrote:
В Tue, 27 May 2014 16:23:05 +0200 "Dr. Werner Fink" <werner@suse.de> пишет:
In short, the junction of / and /usr does not imply that legacy
commands must
be moved from /bin to /usr/bin, nor from /sbin to /usr/sbin IMHO.
Actually it does. The main idea is to have the whole binary part of OS under single root (filesystem, subvolume, dataset - you name it) to make it easy to backup, snapshot, clone and revert it. This leaves the rest as local system defined configuration/data.
But it already is, the single filesystem is / or commonly called root. It is the only way I set up my systems.
But that's NOT necessarily a good thing. System-necessary commands, configuration files, and libraries should all be on the root filesystem. However, non-essential stuff (user-land applications, libraries & configuration files) should be in /usr.... ON A SEPARATE FILESYSTEM. Why? So that if an unfortunate accident occurs, and updating stuff in the /usr hierarchy results in a filesystem corruption, the system is still bootable, and repairable, because the system-essentials are on a separate filesystem. Up until / and /usr were forcibly mashed together, my / filesystem was typically 2GB, and /usr on the order of 50 GB Why? To protect the most critical 1.5GB of files (the / filesystem) from all of the installation and updating activity going on in /usr. All this stuff that forced the merging of /usr into / is utterly retarded. Those people writing systemD are directly responsible for this shitty state of affairs.
Ken
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org