... | ... | @@ -6,15 +6,11 @@ hostname. When it asks about optional components, only select "lib32" and |
|
|
"src", you do not want "ports" since you will be loading pre-built packages
|
|
|
from Emulab.
|
|
|
|
|
|
When it asks about partitioning the disk, choose "Auto (UFS)". It will
|
|
|
identify all the disks on the machine and ask which you want to install
|
|
|
FreeBSD on. Select the first disk and "Entire Disk". Proceed with the remainder
|
|
|
of the install.
|
|
|
Next it will ask you about partitioning. There are a variety of ways to partition disk space depending on how many disks the server has and whether you might want to enforce space quotas.
|
|
|
|
|
|
Before partitioning, note that the following directories will need to exist
|
|
|
on partitions that have enough space to hold them:
|
|
|
An Emulab install has several directory hierarchies that it uses:
|
|
|
|
|
|
* **/usr/testbed/** Needs space for testbed software and logs. 10-50GB should be enough.
|
|
|
* **/usr/testbed/** Space for testbed software and logs. 10-50GB should be enough.
|
|
|
|
|
|
* **/share/** Exported read-only to all nodes. We use it for providing experimenters with the source for the FreeBSD and Linux versions we run as well as common packages. This could require anything from 1GB to 20GB+ depending on what you want to make available. This directory must exist as a distinct filesystem, but most sites don't use it and you can likely keep it small.
|
|
|
|
... | ... | @@ -30,6 +26,12 @@ However, you may want to enforce quotas on them. This is the main reason you'd w |
|
|
|
|
|
Note that since `/share` is exported read-only, FreeBSD requires that it be on a separate filesystem from anything that is exported read-write. So while `/users, /proj` and `/groups` can be on the same filesystem, `/share` cannot.
|
|
|
|
|
|
When it asks about partitioning the disk, choose "Auto (UFS)". It will
|
|
|
identify all the disks on the machine and ask which you want to install
|
|
|
FreeBSD on. Select the first disk and "Entire Disk". Proceed with the remainder
|
|
|
of the install.
|
|
|
|
|
|
|
|
|
Make sure that no matter how you decide to partition things up, you make symbolic links to the appropriate places. For example, if you make one big filesystem called `/z` that has `/users, /proj,` and `/groups` in it, make sure you:
|
|
|
|
|
|
```
|
... | ... | |