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…
CharlotteOS – An Experimental Modern Operating System
31–40 of 104 posts
Re: CharlotteOS – An Experimental Modern Operating System
#32Earlier quoted context omitted.
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
#33Earlier quoted context omitted.
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.
There was also a period of time where everyone and their mom was writing a new operating system trying to replicate Linux’ success
Re: CharlotteOS – An Experimental Modern Operating System
#34This 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…
Recompiling the whole kernel just to change drivers seems like a deal-breaker for wider adoption
Re: CharlotteOS – An Experimental Modern Operating System
#35> GPLv3 or later (with proprietary driver clarification) What's that parenthetical mean?
Specifically, "Users may link this kernel with closed-source binary drivers, including static libraries, for personal, internal, or evaluation use without being required to disclose the source code of the proprietary driver.".
Re: CharlotteOS – An Experimental Modern Operating System
#36Earlier quoted context omitted.
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.
NT the kernel is quite good. windows nt itself was not always great.
Re: CharlotteOS – An Experimental Modern Operating System
#37Earlier quoted context omitted.
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
#38This 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
#39This 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
#40This 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.
(You don't have to recompile the kernel if you put all the device drivers in it, just keep the object files around and relink it.)