Hi!
On Fri, Dec 08, 2006 at 02:08:29PM +0000, Ronan Mullally wrote:
> There are several very good reasons for using a remote-mounted /usr:
>
> - You can mount it read-only so it can't be modified
Local /usr also can be mounted read-only.
> - You can easily 're-task' a server by changing what it mounts
Re-task?! /usr usually contains binaries and data suitable for all tasks
so to re-task you should change what and how you execute on that server,
not /usr.
> - Your data is easier to update
Yeah, I've already agreed with this point. But I don't think it's so
important just because in addition to /usr you should update /etc which is
different on different servers and which is much more painful to update.
> - Your data is easier to backup
Backuping /usr is senseless operation in many cases. But in other cases if
you mount /usr read-only and sure it's same on all servers you can backup
single /usr from _any_ server, just like in case with single remote /usr.
> If I've got more than 3 or 4 servers to manage in a deployment I typically
> use remote-mounted root and /usr filesystems - it makes life an awful lot
> easier.
If you remote-mount root (using network boot?), /usr and everything else ;-)
than that's really can make life much easier, but this setup has nothing
with current topic. I'm asking about configuration where you may boot with
root but without /usr - that's why /etc/localtime symlink replaced by copy
of timezone file, grep compiled without perl regex support, etc.
--
WBR, Alex.
--
[email protected] mailing list
