On 25.08.2015 11:07, Simon Kitching wrote:
On 08/25/2015 10:36 AM, Simon Geard wrote:
On Mon, 2015-08-24 at 15:29 -0500, Bruce Dubbs wrote:
If distros like RedHat were really looking for consistency, they
would use /bin, /lib, and /sbin, and remove them from /usr. What
they really are doing is trying to make things easier for themselves
by not being concerned where each package file is placed.
They *are* concerned where each file is placed - but it's not about
consistency, as such. The purpose is actually to support /usr as a self
-contained system, because this is useful for doing containers,
something that's greatly in fashion these days.
If you look at it from that point of view, the change makes a lot more
sense. For the container, the root filesystem should only hold the bits
that are unique to the container - which includes things like /etc and
maybe /var, but it mostly definitely doesn't include things like glibc,
bash, and all the other bits normally under /lib, /bin, and /sbin.
By moving the contents of those directories under /usr, they get a
single filesystem that needs to be mounted (read-only) into every
container, instead of a hundred containers having a hundred copies of
the basic installation.
Incidentally, this is also the reason why systemd puts configuration
defaults under /usr instead of /etc - so that the bits in /etc are
*only* the bits that are specifically configured for a specific machine
(or container).
Simon.
Agreed. I would just like to add that although the unified approach
helps build clustered environments, it also has several other minor
benefits and possibly a few minor drawbacks depending on use-case. In
other words, a win for some and neutral for most.
I much prefer the split environment also just for the feel of it, I
don't see any benefits at all from the unified approach apart from the
hypothetical clustered environment, which really is something totally
out of scope of lfs/blfs, in my opinion.
As Simon G. said in another email, only a tiny percentage of users
actually care. As it happens, "LFS newbies" might care, which is why I
brought the subject up. Sorry :-)
I doubt any "LFS newbies" unpolluted by LP propaganda care one bit about
clustered environments. I would have thought that people getting into
LFS are usually familiar and comfortable with well-established
Unix/Linux traditions, will expect /bin, /sbin and /lib where they
always have been and are not all that into changing everything for the
sake of changing everything.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
