Mom: "we have plan 9 at home"
Plan 9 at home: https://derivelinux.org/

#plan9os
#derivelinux

Trying out #plan9os fork #9front fornthe first time and, after some configuration, discovered it has built-in functions to generate technobabble, and it is getting increasingly tempting to use it to write up a nonsense resume.

(The commands in question: "bullshit" to generate a short title for a project, /bin/games/festoon to generate a nonsensical but impressive-to-interviewers technical report)

good mornyan fedi  

im wallowing in my lack of desk space  but i think im gonna put that pain to good use and set up my #Plan9OS grid’s DNS today (during lunchtime ofc)

whatsup?

@jbauer Aside from Minux, which others have mentioned, #Plan9OS implements ... parts ... of this.

Several of Jon's comments are contradictory. Among the reasons that a modern Linus system has a huge number of processes is because individual kernel threads and services are exposed as virtual processes. That starts off with at least a thread or several per CPU pipeline AFAIU (it's been a while since I looked into this), plus filesystem journaling processes, and a number of others.

If you limit both IPC and filesystem access, you're both hugely limiting and complexifying application interactions. For better or worse, pipelines and disk storage are a maximally-consistent form of IPC. That doesn't mean applications should have unlimited access, but in some cases (e.g., the shell, system processes), any limitations quickly become hugely problematic.

I agree that the complexity can be overwhelming, and miss much of the old days myself.

@Valenoern This is the essential idea behind "docfs", which would be a document-oriented filesystem. Its networked sibling being "webfs".

"Document" here is in the sense of #PaulOtlet, of any durable record. That might be a text, image, sound, video, multimedia content, data, software, or an amalgamation or melange.

One of my key ideas is that the metadata for these documents would be part of the filesystem, extending the notion of what constitutes file-centric data. I'd like to see some form of bibliographic data presented, where available for public and published media (book, articles, audio recordings, films).

Search is another element, and one idea for the filesystem would be as a virtual filesystem in which attributes could be supplied until a single item matching those criteria was found. "Identity is search".

For projects, some concept of structured workflows, with groups, tasks, milestones, and contributing data. For a sufficiently structured organisation, security and access controls.

I'd like the whole concept to be as commercialisation-hostile as possible, with both copyrights and payments entirely out of scope.

#docfs #webfs #kfc #maundenaum #DublinCore #metadata #bibliography #Plan9OS #Schopenhauer

Idea:
a #Plan9OS phone with a trackball/-point and three buttons on its side, running a modified window manager.

There has been a port of #InfernoOS for #Android that did something similar but it'd be cool to have native mouse buttons and proper Plan 9 instead of a VM.

(btw, how should I tag these? because both "Plan 9" and "Inferno" are ambiguous and hard to search for, but adding "-OS" feels weird.)