A properly initialized root partition.
can help in creating it, using the servers root partition
as a reference.
If you are just starting out, you should
simply use the servers own root directory,
and not try to clone it.
You often do not want to use the same
files for the
boot as you do on the server.
scripts provide a mechanism through which you can override various files
(as well as other subdirectories of root).
One difference that you should pay particular attention to is
the value of
A typical value for a
however your needs may be different.
The scripts provide four
overriding directories situated in
You should always create
which will entirely replace the servers
You can clone the servers
here or you can create a special file which tells the
to remount the servers
You do this by creating the file
containing the mount point to use as a basis of the
For example, the file might contain:
Alternatively, if the server contains several independent roots, the file
This would work, but if you copied
and upgraded the installation, you would need to modify the
files to reflect that move.
To avoid that, paths in
files beginning with
have the actual path of the clients root prepended to them so the file
could instead contain:
scripts create memory file systems to hold the overridden
Only a 2MB partition is created by default, which may not
be sufficient for your purposes.
To override this, you can create the
containing the size, in 512 byte sectors, of the memory disk to create
for that directory.
You then typically provide file-by-file overrides in the
At a minimum, you must provide overrides for
Overrides are hierarchical.
You can supply network-specific defaults
represents the broadcast IP address of
system as given to it via
features work in any of these directories.
The configuration feature works on directories other then
you simply create the directory you wish to replace or override in
and work it in the same way that you work
Since you normally clone the servers
you might wish to remove unneeded files from the memory file system.
if the server has a firewall but you do not, you might wish
You can do this by creating a
which contains a list of relative paths that the boot scripts should remove
from the memory file systems.
As a minimum, you normally need to have the following in
<SERVER>:<ROOT> / nfs ro 0 0
<SERVER>:/usr /usr nfs ro 0 0
You also need to create a customized version of
which should contain
the startup options for the
which could be empty but prevents the servers own
from leaking onto the
you will not need to set
because these will be already set by the startup code.
Finally, it might be convenient to use a
as the switch variable to do machine-specific configuration
in case a number of
clients share the same configuration