TIL about the leave command
#POSIX
LXQT has coded a point release of LXQT-config
Go and fetch it on GitHub
#LXQT #LXQT_config #programming #OpenSource #Linux #UI #Xorg #Wayland #POSIX
https://lxqt-project.org/release/2026/01/29/point-release-lxqt-config-2-3-1/
To those who use Linux or other POSIX-compatible system: What was your first OS?
Mine was Ubuntu 8.04 Hardy Heron. It was quiet a lot of fun those days, and it was kinda cool to get the CD from local Ubuntu community.
How about you?
#Linux #POSIX #UNIX #BSD #OS #OperatingSystem #OpenSource #FOSS
An amazing amount of work has been done to polish and bug squash my favorite photo editor
Feast yourself upon the updates of Gimp v3.0.8
#photo #editor #GIMP #bash #csh #ksh #zsh #fish #sh #OpenSource #Linux #Mac #programming #technology #POSIX
Current weather for Kwamalasemutu SR / SA
A gorgeors place where you can meet and interact with natur up close and personal
#Weather #curl #wttr #bash #csh #ksh #zsh #fish #sh #OpenSource #programming #technology #Mobile #POSIX
Current weather in Leonsberg SR/SA with the power of wttr.in *sh curl and lolcat
Avoid using prt 80 when aded the server may return a 0 status not respond
#Weather #curl #wttr #bash #csh #ksh #zsh #fish #sh #OpenSource #programming #technology #Mobile #POSIX
Current weather in Palmentuin SR / SA
compliments of wttr.in curl *sh and lolcat
#Weather #curl #wttr #bash #csh #ksh #zsh #fish #sh #OpenSource #programming #technology #Mobile #POSIX
Is it possible to temporarily increase the niceness of a process (i.e. lower its scheduling priority), then later increase it again to the original value, from within the process?
Every approach I try seems to require `CAP_SYS_NICE` or a very loose `ulimit -e`, and given that I just want to make the process nicer for a bit, and then set it back to its previous niceness, this seems like too big a restriction.
What am I missing?
(I have tried setpriority(), nice() and sched_setparam())
Sometimes devil is in the details. #POSIX requires option parsing to terminate when the initial non-option argument is encountered. This is different than the #GNU style which continues parsing arguments until an explicit "--" is encountered. The latter has been susceptible to command line injection attacks. One recent example is in #bubblewrap & #flatpak combo with CVE-2024-32462. Otoh, #sydbox and all its utilities use posixly correct option parsing: https://nvd.nist.gov/vuln/detail/cve-2024-32462 #linux #security
I directly use mainly :bash: GNU Bash, as it's :gnu: default one, but nevertheless I try hard to avoid bashisms, writing scripts compatible with any POSIX-compliant shell and tools. :sh:
CC: @vavakado@mas.to
#GNU #bash #Bourne #POSIX #UNIX #shell
CC: @vavakado@mas.to
#GNU #bash #Bourne #POSIX #UNIX #shell
[lien] A static site generator written in POSIX shell - Lobsters (aashvik.com by aashvik) #posix #gik #net #cli
Weather in Marienburg SR SA image build the following way:
* photograph composition
** location districk of Commewijne
** object een sluis (NL)
* shell bash
** sh ksh zsh sh fish will do fine
* server wttr.in
* fecth program curl
* formatting program lolcat
* composed with Love for all who read this
#Weather #curl #wttr #bash #csh #ksh #zsh #fish #sh #OpenSource #programming #technology #POSIX
Current weather in Leonsber SR SA
Compliments of witte curl *sh lolcat
#Weather #curl #wttr #bash #csh #ksh #zsh #fish #sh #OpenSource #programming #technology #POSIX
JuiceFS is a distributed POSIX file system built on top of Redis and S3
https://github.com/juicedata/juicefs
#HackerNews #JuiceFS #Redis #S3 #distributed #file #system #POSIX
Preparing an engineering-focused presentation entitled "The Zen of Shell Scripting" for an internal talk at work. Question for seasoned Shell programmers: What would you have liked to know when you first started out? Interested in both big ideas and sharp edges that come with Shell scripting.
Ceci n'est pas une pipe: |
Linux distribution for DSC Damn Small Computers
God, why is #vi(1) so opinionated? Like, really, it implies that one writes code in #C (because https://aartaka.me/better-word.html) and composes docs and navigates them in troff macros (see sections configuration option in ex/vi manual.) There’s simply no discourse and option for different use of vi than that. Even in #POSIX, where the reference implementation behavior was pretty much copied and cryopreserved.
#ed(1) just doesn’t care. It only cares about lines and it doesn’t ever want to mandate a thing on you. Want to do #Lisp in ed? Sure, go ahead: https://aartaka.me/lisp-lines.html Want to use it as a task runner? Why not? https://aartaka.me/customize-ed-2.html#ide
Don’t use restrictive and overly opinionated tech. Use tech that accepts you as you are. Use ed(1)
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst