|
|
@ -1,5 +1,6 @@ |
|
|
|
The overlay-boot Project |
|
|
|
======================== |
|
|
|
= The overlay-boot Project |
|
|
|
:author: Ralph Ronnquist |
|
|
|
:revdate: Sun, 30 Apr 2023 23:46:31 +1000 |
|
|
|
|
|
|
|
The *overlay-boot* project implements a "minimalist approach" for |
|
|
|
dividing a single host into "subhosts" for administratively separated |
|
|
@ -30,8 +31,7 @@ framework. |
|
|
|
including the trivial case of "no services" (as is necessary for |
|
|
|
installing and configuring the service or services of a subhost). |
|
|
|
|
|
|
|
A usage example (minimal) |
|
|
|
------------------------- |
|
|
|
== A usage example (minimal) |
|
|
|
|
|
|
|
A subhost is techincally defined as a directory that contains three |
|
|
|
mount points "work", "root" and "live", and a configuration file with |
|
|
@ -72,8 +72,7 @@ The subhost environment may be "entered" with |
|
|
|
---- |
|
|
|
==== |
|
|
|
|
|
|
|
Another usage example (MTA) |
|
|
|
--------------------------- |
|
|
|
== Another usage example (MTA) |
|
|
|
|
|
|
|
This is an example setup at +/opt/mta+ of a larger overlay subhost |
|
|
|
for an MTA as primary service and with some additional useful |
|
|
|