aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristos.K <freedomrfox@gmail.com>2017-08-28 19:40:56 +0300
committerChristos.K <freedomrfox@gmail.com>2017-08-28 19:40:56 +0300
commit6fe716542c99d85e0985eb7c2ca00a0298bb12d3 (patch)
tree791309572a2c8a785418e7ead8917247b32c6aff
parentNot used (diff)
downloadGSE-6fe716542c99d85e0985eb7c2ca00a0298bb12d3.tar.gz
GSE-6fe716542c99d85e0985eb7c2ca00a0298bb12d3.tar.bz2
GSE-6fe716542c99d85e0985eb7c2ca00a0298bb12d3.zip
Included Warning
-rw-r--r--README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.md b/README.md
index a3f759a..bd79251 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,8 @@ A stateless environment based on Gentoo, which aims on making the
maintenance of multiple machines easier, improve stability and usability
on environments like Research or University computer labs.
-
+#### Before you go on
+ Warrning: This project is currently experimental. It's on alpha stage, therefore it is recommended to be used only for testing, on enviroments that shield important data from the project's actions.
## An introduction to the stateless concept
To begin with, a stateless system, as a concept, is an operating system which can boot and operate without requiring to hold a “memory” of its last state. However, even as a concept, this raises many questions, and could make sceptical even someone which has spend a little time reading about the operation of Linux. That is because, such a system would have many operational restrictions. First of all, the system would be “frozen in time”, meaning that every time the system boots, is like booting for the first time, because no inner “advancement” is happening, that is, no previous timeline of changes and configurations exists.