Is there a way to get username from uid using only #POSIX utilities? If no, I'll think about sending a proposal to POSIX to add a new flag to id for that.

@alfonsosiciliano

Is there a reason you didn't use syscall.master to parse instead? (Or maybe you did and the blog is slightly wrong?)

https://cgit.freebsd.org/src/tree/sys/kern/syscalls.master

#UNIX #POSIX #BSD #FreeBSD #coding #C #Opensource #OS #kernel #syscall

New blog post: "FreeBSD 15 System Calls Table".

https://alfonsosiciliano.gitlab.io/posts/2023-08-28-freebsd-15-system-calls.html

#UNIX #POSIX #BSD #FreeBSD #coding #C #Opensource #OS #kernel #syscall

About locales and standards (e.g. environment variables LC_*), a rant:

https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f027338b0fab0f5078971fbe

#posix

@hnygd @Codeberg@social.anoxinon.de Thank you all for your replies!

At the moment I am using a self developed solution around #newstow (or #nstow, https://github.com/adam-gaia/new-stow), a templated system of #POSIX shell scripts and a self-hosted git instance (#GITEA).

Works good, but I am alway looking for the next level of automation.

@hnygd I will have a deeper look into your #ansible scripts. Thanks for sharing!

I had a long conversation with @requiem and he helped me be OK with admitting this to myself and others.

I think #POSIX sucks and we could do better if we moved on from it.

@b0rk_reruns
Thanks, but I'd rather keep using that non #posix features of that awful shell that is #bash 😁
@alcinnz

Testing sudo-rs and improving sudo along the way, https://ferrous-systems.com/blog/testing-sudo-rs/.

sudo-rs is a re-implementation of sudo in Rust. While testing sudo-rs, they have found several inconsistencies in the specification, and found 2 bugs in the original sudo implementation.

This test suite can run on both implementations.

Link to sudo-rs: https://github.com/memorysafety/sudo-rs.

#sudo #posix #unix #test #safety #security #RustLang

Sabias que para el 19-01-2038 a las 03:14:07 (UTC) los contadores de la hora en sistemas POSIX de 32 bits llegara a su limite? Luego de eso, estos contadores se reiniciarían volviendo al año 1901. Puede traer problemas en maquinaria pesada, sistemas embebidos, aviones y muchos componentes. Por esto se tienen que actualizar a sistemas de 64 bits, retrasando este problema.

#VidaInformatica #Informatica #sistemas #32bits #limite #software #posix #64bits #linux #windows #unix #tecnologia

@nixCraft AFAIK
#Busybox were created to slim down disk occupation of basic #POSIX commands and it achieved this design goal very efficiently.
#Systemd has some controversial design choices but as others has already pointed out when used wisely is a good tool

Project of the day: pax archive utility, aka #POSIX endorsed #tar replacement: https://github.com/michaelforney/pax

Does anyone know how you get `sort` to work the same on #Linux and #macOS? (and ideally other #POSIX/#UNIX like platforms)

Should `sort -f` to case-fold be enough? That seems to at least exist in both macOS and Linux.

I feel like ideally, I'd just have it sort "ASCIIbetical" order, i.e sort based on the byte values, like what `strcmp` would do. But there doesn't seem to be a standard flag for that.

@pmj https://stackoverflow.com/questions/729692/why-should-text-files-end-with-a-newline

Stichwort #POSIX und line termination. Die Zeile ist eigentlich gar nicht da ;)

I mean … DANG!

#iOS #Unix #POSIX #Perl

I'm super impressed with `a-Shell` and `a-Shell mini` for #iOS. Having a POSIX shell environment on my iPad is amazing.

Several shell scripts I authored on my iPad using a-Shell's port of dash shell in POSIX mode worked as-is (sans the shebang line) when I ran them in bash on my Mac Mini.

🔜 trying out the #lua and #perl ports

https://holzschu.github.io/a-Shell_iOS/

https://github.com/holzschu/a-shell

#POSIX #Unix

[1] also:impressed "and by extension I'm impressed with WebAssembly. Wow."

@alexis This is a mood.

Image source (artist unknown): https://derpibooru.org/images/236967

#TwilightSparkle #POSIX #shell #Linux #Android #command #terminal #manual @pony@chirp.social @pony@a.gup.pe

TIL: If you write to a closed socket in #posix, your process receives SIGPIPE, whose default action is to kill your process.

Why???? The write() call communicates failure by returning 0 or -1 or whatever. Does it really need to also abort the process?

@benjamineskola @unfortunateshort @josephholsten @fuchsiii I mean, I know that #zsh is seen as more or less "the best #POSIX #sh compatible shell there is"...

I think #fish really shines at the user experience when interacting directly with it.

@nixCraft that is actually true...

Unless someone provides a program with #root #privilegues it can only mess up the $HOME of the user account which it runs under.

This is why the default config for servers like #Apache and #PostgreSQL to literally be run as #daemons or rather #systemD services under dedicaded user accounts, so a webserver - even when hacked - can't f**k up the system.

It's part of the #KISS-Approach to #Users and #Groups in #POSIX and is supplemented with #AppArmour...

I wonder why #linux and other #POSIX systems accept NUL-terminated strings in their underlying system calls like open and mkdir? Why not just accept pointer + length instead and make life easier for programming languages that have native string type with length builtin?