From 8b340beca42cc3a2de1df49d42f1f0253ba185ef Mon Sep 17 00:00:00 2001 From: Peter Boy Date: May 11 2021 14:32:00 +0000 Subject: Some minor modifications on already existing content --- diff --git a/docs/modules/ROOT/pages/server-administration.adoc b/docs/modules/ROOT/pages/server-administration.adoc index 66a966c..cc65161 100644 --- a/docs/modules/ROOT/pages/server-administration.adoc +++ b/docs/modules/ROOT/pages/server-administration.adoc @@ -34,19 +34,3 @@ Fedora Server Edition is designed as a headless device, i.e. without a graphical Typically, however, administration is done remotely via a secure SSH connection. In addition, a lightweight web-based graphical user interface, Cockpit, is available by default and is intended to simplify many typical and repetitive maintenance tasks. For example, the creation, formatting and mounting of a logical file area can be done with a short input form consisting of 3-4 topics and one click. This saves even the experienced system administrator a lot of time and the (error-free) typing of several command lines. - - - - -== Comming Up Next - -- Manage storage - -- SELinux, don't deactivate but resolve issues (link to cockpit SELinux page and description how to resolve on CLI (or link)) - -- Ansible, would be nice to offer some configurable Ansible scripts for those repetitive tasks (downloadable from server-wg home page) -* links to existing script at GitHub system roles and a guide how to use that script for this purpose - - - -More topics of this kind to be added diff --git a/docs/modules/ROOT/pages/server-faq.adoc b/docs/modules/ROOT/pages/server-faq.adoc index aca6a19..ae7841e 100644 --- a/docs/modules/ROOT/pages/server-faq.adoc +++ b/docs/modules/ROOT/pages/server-faq.adoc @@ -16,3 +16,5 @@ Can I see a built preview of this template to get a better idea about the result Of course you can! Just look at the README of the repository — it should tell you everything. Is writing documentation hard and dreadful?:: Absolutely not (OK, just joking). Writing documentation in asciidoc is very simple and straightforward. And in fact, writing documentation makes you very happy. Just try and see for yourself! +How do I manage SELinux issues?:: + First of all: Don’t deactivate but resolve issues - (Link to Server Sysadmin Cockpit page and Quick Docs) \ No newline at end of file diff --git a/docs/modules/ROOT/pages/server-troubleshooting.adoc b/docs/modules/ROOT/pages/server-troubleshooting.adoc index bd32880..af40804 100644 --- a/docs/modules/ROOT/pages/server-troubleshooting.adoc +++ b/docs/modules/ROOT/pages/server-troubleshooting.adoc @@ -17,6 +17,9 @@ Some examples from the latest discussions 1. The well known BIOS boot partition issue 2. systemnd-oomd and httpd / jBoss/wildfly 3. UEFI – one ESP for /boot/efi requirement in software RAID 1 / RAID x +4. How manag SELinux issues - Link to Quick docs and to Cockpit SELinux page ++ +Specifically: don’t deactivate but resolve issues ### Some generic information