removing the junk.

[Bruce Cran]

On Tue, 22 Jun 2010 17:24:29 +0100
Bruce Cran <bruce at cran.org.uk> wrote:

> On Tue, 22 Jun 2010 08:47:21 -0700
> Devin Teske <dteske at vicor.com> wrote:
> 
> > Please-oh-please don't remove ability to install via NFS.
> 
> No, I think it's just referring to the post-install setup of a machine
> as an NFS client.  We're just discussing sysinstall on IRC at the
> moment and have come up with the idea of asking what role the machine
> will be and choosing appropriate settings. So, for example:
> 
> Default layout:
> 
> 1GB /
> 2x RAM swap up to 2GB RAM, and then 1x RAM
> 1GB /tmp
> 4GB /var
> [rest of drive] /usr
> 
> Desktop:
> 
> Default layout
> 
> Database server:
> 
> Allocate 16GB to /usr and leave the rest for /var
> Ask if the user wants to install MySQL or Postgresql (?)
> 
> NFS server:
> 
> Same layout as for Desktop but enable NFS. Or should we give 16GB
> to /usr and leave the rest unallocated? I don't know enough about how
> NFS servers are setup.
> 
> We *could* also choose appropriate packages similar to what Debian
> does, but that's probably a step too far for FreeBSD.
> 

Just to clarify, I've had some more feedback. A server should have:

1GB /
1GB /tmp
40% /var
rest to /usr

And a database server should have 50-60% allocated to /var, and the
rest for /usr - and no hard cap on the size of it because by
default /home will live there too.

Also, on 32-bit architectures swap should probably take up any address
space not used by RAM (i.e. with 512MB RAM give 3.5GB swap, 2GB RAM and
2GB swap etc.) while on 64-bit platforms we could just allocate the
same amount for swap as there is RAM unless the machine has 1GB or
less in which case we allocate twice the maount of swap as the machine
has RAM.

-- 
Bruce