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

21–30 of 104 posts

Re: CharlotteOS – An Experimental Modern Operating System

#21

Post by BobbyTables2 »

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…

Wish OP had put that as the main readme.

The intro page is currently useless.

Re: CharlotteOS – An Experimental Modern Operating System

#22

Post by KerrAvon »

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.

Re: CharlotteOS – An Experimental Modern Operating System

#24

Post by ofrzeta »

IshKebab wrote: post #23
ofrzeta wrote: post #8

So, what's modern about it? "novel systems like Plan 9" is quite funny because Plan 9 is 30 years old.

That's still newer than Linux's system design.

In an operating system course I attended it was mostly Unix and everyone was used to bashing Windows NT ("so crappy, bsod etc.") but we had Stallings' book and I was surprised to learn that NT was in many ways an improvement over Unix and Linux.

Re: CharlotteOS – An Experimental Modern Operating System

#25

Post by vlovich123 »

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.

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.

Re: CharlotteOS – An Experimental Modern Operating System

#26

Post by Razengan »

varispeed wrote: post #19

Modern operating system, ready to face challenges of today political landscape, should natively support "hidden" encrypted containers, that is you would log in to completely different, separate environment depending on password. So that when under threat could disclose a password to an environment you are willing to share and attacker would have no way of proving there is any other environment present.

It would be easy to tell for anyone seriously after you: If I kidnap you and make you log into your computer, and you log into the decoy state, it'd be obvious to see that the last time you visited any website etc. was over a month ago and so on.

Re: CharlotteOS – An Experimental Modern Operating System

#27

Post by Razengan »

pjmlp wrote: post #11
ofrzeta wrote: post #8

So, what's modern about it? "novel systems like Plan 9" is quite funny because Plan 9 is 30 years old.

The sad part is that there are too many ideas of old systems lost in a world that 30 years later seems too focused on putting Linux distributions everywhere.

Yeah the more you read up on computing history from barely even 40 years ago, it seems that most of the things that we take for granted today became so more through politics (and in the case of Microsoft, bullying) than merit.

Re: CharlotteOS – An Experimental Modern Operating System

#28

Post by varispeed »

Razengan wrote: post #26
varispeed wrote: post #19

Modern operating system, ready to face challenges of today political landscape, should natively support "hidden" encrypted containers, that is you would log in to completely different, separate environment depending on password. So that when under threat could disclose a password to an environment you are willing to share and attacker would have no way of proving there is any other environment present.

It would be easy to tell for anyone seriously after you: If I kidnap you and make you log into your computer, and you log into the decoy state, it'd be obvious to see that the last time you visited any website etc. was over a month ago and so on.

For sure you'd have to use it from time to time.

Re: CharlotteOS – An Experimental Modern Operating System

#30

Post by yjftsjthsd-h »

bionsystem wrote: post #7
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…

I believe redox is doing the same (the everything as an URI part)

Skimming https://doc.redox-os.org/book/scheme-rooted-paths.html and https://doc.redox-os.org/book/schemes.html , I think they've slightly reworked that to a more-unixy approach, but yeah still fundamentally more URI than traditional VFS
Post reply on HN