memory-leaks

commit d7fa0c895d3e4827e0be330a6479070e24b798cf
parent 56f6674b05114da3de105d261c979f9d5a87639a
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sun,  9 Mar 2025 11:17:44 +0100

Perform morning routine

* brew coffee
* jot down results of the previous day
* sip coffee
* google something on a hunch
* shake head in disbelief

Diffstat:
M
guides/sysadmin/machines/amdahl30/killing-time.org
 | 
5
+++++

1 file changed, 5 insertions(+), 0 deletions(-)
diff --git a/guides/sysadmin/machines/amdahl30/killing-time.org b/guides/sysadmin/machines/amdahl30/killing-time.org
@@ -524,6 +524,11 @@ Then confirmed absence of strays with ~zypper packages~ (with
         Windows cruft
       - "System → Storage → Cleanup recommendations" agrees we can
         reclaim the 7 GB =Windows.old=
+**** and then
+The Kingston utility thingy does not identify the disk 🤷 moving on
+** XFS?
+interacts badly with the GPU?
+https://bugzilla.kernel.org/show_bug.cgi?id=202349
 * This is insane
 Selected subset of moving parts; "testability" considering ease of
 clean reverts: