Welcome all

Welcome gentlement to the first weekly meeting regarding our new operating system Any ForumsOS

Any ForumsOS will feature

> single user because multiuser is confusing for Any Forumstards + nobody shares their pc with others these days + is bloat
> read write suid atime sticky bit bullshit is all removed, the only file metadata is executable bit because everything else confuses Any Forumstards + is bloat + git was correct
> no such thing as dotfiles because hidden files are confusing for Any Forumstards
> programs are content addressed at the kernel level because Guix/Nix got it right
> program data is in a directory specified by the content address of the program so dotfiles don't collide + clean home dir
> program cache is in a directory specified by the content address of the program and automatically cleared on reboot so caches don't collide + clean home dir + is bloat
> no such thing as root user because sudo is confusing for Any Forumstards + is bloat
> programs can't read home folder unless given permission because muh privacy + is bloat
> init system is built into the kernel because init system confuses Any Forumstards + is bloat
> programs can't read anything besides their program data and cache directories because it is beyond moronic that unix lets fucking programs do whatever the fuck they want + muh privacy

You get the idea. Share suggestions to simplify it and reduce bloat and whatnot. I got the tech side down mostly I need help with logos marketing user interface all that bullshit and the tech side as well

Attached: 6537F9C7-32EE-4A15-A916-424AA3EF8642.jpg (1024x702, 102.45K)

making an OS is way too hard for Any Forums user

Do we have a logo? I can make a logo. Please we need a logo

here bitch

Attached: Untitled3_20220321210914.png (1000x1000, 39.96K)

Is it its own thing or a loonix distro?

Any ForumsOS leaves behind guhnoo loonix because it is bloat. We are starting anew and removing many of linux's bugs including read write suid atime sticky bit multi user etc

You're not even gonna come close to being POSIX compliant, best you could do is fork a BSD.

>and the tech side as well

Attached: 1647871170579.jpg (600x457, 47.17K)

POSIX compliance is bloat.

> MUHHH BACKWORDS COMPATABILUTY!!!!

GENTLEMEN STAY FOCUSED Any ForumsOS IS MOVING US FORWARD NOT BACK! WE ARE ABANDONING THE DISASTER THAT IS UNIX AND STARTING ANEW! NO POSIX, NO UNIX, NO BSD, NO SUNOS, NO LINUX!

Applications will be sandboxed by default. People love saying
> muh security will always be a problem

Wrong. Computers are insecure because computers are unix which wasn't designed with internet in mind. We are moving FORTH gentlemen. Eschew the old ways!

If this general lasts longer than 5 weeks, I will contribute

You're gonna have TempleOS levels of software compatability, if you even get to running programs that is.
DOA

another one?

What type of scheduling are we planning on?
Round robin, fifo, event-driven, preemptive, time slicing?

>Applications will be sandboxed by default.
What applications?

removing POSIX abstractions like everything is a file would clean up some bloat.
why would something that is clearly not a file like your C drive need to be a file?

>Any Forums writing code

Attached: lol.jpg (1375x749, 331.26K)

Software compatibility is B L O A T

>Software is B L O A T
FTFY

.section ".text"
.globl task_switch
.include "assembly_macros.ah"
task_switch:
preserve_cpu_context
bl get_next_task // Task* next -> r0
ldr r1, =scheduler_object
str r0, [r1, #0] // set running task
restore_cpu_context
subs pc, lr, #0

.globl task_finish_stub
task_finish_stub:
bl remove_running_task
// Set the running task as the do nothing task
ldr r0, =scheduler_object
ldr r1, =donothing_task
str r1, [r0, #0]
ldr sp, [r1, #4]
ldr lr, =donothing_loop
// Schedule the next task
svc #SCHED

.globl donothing_loop
donothing_loop:
wfe
b donothing_loop


(Me)
Proof that I code and that I can contribute

>single user
>no dotfiles
>no sudo
>clean home

so... literally haiku?

ok fag. If this gains some momentum, then I'll contribute

Attached: 1647917275120.jpg (820x820, 280.12K)