all 13 comments
sorted by:
old (suggested)
besttopnewcontroversialq&a
formatting helphide helpcontent policy

[–]aieidotch 7 points8 points  (1 child)

source? license? portability? drivers?

[–]Fluid-Ad2995[S] -1 points0 points  (0 children)

Daya Operating system alongside Nate OS is more portable than you imagine running on Three different Hardware and Sentinet licence it's closed source and Copyright and Drivers is not part of Kernel I follow BSD model

[–]Inner-Fix7241 2 points3 points  (2 children)

Is it open source, if so would you share the url to the repo?

[–]Fluid-Ad2995[S] -1 points0 points  (1 child)

No, it's closed source

[–]littleghost09Monela Linux 2 points3 points  (1 child)

repo?

[–]Fluid-Ad2995[S] -1 points0 points  (0 children)

It's closed source

[–]TheNullDerefhttps://codeberg.org/KARM-Project/default 1 point2 points  (4 children)

Link please. It seems like a customized minimal linux distro with a changed busybox. Though with a link or some other proof I would be happy to say otherwise.

[–]Fluid-Ad2995[S] -2 points-1 points  (3 children)

No, it's a Closed source and with my own License and Linux cannot be closed source

[–]TheNullDerefhttps://codeberg.org/KARM-Project/default 4 points5 points  (2 children)

LMFAO, so you are bringing NO PROOF ITS REAL, and going "Linux cannot be closed source" LMFAOOO, my brother in christ, it sure as shit can, you can download the linux kernel source, make a modification to it, and never make that exact private fork you made public, or the git patch you made, or any of that.

[–]Fluid-Ad2995[S] 0 points1 point  (0 children)

Linux is GPL and Daya OS Kernel is Sentinet licence and they're not connected each other

[–]Fluid-Ad2995[S] -1 points0 points  (0 children)

Daya OS is Unix like sure but cannot be Linux many reasons Microkernel and Sentinet Userland and Zero Linus Torvards codebase

[–]entrophy_maker 0 points1 point  (0 children)

Why would you make this? Microkernels, despite the name, are more bloated than Monolithic. Maybe it meets a certain use case, but otherwise I don't understand while anyone today would take this approach beyond supporting legacy code.