Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CharlotteOS – An Experimental Modern Operating System

github.com

Post reply on HN
Print view View original

71–80 of 104 posts

Re: CharlotteOS – An Experimental Modern Operating System

#71

Post by miohtama »

KerrAvon wrote: post #22
embedding-shape wrote: post #3

This is probably a better introduction it seems, than specifically the kernel of the OS: https://github.com/charlotte-os/.github/blob/main/profile/RE... > URIs as namespace paths allowing access to system resources both locally and on the network without mounting or unmounting anything This is such an attractive idea, and I'm gonna give it a try just because I want something with this idea to succeed. Seems the proje…

In practice, the problem with URIs is that it makes parsing very complex. You don’t really want a parser of that complexity in the kernel if you can avoid it, for performance reasons if nothing else. For low-level resource management, an ad-hoc, much simpler standard would be significantly better.

You can use a subset of easily parseable URIs

Re: CharlotteOS – An Experimental Modern Operating System

#72

Post by irusensei »

grepfru_it wrote: post #16
the__alchemist wrote: post #13

I love seeing projects in this space! Non-big-corp OSSes have been limited to Linux etc; would love to explore the space more and have non-Linux, non-MS/Apple options. For example, Linux has these at the core which I don't find to be a good match for my uses: - Multi-user and server-oriented permissions system. - Incompatible ABIs - File-based everything; leads to scattered state that gets messy over time. - Package…

Haiku, plan9, redox, and Hurd comes to mind Reactos if you need something to replace windows Implementing support for docker on these operating systems could give them the life you are looking for

I don't think they will like Plan9 if file based everything is a turn off.

Did you know the Go language supports Plan9? You can create a binary from any system using GOOS=plan9 with amd64 and i386 supported. You might need to disable CGO and use libraries that don't have operating system specifics though. You can even bootstrap Go from it provided you have the SDK.

Incidentally 9Front is a modern fork of Plan9.

Re: CharlotteOS – An Experimental Modern Operating System

#73

Post by irusensei »

the__alchemist wrote: post #13

I love seeing projects in this space! Non-big-corp OSSes have been limited to Linux etc; would love to explore the space more and have non-Linux, non-MS/Apple options. For example, Linux has these at the core which I don't find to be a good match for my uses: - Multi-user and server-oriented permissions system. - Incompatible ABIs - File-based everything; leads to scattered state that gets messy over time. - Package…

Fuchsia

Re: CharlotteOS – An Experimental Modern Operating System

#74

Post by LavenderDay3544 »

jancsika wrote: post #29

> GPLv3 or later (with proprietary driver clarification) What's that parenthetical mean?

There's a note in the repo that clarifies the meaning of the GPLv3 regarding the use of combining covered works with proprietary libraries when the resulting combined work is never conveyed. It doesn't modify the license, it just explains what it means in that specific case as we interpret it.

Also to be clear I am not a lawyer and nothing I say constitutes any form of legal advice.

Re: CharlotteOS – An Experimental Modern Operating System

#75

Post by LavenderDay3544 »

embedding-shape wrote: post #3

This is probably a better introduction it seems, than specifically the kernel of the OS: https://github.com/charlotte-os/.github/blob/main/profile/RE... > URIs as namespace paths allowing access to system resources both locally and on the network without mounting or unmounting anything This is such an attractive idea, and I'm gonna give it a try just because I want something with this idea to succeed. Seems the proje…

OP here.

The plan is to hand out panes which are just memory buffers to which applications write pixel data as they would on a framebuffer then when the kernel goes to actually refresh the display it composites any visible panes onto the back buffer and then swaps buffers. There is nothing unsafe about that any more so than any other use of shared memory regions between the kernel and userspace and those are quite prolific in existing popular OSes.

If anything the Unix display server nonsense is overly convoluted and far worse security wise.

Re: CharlotteOS – An Experimental Modern Operating System

#76

Post by LavenderDay3544 »

Philpax wrote: post #4
embedding-shape wrote: post #3

This is probably a better introduction it seems, than specifically the kernel of the OS: https://github.com/charlotte-os/.github/blob/main/profile/RE... > URIs as namespace paths allowing access to system resources both locally and on the network without mounting or unmounting anything This is such an attractive idea, and I'm gonna give it a try just because I want something with this idea to succeed. Seems the proje…

The choice of a pure-monolithic kernel is also interesting; I can buy that it's more secure, but having to recompile the kernel every time you change hardware sounds like it would be pretty tedious. Early days, though, so we'll see how that decision works out.

Incremental compilation makes that a lot less heavyweight than you would think and the idea is to automate the process so the average non-technical user doesn't need to know or care how it works.

Re: CharlotteOS – An Experimental Modern Operating System

#77

Post by LavenderDay3544 »

vlovich123 wrote: post #25
Philpax wrote: post #4

Earlier quoted context omitted.

The choice of a pure-monolithic kernel is also interesting; I can buy that it's more secure, but having to recompile the kernel every time you change hardware sounds like it would be pretty tedious. Early days, though, so we'll see how that decision works out.

Why would you buy it’s more secure. Traditionally in windows in-kernel compositing was a constant source of security vulnerabilities. Sure rust may help the obvious memory corruption possibilities but I’m not convinced.

[flagged]

Re: CharlotteOS – An Experimental Modern Operating System

#78

Post by LavenderDay3544 »

surajrmal wrote: post #34
incognito124 wrote: post #10

Earlier quoted context omitted.

Recompiling the whole kernel just to change drivers seems like a deal-breaker for wider adoption

If this kernel ever gets big enough where this might matter, I'm sure they can change the design. Nothing is set in stone forever and for the foreseeable future it's unlikely to matter.

If there's enough demand for dynamic kernel modules they can be added later. That's not a feature that you have to build ypur whole kernel around from that start. Linux definitely didn't but it has it now so it's definitely that can revisited or even made an opt-in feature.

Re: CharlotteOS – An Experimental Modern Operating System

#79

Post by userbinator »

the__alchemist wrote: post #13

I love seeing projects in this space! Non-big-corp OSSes have been limited to Linux etc; would love to explore the space more and have non-Linux, non-MS/Apple options. For example, Linux has these at the core which I don't find to be a good match for my uses: - Multi-user and server-oriented permissions system. - Incompatible ABIs - File-based everything; leads to scattered state that gets messy over time. - Package…

Have you seen TempleOS?
Post reply on HN