|author||Kylie McClain <firstname.lastname@example.org>||2020-07-10 08:37:10 -0400|
|committer||Kylie McClain <email@example.com>||2020-07-10 08:37:10 -0400|
mutiny(7): get rid of "Documentation section", it rambles
1 files changed, 2 insertions, 17 deletions
diff --git a/mutiny.7.adoc b/mutiny.7.adoc
index 1a1194b..3f55c7f 100644
@@ -60,23 +60,8 @@ endif::
reference external websites in order to learn about it. Documentation should be consistent,
too. On *Mutiny*, all documentation should be accessible through *man* or _/share/doc_.
-The state of system administration nowadays can be very fragmented. Most people just search for the
-documentation online nowadays, finding the manuals to be lacking, or just too archaic.
-However this is rarely a problem with *BSD systems. This is because BSD systems, historically, have
-put more emphasis on good documentation of their systems. Every single aspect of the kernel's
-internals, drivers, quirks, etc., is documented in a manpage.
-On a large scale, this unity in the system is what Mutiny is striving for. Linux systems have had a
-tendency to be disjointed at times, as the model which the system is developed in doesn't usually
-correspond to the stewardship that comes with the tightly-managed attitude of something like
-Manual pages will be required for any package that installs a program to _/bin_, and in all files in
-_/etc_ will also require manual pages to exist for them.
+ Manual pages will be required for any package that installs a program to _/bin_, and in all
+ files in _/etc_ will also require manual pages to exist for them.
=== Standards adherence