Por lo visto han añadido #Hurd a esta lista: Free/Open Source Software choosing to use and/or support #LLM usage/AI, as well as alternatives and tips to requesting better policies or forking. https://codeberg.org/small-hack/open-slopware

Linux por descontado ya estaba incluido.

@thomas @civodul

There's always Hyperbola #GNU and soon #BSD which ironically
might be more GNU respecting than the GNU project themselves.

IDK how #RMS doesn't kick out the #Hurd developers accepting
code tainted from propietary AI (SAAS) agents with potential
Copyright steal (both sides). This is a disgrace.

No wonder the Hyperbola guys got fed up of these hypocrisy
and basically trey are tryong to create soome OpenBSD hardfork
with 100% FLOSS code, no AI and potentially more FS' support,
because FFSv2 -ahem- is not that reliable.

@swick

I've long thought that there's a hole that needs filling, that does what the original #Unix namei does but allows application mode code to supply everything necessary as (opaque) open descriptors: the root directory, the working directory, and the security credentials.

Frustratingly, Unix openat(), Windows NT's NtCreateFile(), and #Hurd's dir_lookup() all come close but all miss a final piece of the puzzle in different ways. openat() misses, for example, a descriptor for the root directory and something like NT's process token handles for security processing. NT has odd ideas about current directories.

This way, server processes could simply make use of the kernel's own already existing logic to handle not traversing '..' over a changed root, following symbolic links, and checking security using client credentials.

There's so much reinvention of this wheel that would have been resolved decades ago if it had only been exposed as a system call.

#filesystems

@abcdw top of my wish list! Wouldn't it be great to have #hurd running on #riscv

I guess the framework way is that as better riscv hardware is developed, you can just pop in a new mobo and away you go!