1 |
On Thursday, December 20, 2012 07:02:06 AM Rich Freeman wrote: |
2 |
> On Thu, Dec 20, 2012 at 6:21 AM, Richard Yao <ryao@g.o> wrote: |
3 |
> > No one has proposed moving everything to /usr. At the minimum, we would |
4 |
> > still have /etc and /var in /, as well as various mountpoints. If we do |
5 |
> > move those to /usr, then we effectively renamed / to /usr, which is |
6 |
> > pointless. The absurdity of mounting /usr over NFS instead of / is |
7 |
> > precisely why people are saying to just mount / (with /usr as being part |
8 |
> > of it). |
9 |
> |
10 |
> We're drifting here, but the concept is that machine-local stuff like |
11 |
> configuration stays out of /usr, and generic distro stuff stays in |
12 |
> /usr. |
13 |
> |
14 |
> A webserver for site1 vs site2 would be identical in /usr, but |
15 |
> different elsewhere. |
16 |
|
17 |
It would be identical everywhere but on: |
18 |
/etc/apache |
19 |
/var/www |
20 |
(using default locations) |
21 |
|
22 |
I would actually put /var/www on the share as well and use symlinks from |
23 |
/etc/apache to point to the specific vhost-config files. That way I could |
24 |
quickly move websites to a different node when I'd need to take one down for |
25 |
maintenance. |
26 |
|
27 |
Having only /usr shared betweehn those wouldn't be sufficient and would make |
28 |
patching and updates more risky as I would then be updating the whole |
29 |
environment at once. |
30 |
|
31 |
> However, that whole approach makes less sense for a distro that prides |
32 |
> itself on you being able to make every installation unique. That |
33 |
> said, if you do want to make a whole bunch of Gentoo installs the same |
34 |
> then sticking everything important in /usr and network mounting it is |
35 |
> a good way to accomplish it. |
36 |
|
37 |
How does portage handle a situation like this? |
38 |
Would I be able to use emerge on any node to add additional software along |
39 |
with all the config-file changes? |
40 |
|
41 |
If we take the webserver examples: |
42 |
The software is under /usr |
43 |
The configuration is under /etc/apache |
44 |
|
45 |
If I update apache and there are additional options and/or changes to the |
46 |
config files, how do I migrate those to all the different nodes? |
47 |
If the config is the same on all nodes, why not simply share the " / " ? |
48 |
If it differs, I then need to write down all the new options and go through |
49 |
every single node and update the config there. |
50 |
|
51 |
The same is true with any other environment where multiple nodes are used for |
52 |
the same purpose. |
53 |
|
54 |
For the usecases that I generally deal with, the only time where a shared /usr |
55 |
would make sense is when I select " Install everything " during the install. |
56 |
I used to do that to avoid having to deal with RPM-dependencies when I was |
57 |
using Redhat. |
58 |
|
59 |
-- |
60 |
Joost |