From 23991199e89a332d8adcf911785e10c6b89ba873 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sol=C3=A8ne=20Rapenne?= <solene@perso.pw>
Date: Wed, 13 Sep 2023 10:48:09 +0200
Subject: [PATCH] shell tip #14

---
 issues/issue-14/10_en.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/issues/issue-14/10_en.html b/issues/issue-14/10_en.html
index 3eba1ba..a00e071 100644
--- a/issues/issue-14/10_en.html
+++ b/issues/issue-14/10_en.html
@@ -61,7 +61,14 @@
 <article id="tips">
 <div class="puffies" aria-hidden="true">🐡🐡🐡</div>
 <h2>Shell tips</h2>
-<p></p>
+<p>Know your processes! The <code>ps</code> command can actually provide a lot of information about processes running on your system. Per the man page, in the <code>state</code> column, letters are used to indicate some important information about the processes.</p>
+<ul>
+    <li><code>c</code> indicates that the process is running in a chroot</li>
+    <li><code>p</code> tells the process has called pledge() (but not which promises were used)</li>
+    <li><code>U</code> shows the process has called unveil() and can't unveil() new paths/files anymore</li>
+    <li><code>u</code> shows the process has called unveil() but it's not locked. It's most likely an issue with how unveil() has been added in the program!</li>
+    <li><code>X</code> will remind you that you are currently tracing/debugging the process, in case you forgot</li>
+<p>Of course, there are many other states, I encourage you to read <code>ps(1)</code> man page to know about all the features it provides.</p>
 </article>
 
 <article id="links">