@SRAZKVT they are mandated to have no particular behavior at all
@SRAZKVT they are mandated to have no particular behavior at all
if i ever find an audience with linus torvalds i will demand to know why he just lets us suffer like this
@hipsterelectron aren't inodes mandated by posix ?
@SRAZKVT they are mandated to have no particular behavior at all
@SRAZKVT in order to query the operating system for the existence of a file—WHICH THE FILESYSTEM OSTENSIBLY MAINTAINS A WHOLE SEPARATE ATTRIBUTES DATABASE TO KEEP TRACK OF—you have to go and actually try to read it from disk using a path string which might decide to go somewhere else after an update
@SRAZKVT i remember when i learned the OS/FS can and will just recycle recently freed inodes. i thought it was the perfect example of how searching for deeper meaning or truth in this world is a fool's game
@SRAZKVT yeah here's a number as a souvenir. you cannot redeem it at any store and the stats have stopped returning your syscalls
@hipsterelectron how can inodes be real if our files aren't real
@milo an inode is like if the order number on your last fast food receipt was also your social security number
@milo it's certainly not my node
@milo one of the easiest possible things for an OS to fix and i have never seen a single one ever decide yeah we can afford to generate an incredibly infrequently-accessed 64-bit integer so users can enforce a memory model upon filesystem VFS operations and not die from race conditions
@milo everything is always a race condition as in literally provably and everyone acts like this is a normal way to interact with the ontology of data
@hipsterelectron yeah it constantly blows my mind how fragile filesystems are when it comes to atomicity