fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#syscalls

0 posts0 participants0 posts today

🤔 Oh, you wanted to know where the #bytes go? Well, let's take a thrilling tour through the #labyrinth of #syscalls, because nothing screams excitement like relentless file paths and arcane #assembly #language. 🚀 Spoiler alert: it's all gloriously tedious, but don't worry, your bytes are probably somewhere safe... or not. 🤷‍♂️
flak.tedunangst.com/post/where #tech #thrill #HackerNews #ngated

flak.tedunangst.comwhere do the bytes go?

Linux 6.15 will bring open_tree_attr() system call.

"Add open_tree_attr() which allow to atomically create a detached mount tree and set mount options on it. If OPEN_TREE_CLONE is used this will allow the creation of a detached mount with a new set of mount options without it ever being exposed to userspace without that set of mount options applied."

lore.kernel.org/all/20250128-w

lore.kernel.org[PATCH 3/5] fs: add open_tree_attr() - Christian Brauner

🎩✨ Behold, the riveting saga of #syscalls on OpenBSD! Because, naturally, manually entering addresses for every build wasn't enough of a party 🚀. Now, watch in awe as one brave soul ports a "real" application to raw syscalls—truly, the Shakespeare of low-level programming! 🐢🔧
nullprogram.com/blog/2025/03/0 #OpenBSD #lowlevelprogramming #technews #softwaredevelopment #codingadventures #HackerNews #ngated

nullprogram.comA more robust raw OpenBSD syscall demo

Experimented with #ToaruOS today and wrote my first ever syscall. Not just for ToaruOS, but in general.

(I had to make the panic() function non-static for this to work, but it was worth it.)

It’s my first time really tinkering with ToaruOS’s internals at the code level so I’m very proud of myself.

May write a guide for this eventually, lemme know if you wanna see that. It’ll be on my blog.

💥 Want to see how simple ASM can be and dilly-dally some more with syscalls and OS security mechanisms?

Then, "Let's Reflect: Simple ASM Review and OS Security Mechanisms"

🎯 Want to level up your low-level programming?

Check out yet another blog entry: dreaming-of-dragons.blogspot.c

dreaming-of-dragons.blogspot.comWherein We Pause to Reflect: Simple ASM Review and OS Security Mechanismsembedded programming dreaming of dragons

I appreciate the clarity and helpfulness of #rust ‘s error messages, I find myself apprehensive when dealing with #linux #syscalls. The potential for unexpected outcomes looms large, as a single oversight in comprehending the intricacies of the man page can quickly lead to unforeseen issues and the error messages are not helpful at all.

Replied in thread

@agierscher In agreement here. The way I usually look at it is as a suggestion to consider the language for two types of projects:

a) it is a new(ish) codebase, or
b) the project is leaning towards a rewrite anyways.

Until developers stop authoring new C code and/or relying on the C and C , we can't really escape C code. And as @snonux mentioned, rewrites aren't the answer here. But other implementations of the 's can be made, avoiding a link to .

Processes, Threads, Coroutines in Various Programming Languages.

Apart from giving an overview of the topic, I compare the runtime thread count of three different codes in five languages.

A hello world application.

An app that makes three blocking HTTP GET requests.

And finally an async/coroutine/green thread solution for making those same HTTP GET requests.

I was surprised by some results. :)

youtu.be/ehW2dv0IPIM

Code: github.com/simonracz/threads-s

#linux #threads #processes #coroutines #go #rust #java #c++ #c #python #syscalls