| 1 |
Hi! |
| 2 |
|
| 3 |
On Fri, Dec 08, 2006 at 02:08:29PM +0000, Ronan Mullally wrote: |
| 4 |
> There are several very good reasons for using a remote-mounted /usr: |
| 5 |
> |
| 6 |
> - You can mount it read-only so it can't be modified |
| 7 |
|
| 8 |
Local /usr also can be mounted read-only. |
| 9 |
|
| 10 |
> - You can easily 're-task' a server by changing what it mounts |
| 11 |
|
| 12 |
Re-task?! /usr usually contains binaries and data suitable for all tasks |
| 13 |
so to re-task you should change what and how you execute on that server, |
| 14 |
not /usr. |
| 15 |
|
| 16 |
> - Your data is easier to update |
| 17 |
|
| 18 |
Yeah, I've already agreed with this point. But I don't think it's so |
| 19 |
important just because in addition to /usr you should update /etc which is |
| 20 |
different on different servers and which is much more painful to update. |
| 21 |
|
| 22 |
> - Your data is easier to backup |
| 23 |
|
| 24 |
Backuping /usr is senseless operation in many cases. But in other cases if |
| 25 |
you mount /usr read-only and sure it's same on all servers you can backup |
| 26 |
single /usr from _any_ server, just like in case with single remote /usr. |
| 27 |
|
| 28 |
> If I've got more than 3 or 4 servers to manage in a deployment I typically |
| 29 |
> use remote-mounted root and /usr filesystems - it makes life an awful lot |
| 30 |
> easier. |
| 31 |
|
| 32 |
If you remote-mount root (using network boot?), /usr and everything else ;-) |
| 33 |
than that's really can make life much easier, but this setup has nothing |
| 34 |
with current topic. I'm asking about configuration where you may boot with |
| 35 |
root but without /usr - that's why /etc/localtime symlink replaced by copy |
| 36 |
of timezone file, grep compiled without perl regex support, etc. |
| 37 |
|
| 38 |
-- |
| 39 |
WBR, Alex. |
| 40 |
-- |
| 41 |
gentoo-server@g.o mailing list |
Archives