Aargh, tuo kumivenesimulaattori!
Aargh, tuo kumivenesimulaattori! Kun Tietomaassa viimeksi käydessäni kokeilin sitä, en keksinyt kuinka se pysäytetään, joten piti sitten vain kavuta sieltä varovaisesti pois, vaikka se yhä huojui aallokossa.
Aargh, tuo kumivenesimulaattori! Kun Tietomaassa viimeksi käydessäni kokeilin sitä, en keksinyt kuinka se pysäytetään, joten piti sitten vain kavuta sieltä varovaisesti pois, vaikka se yhä huojui aallokossa.
If I caught that correctly, this ”Sam Spade” character referred to the Taco Bell incident occurring ”the day before [Eric’s] death”. Assuming this is true, it would imply that the poster knew the exact day that Eric died, when even the authorities appear to have no such knowledge (due to uncertainty resulting from the state of decomposition). While the poster’s truthfulness in general is questionable, this embedded implication about their knowledge could be a Freudian slip.
Output from procps’ ps with -e only produces the process name, so grepping for ”cli.js start” fails every time. This change adds (POSIX-compliant) -f to all ps calls to get the full command. AWK print parameter is adjusted accordingly where needed.
Issue #1359 resulted in PR #1370, but only addressed the stop: target. The changes here address the rest of the ps calls the same way.
I’m unfamiliar with ThinLinux, but is there a good reason you cannot use your desktop environment’s settings application to adjust display settings? The wiki article is quite old, and while some of it may still be valid, display detection and GUI settings tools have improved over the years. Those tools should be the preferred method of adjusting settings, barring exceptions such as brand new hardware with lacking support.