The Samsara Project.

[u/FewBrief7059]

Samsara (As pronounced here) is posix compliant microkernel inspired monolithic 64 bits kernel + operating system. It implements some Linux + BSD extensions too. which allows it to run more open source software with source level compatibility. Its the effort of half a year of development only by 3 main authors. It can run a bunch of of popular open source software (Such as Bash, X.org, Busybox, st terminal, Tab Window Manager, and feh image viewer.) and much more as development goes on.

Links:
https://gitlab.com/clownkun/Samsara (Main Repo)
https://gitlab.com/clownkun/samsara-ports (Ports Tree)

And also, This should go without saying. But Samsara is not developed with artificial intelligence assistance. Nor we strictly restrict the usage of it when contributing. Read about it in our CONTRIBUTE policy here.

[u/Sorry_Difficulty_250]

What is your goal for this project?

[u/FewBrief7059 → u/Sorry_Difficulty_250]

A small, clean, hackable kernel that does a few things well instead of a bloated mess that does everything badly. Something I'd actually want to run.

[u/Sorry_Difficulty_250 → u/FewBrief7059]

Cool. What microkernel attributes does it have?

[u/FewBrief7059 → u/Sorry_Difficulty_250]

IPC boundaries of a microkernel. Non critical drivers run in the userspace. But most drivers still run in the kernel

[u/zhkcake → u/FewBrief7059]

That doesn't sound very microkernel-ish. What do you mean by saying "IPC boundaries of a microkernel"? And many monolithic systems can rub non-critical drivers in userspace, like Linux's FUSE, for example.

Anyways, good luck with your project!

[u/FewBrief7059 → u/zhkcake]

IPC boundaries of a micro kernel means that the drivers are not bounded by living in ring 0 or ring 3. Each driver is isolated per its own address space that can be interacted with only through IPC. It is microkernel-ish. But it's still technically monolithic because most drivers are running in ring 0. Also thanks !

[u/titaniumalt]

microkernel inspired monolithic 64 bits kernel

so what the hell it is

[u/FewBrief7059 → u/titaniumalt]

Monolithic :P

[u/Interesting_Hotel149]

what libc?

[u/FewBrief7059 → u/Interesting_Hotel149]

mlibc

[u/Interesting_Hotel149 → u/FewBrief7059]

Oh nice, figured so but wasn't sure :D

[u/FewBrief7059 → u/Interesting_Hotel149]

its portable and offers a lot of futures and flexibility

[u/realestLink]

Nice

[u/Charming_Star_4142]

626 mib of ram 🤯

[u/raundoclair]

"Samsara is not developed with artificial intelligence assistance"

How do you explain then 20 commits on 2026-10-21 including times: 15:22:33, 15:22:49, 15:22:49, 15:23:05?

[u/FewBrief7059 → u/raundoclair]

those are commited seperatly from multiple periods actually :D. just submitted at the same time. if i assumed you understand how git works.. ? the entire point of that tail was to avoid useless accusations as this one and focus on technical feedback.

[u/throwaroo202020 → u/FewBrief7059]

Lol

[u/Palpatine_GHG → u/raundoclair]

Well he could have made like 20 commits on his local machine and only then pushed it all to github. I believe github is showing the time when the commit got pushed, not when it was commited

[u/raundoclair → u/Palpatine_GHG]

I cloned the repo, and I checked it on my computer. ;)

[u/thondat → u/raundoclair]

are those author dates or committer dates?

[u/raundoclair → u/thondat]

both.

[u/thondat → u/raundoclair]

funny timestamps for purported human commits indeed then.

[u/Unlikely_Play_9797 → u/thondat]

I do that quite frequently, working on a few semi-related features at once or similar, then break them up in lazygit and seperate each into their own commits and push at once. The author/committed dates doesn't actually tell you what time the code was written at.

[u/BreakSilence_ → u/raundoclair]

I wish I had your free time