Bug#592564: document unusual but supported file system configurations
On Wed, 11 Aug 2010 at 09:28:22 +0200, Carsten Hey wrote:
> Read-only mounting /etc seems to imply that it can also be on a separate
> file system (although I never saw such a setup)
Doesn't work: to boot and mount /etc you need /etc/fstab and /etc/init.d/* and
so on, for which you need /etc. I don't think we (should) support having a
minimal /etc that gets replaced by a larger /etc mounted over the top.
You can achieve a read-only /etc by (re)mounting / read-only, as long as all
filesystems that have to be writeable (/tmp, /var) are external. In a system
with a read-only / you'd typically have /tmp as a tmpfs and /var on another
partition, I think?
Some other useful configurations for separate filesystems include:
* /tmp on tmpfs (does d-i do this by default now?)
* /var/cache (offloaded to somewhere large and/or fast but not backed up)
* /var/log (so that logfiles can't fill /)
* user files (/var/www, /srv, /home)