On Thursday, December 20, 2012 07:02:06 AM Rich Freeman wrote: > On Thu, Dec 20, 2012 at 6:21 AM, Richard Yao <r...@gentoo.org> wrote: > > No one has proposed moving everything to /usr. At the minimum, we would > > still have /etc and /var in /, as well as various mountpoints. If we do > > move those to /usr, then we effectively renamed / to /usr, which is > > pointless. The absurdity of mounting /usr over NFS instead of / is > > precisely why people are saying to just mount / (with /usr as being part > > of it). > > We're drifting here, but the concept is that machine-local stuff like > configuration stays out of /usr, and generic distro stuff stays in > /usr. > > A webserver for site1 vs site2 would be identical in /usr, but > different elsewhere.
It would be identical everywhere but on: /etc/apache /var/www (using default locations) I would actually put /var/www on the share as well and use symlinks from /etc/apache to point to the specific vhost-config files. That way I could quickly move websites to a different node when I'd need to take one down for maintenance. Having only /usr shared betweehn those wouldn't be sufficient and would make patching and updates more risky as I would then be updating the whole environment at once. > However, that whole approach makes less sense for a distro that prides > itself on you being able to make every installation unique. That > said, if you do want to make a whole bunch of Gentoo installs the same > then sticking everything important in /usr and network mounting it is > a good way to accomplish it. How does portage handle a situation like this? Would I be able to use emerge on any node to add additional software along with all the config-file changes? If we take the webserver examples: The software is under /usr The configuration is under /etc/apache If I update apache and there are additional options and/or changes to the config files, how do I migrate those to all the different nodes? If the config is the same on all nodes, why not simply share the " / " ? If it differs, I then need to write down all the new options and go through every single node and update the config there. The same is true with any other environment where multiple nodes are used for the same purpose. For the usecases that I generally deal with, the only time where a shared /usr would make sense is when I select " Install everything " during the install. I used to do that to avoid having to deal with RPM-dependencies when I was using Redhat. -- Joost
