/g/ - syscall of the day: ustat/(f)statfs - Technology

Anonymous

syscall of the day: ustat/(f)s(...) 04/07/26(Tue)09:02:12 No.108548206

File: 1760304060962246.gif (722 KB, 416x498)

syscall of the day: ustat/(f)statfs Anonymous 04/07/26(Tue)09:02:12 No.108548206 Archived

previous: >>108539586
#define __NR_ustat                136
#define __NR_statfs                137
#define __NR_fstatfs            138
https://man7.org/linux/man-pages/man2/ustat.2.html
https://man7.org/linux/man-pages/man2/statfs.2.html

tl;dr:
get filesystem statistics

holy fucking magic numbers batman... just look at that list
also
>Nobody knows what f_fsid is supposed to contain (but see below).
i mean this is just comical? how is linux even real?
then there's also
>The __fsword_t type used for various fields in the statfs structure definition is a glibc internal type, not intended for public use.
>This leaves the programmer in a bit of a conundrum when trying to copy or compare these fields to local variables in a program.
>Using unsigned int for such variables suffices on most systems.
genuinely how does any OS function if this is the level of nonsense we're facing?

relevant resources:
man man
man syscalls
https://man7.org/linux/man-pages/
https://linux.die.net/man/
https://elixir.bootlin.com/linux/
https://elixir.bootlin.com/musl/
https://elixir.bootlin.com/glibc/

Anonymous
04/07/26(Tue)09:05:37 No.108548235

Anonymous 04/07/26(Tue)09:05:37 No.108548235

>>108548206
bussy status?

Anonymous
04/07/26(Tue)09:08:10 No.108548255

Anonymous 04/07/26(Tue)09:08:10 No.108548255

>>108548206
>genuinely how does any OS function if this is the level of nonsense we're facing?
With duct tape and bubble gum.

Anonymous
04/07/26(Tue)09:16:02 No.108548329

Anonymous 04/07/26(Tue)09:16:02 No.108548329

>>108548206
>how does any OS function if this is the level of nonsense we're facing
Hardware engineers doing a LOT of heavy lifting.

Anonymous
04/07/26(Tue)09:39:57 No.108548524

Anonymous 04/07/26(Tue)09:39:57 No.108548524

>>108548206
i don't even know what a syscall is but i fucking love these threads

Anonymous
04/07/26(Tue)09:46:33 No.108548573

Anonymous 04/07/26(Tue)09:46:33 No.108548573

deprecated

Anonymous
04/07/26(Tue)10:37:38 No.108548875

Anonymous 04/07/26(Tue)10:37:38 No.108548875

i want syscall anon PREGNANT by tomorrow

Anonymous
04/07/26(Tue)12:44:02 No.108549847

Anonymous 04/07/26(Tue)12:44:02 No.108549847

Imagine getting impregnated by your big dick futa gf that would be weird haha

Anonymous
04/07/26(Tue)13:01:11 No.108549977

Anonymous 04/07/26(Tue)13:01:11 No.108549977

>genuinely how does any OS function if this is the level of nonsense we're facing?
at this point just use the raw syscall instead of dealing with glibc

Anonymous
04/07/26(Tue)13:24:04 No.108550157

Anonymous 04/07/26(Tue)13:24:04 No.108550157

as I understand it glibc is the universal C library with all the tooling and instrumentation that keeps compatibility between different machines.

Anonymous
04/07/26(Tue)13:25:06 No.108550164

Anonymous 04/07/26(Tue)13:25:06 No.108550164

I have a question, glibc makes the C software you write "POSIX compatible" so can run over every POSIX compliant infrastructure?

Is this correct?

Anonymous
04/07/26(Tue)14:29:45 No.108550735

Anonymous 04/07/26(Tue)14:29:45 No.108550735

>>108550164
no, glibc makes your software glibc compatible* *not guaranteed :^)

Anonymous
04/07/26(Tue)14:44:07 No.108550858

Anonymous 04/07/26(Tue)14:44:07 No.108550858

>>108549977
glibc is providing the wrappers though.
Also, if you value not having nightmares, do NOT look into AIO. You hear me? NO AIO!

>>108550157
glibc provides userspace implementations of all sorts of shit. Mind you, *userspace*.

>>108550735
This.

Anonymous
04/07/26(Tue)15:46:00 No.108551397

Anonymous 04/07/26(Tue)15:46:00 No.108551397

File: Screenshot From 2026-03-3(...).png (111 KB, 340x263)

111 KB PNG

>>108550858
>>108550735

Appreciated. This is very interesting.

Anonymous
04/07/26(Tue)18:07:04 No.108552448

Anonymous 04/07/26(Tue)18:07:04 No.108552448

>>108548875
now this is the kind of energy i need in my life
>>108548524
glad you're enjoying them, anon
>>108550735
>*not guaranteed :^)
lol

Anonymous
04/07/26(Tue)19:09:11 No.108552843

Anonymous 04/07/26(Tue)19:09:11 No.108552843

>>108550164
No. Look at the "standards" or "history" section of the manpages, stuff that's C- or POSIX-compatible is marked as such. A simple example would by memchr(3), listing memchr as part of the POSIX and C standards, and memrchr() and rawmemchr() as glibc extensions.

Anonymous
04/08/26(Wed)00:25:57 No.108554401

Anonymous 04/08/26(Wed)00:25:57 No.108554401

bampu

Anonymous
04/08/26(Wed)09:14:26 No.108556910

Anonymous 04/08/26(Wed)09:14:26 No.108556910

>>108548206
from the manpage:

Subsequently, Linux 2.6 added new statfs64() and fstatfs64() system
     calls that employ a new structure, statfs64.  The new structure contains the same fields as the original statfs structure, but the sizes of various fields are increased, to  accommodate
     large file sizes.  The glibc statfs() and fstatfs() wrapper functions transparently deal with the kernel differences.

this might explain the retarded __fsword_t type. They tried to be "helpful" by abstracting over 32/64 bit architectures but half assed it

Anonymous
04/08/26(Wed)13:05:49 No.108558578

Anonymous 04/08/26(Wed)13:05:49 No.108558578

>>108550735
why is it like this

Anonymous
04/08/26(Wed)13:14:28 No.108558665

Anonymous 04/08/26(Wed)13:14:28 No.108558665

>>108548329
Hardware is magic as far as I'm concerned.
God personally intervenes in every CPU cycle to ensure that instructions are executed as intended.

Anonymous
04/08/26(Wed)13:48:42 No.108558960

Anonymous 04/08/26(Wed)13:48:42 No.108558960

>>108558665
honestly this really doesn't feel far off from the truth lol

Anonymous
04/08/26(Wed)17:53:54 No.108561011

Anonymous 04/08/26(Wed)17:53:54 No.108561011

>>108558665
Aliens gave us two's complement.