From 84cd2765172d65c486e1863a18b635d2a54a3e75 Mon Sep 17 00:00:00 2001
From: surister <surister98@gmail.com>
Date: Fri, 29 Nov 2019 12:53:41 +0100
Subject: [PATCH] new linuxs answers

---
 README.md | 25 +++++++++++++++++++++----
 1 file changed, 21 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index ea049f5..6915e01 100644
--- a/README.md
+++ b/README.md
@@ -800,7 +800,22 @@ TCP establishes a connection between the client and the server to guarantee the
 
 <details>
 <summary>Running the command <code>df</code> you get "command not found". What could be wrong and how to fix it?</summary><br><b>
-</b></details>
+</b>
+<p>
+Most likely the default/generated $PATH was somehow modified or overridden thus not containing <code>/bin/</code> where df would normally go.
+This issue could also happen if bash_profile or any configuration file of your interpreter was wrongly modified, causing erratics behaviours.
+You would solve this by fixing your $PATH variable:
+
+As to fix it there are serveral options:
+
+1. Manually adding what you need to your $PATH <code>PATH="$PATH":/user/bin:/..etc</code> 
+2. You have your weird env variables backed up.
+3. You would look for your distro default $PATH variable, copy paste using method #1
+
+Note: There are many ways of getting errors like this: if bash_profile or any configuration file of your interpreter was wrongly modified; causing erratics behaviours,
+permissions issues, bad compiled software (if you compiled it by yourself)... there is no answer that will be true 100% of the time.
+</p>
+</details>
 
 <details>
 <summary>How to make sure a service will start on a OS of your choice?</summary><br><b>
@@ -816,8 +831,7 @@ With cron, tasks are scheduled using the following format:
 
 <minute> <hour> <day of month> <month> <day of week> <command to execute>
 
-The tasks are stored in a cron file.
-
+The tasks are stored in a cron file, you can write in it using <code>crontab -e</code>
 
 Alternatively if you are using a distro with systemd it's recommended to use systemd timers.
 
@@ -828,6 +842,8 @@ Alternatively if you are using a distro with systemd it's recommended to use sys
 
 Normally you will schedule batch jobs.
 
+
+
 </b></details>
 
 ##### Permissions
@@ -1072,10 +1088,11 @@ execution or run forever
 
 <details>
 <summary>What signal is used when you run 'kill <process id>'?</summary><br><b>
-
+<pre>
 The default signal is SIGTERM (15). This signal kills
 process gracefully which means it allows it to save current
 state configuration.
+</pre>
 </b></details>
 
 <details>