summaryrefslogtreecommitdiffstats
path: root/share/examples/diskless/ME
diff options
context:
space:
mode:
Diffstat (limited to 'share/examples/diskless/ME')
-rw-r--r--share/examples/diskless/ME45
1 files changed, 32 insertions, 13 deletions
diff --git a/share/examples/diskless/ME b/share/examples/diskless/ME
index 1179d64..85178e0 100644
--- a/share/examples/diskless/ME
+++ b/share/examples/diskless/ME
@@ -1,18 +1,37 @@
-When templating, ME is typically a softlink to the appropriate host
-subdirectory. This softlink is different for each machine and
-should not be updated by the template process. Any system-wise configuration
-file that needs to be personalized is typically turned into a softlink
-through /conf/ME. For example, /etc/rc.conf.local would be turned into a
-softlink pointing to /conf/ME/rc.conf.local.
+When templating, /conf/ME is typically a softlink to
+/conf/<appropriate-machine>. When doing a diskless boot, /conf/ME is
+retargeted by /etc/rc.diskless1 from pointing to the server to pointing
+to the client's directory, /conf/<ip-address-of-client>. The retargeting
+is accomplished through an MFS -o union mount.
-On any given machine, ME is typically a link to the hostname which also
-exists as a subdirectory in the /conf directory. So, for each machine you
-do:
+When templating, this softlink should be different for each machine.
+When doing a diskless boot, this softlink is typically part of the / NFS
+mount from the server and points to the server's conf directory, but gets
+retargeted during the /etc/rc.diskless1 phase.
- cd /conf
- ln -s this_machines_name ME
+System-wide configuration files must generally be targeted through /conf/ME.
+For example, your /etc/rc.conf.local should become a softlink to
+/conf/ME/rc.conf.local and your real rc.conf.local should go into the
+appropriate /conf/<appropriate-machine> directory. This is also true of
+/etc/rc.local, /etc/fstab, /etc/syslog.conf, /etc/ccd.conf, /etc/ipfw.conf,
+/etc/motd, /etc/resolv.conf, and possibly even /etc/ttys ( if you want
+to start an X session up on boot on certain of your machines ).
+
+When templating, you duplicate your / and /usr partitions on each machine's
+local disk from a single master ( assuming /var and /home reside elsewhere ),
+EXCEPT for the /conf/ME softlink. The /conf/ME softlink is the only thing
+on / that should be different for each machine.
+
+There are often categories of configuration files. For example, all of your
+shell machines may use one resolv.conf while all of your mail proxies may
+use another. Configuration files can be categorized fairly easily through
+/conf/HT.<category> directories. You put the actual configuration file in
+/conf/HT.<category> and make a softlink from
+/conf/ME/<appropriate-machines>/config-file to "../HT.<category/config-file".
+This means that access to these files tends to run through more then one
+softlink. The advantage is that for all the complexity of your /conf
+directory hierarchy, most of your common config files exist in only one place
+in reality.
-The ME link is not used with diskless booting. It is designed for templating
-where each destination box has its own local disk.
OpenPOWER on IntegriCloud