Le 18/11/2018 à 01:21, Miroslav Skoric a écrit :
On 11/17/18 3:18 PM, Didier Kryn wrote:
<snip>
The advantage of separating /usr is it can be mounted after
boot. /bin and /sbin (and /lib) contain the critical applications
(and library) necessary to boot the system, and they are, by
necessity, part of the root filesystem. Merging /usr means, actually
merging /usr/bin with /bin, /usr/sbin with /sbin and /usr/lib with /lib.
Merging /usr means all the bloat from /usr/bin and /usr/lib will
now be in /bin and /lib (not so much bloat in /usr/sbin). This has very
Two more questions:
1. Installing (too many) software from repositories tends to fill in
/usr to the point it screams for space (particularly in older machines
with smaller HDD). However it seems to me that the root filesystem is
still happy in such cases. But what in case of merger? Can the whole
system be rendered unusable? (Or screaming?)
2. What about local compilations of various 3rd party software that
usually go to /usr/local/bin, sbin, lib, ... in case of merger will
they all go to the root filesystem? More potential trouble? Yes/No? Tnx.
Misko
Debian/Devuan's /usr fits easily in say 8GB. Hard to find such
small disks today. So disk space isn't really an issue in my opinion.
I'm not speaking of special embeded or hand-held systems. There is no
objection to making /usr/local a mountpoint.
Didier
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
