Re: support for merged /usr in Debian
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, Jan 01, 2016 at 03:53:03PM +0100, Marco d'Itri wrote:
> On Jan 01, Ian Jackson wrote:
>
> > Someone has already mentioned mounting /usr ro. But one generally has
> > to keep /etc rw. I don't think that the right way to address this is
> > to make /etc a mount point.
> I am not aware of any plan to make /etc a mount point, which indeed
> would pointless.
> On a merged /usr system the root file system only contains /boot, /etc,
> /var and /home while the OS proper is all in /usr.
>
> > Anotheer example: I have a system which does a rather hackish NFS root
> > boot. It has its own / but uses /usr from the fileserver. This has
> > worked surprisingly well for a long time.
> With a merged /usr you would be able to serve the whole OS over NFS (and
> even share it among multiple systems without the constant threat of
> having / and /usr diverge) and only configuration + data from the local
> disk, which makes this kind of setup much more useful.
"whole OS over NFS" is the same as "whole OS on /usr"
A design with "whole OS over NFS" breaks the good pratice of having
A design with "whole OS on /usr" breaks the good pratice of having
tools like /bin/mount and /sbin/ifconfig available when /usr is unavailable.
To me is this "TheUsrMerge" something like among
* "it is hard too to explain to have /sbin/fsck and not /usr/sbin/fsck"
* "there was a question about /bin/kill and /usr/bin/killall being inconsequent"
* "we could not agree if p{erl,ython,hp} should in /bin or in /usr/bin"
* "when calling `foo` we rely on $PATH. To avoid $PATH we call `/bin/foo`,
to have a reason to rant it should be /usr/bin/foo"
* "reverting a historic decission is much better then accepting a historic decission"
* "just because we can"
* "others doing also"
In other words: I don't yet see a _good_ reason for "TheUsrMerge".
And I think that it is ill-named,
it should be named "PutAllExecutablesInRootFS" :-)
And the "PutAllExecutablesInRootFS" is
in fact "put all executables in a single file system".
That makes it harder to split out executables in different file systems.
(having a mechanisme for executables in different places,
makes it easy to add another place)
I mean that executables will be in different places. ( ramdisks, netwerk disks
/usr/local /opt )
Groeten
Geert Stappers
- --
Leven en laten leven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJWiAv1AAoJECE10SPYwZvsksgQAIbp0VeOgxTJHcy5+34v8Qk/
3gnwag2Rh6qLCIZ/ag+sO1EDdp/ja0af8XSOxln4p7EnPzgsVRUBA9QIG8ebRn7Z
gdOMk4oTEdBb3i4XcZ0oSjjwsZAYt6aGcjEsYpQlRjexdP7r8ZF+8PMqJ4sfY98C
MumzBvJjBcf3J9Pt3XlyV4AGh5AZt/Ku9sDu6BezeVYd0yo9/TLE+V/9a3MBuve7
p2LaGIQ81XlHpIMbghwrbObu8caKNnk7mBcOUOXSGJBr+7PEOlE5GU+HsmC9ZV49
9FQW+j35x0y2cRSxkOZFgPX4VneXH7VMN1Cpn57gGurZEbWwmvHHLqrfnRN+bOc8
lCRDh8szm/jsMapnQhXClcAb3RsPpOfb4lQ5n8owSqJAGfEezfNyEwcjGlMEJg6l
y/kno8S+vfilJTelQ0EsV8x/DCW7RsofC7mUjxQ5nfxzi+BsFbCRbmywCRBsz9/v
b8eYVYsx0rbgh/L0ZfXpqJBlyLjcNrtUlCiY91IGX4faxp1xcHBVD9feQeIC5lfS
LrUezPTZ3bXjPGo3nGFugkCRflWHx+exmFwDaQXaLP5FNu9+Vv3ufna+P/khHxms
Z93Pn6dDFamNNooa2DbJQxmmZeXMeEw74YLGwQ9fxJXeC5Ntt9cvBeevYs5iZfWU
csniUjI3remGk2HdtCa2
=pc0X
-----END PGP SIGNATURE-----
Reply to: