andrew/disco
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

more readme

Browse Source
This commit is contained in:
Andrew Kesterson
2012-08-05 22:34:08 -04:00
parent 4d50e5736f
commit e8f39c7582
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -243,11 +243,13 @@ DISCO is a work in progress so not all of it is complete, but the general idea i
- report overall success or failure (any piece of any module failing indicates failure)
DISCO is able to easily report all differences by executing all scripts and templates inside a
restricted bash execution environment, and on top of a read-only unionfs with a scratchpad on
the top. If the NOOP flag is set, then all the same operations are performed, but the restricted
environment stops all potentially dangerous commands at the reporting level, and the fetched files
are not merged out of the scratchpad onto the live filesystem. The scratchpad is also not merged if
there is a failure during live (non-NOOP) execution, to prevent from locking the system in a
non-functioning state.
restricted bash chroot, and on top of a read-only unionfs with a scratchpad on the top,
some custom twiddly bits in the middle, and the existing running filesystem at the bottom (read-only).
The scratchpad is not merged if there is a failure during live (non-NOOP) execution, to prevent
from locking the system in a non-functioning state.
If the NOOP flag is set, then all the same operations are performed, but the restricted
environment stops all potentially dangerous commands at the reporting level (presumably), and
the fetched files are not merged out of the scratchpad onto the live filesystem.
See the client disco-fs-* and disco-exec-* scripts for more information on how this is done.