Threads for tommy
-
TempleOS only only runs one app at a time, the logic being that a human can only concentrate at only one thing at a time. There is no need to have multitasking, but sometimes an app would benefit additional processing power, so TempleOS can do multi-core processing by having a master-slave model: The main CPU can control the other CPU’s and hand out tasks to them.
And while we think about crazy OS ideas: Why not run multiple independent kernels - one on every CPU? So while a rouge process could corrupt and take down one kernel the rest of the system would continue working.
-
TempleOS can do multi-core processing by having a master-slave model: The main CPU can control the other CPU’s and hand out tasks to them.
Classic Mac OS did this.
And while we think about crazy OS ideas: Why not run multiple independent kernels - one on every CPU? So while a rouge process could corrupt and take down one kernel the rest of the system would continue working.
This kinda exists already; galaxies in VMS achieve virtualization this way, I believe. Running multple OS instances could be useful for the Erlang OS mentioned though, especially since the concepts could make it transparent.
-
Classic Mac OS did this.
I forgot that the MDD dual G4 models could still boot Mac OS 9. I’m reasonably certain those shipped after OS X came out of beta, though, and could only boot OS 9 because it was (only slightly) too early to stop that.
Were there other multi CPU macs that booted classic Mac OS?
-
-
-
You are describing unikernels.
From my perspective it’s less about the human and more about the fact that most companies don’t run one computer or even one database - they run thousands. We are long past the “one operating system / computer” phase. Even the smallest companies are load balancing their webservers amongst multiple vms. We need new operating systems to facilitate this.
-
I think on a personal level, nobody has only one device anymore (desktop/laptop/phone/tablet/smartwatch/e-reader/smart-TV/home-automation-stuff/home-server-possibly) and we need a good unified system for handling this, instead of pretending they’re all islands that just happen to communicate sometimes, with integration an afterthought.
-
-
Why not run multiple independent kernels - one on every CPU?
This has been explored in research. Check out http://www.barrelfish.org/
-
And while we think about crazy OS ideas: Why not run multiple independent kernels - one on every CPU? So while a rouge process could corrupt and take down one kernel the rest of the system would continue working.
Check out rump kernels in NetBSD probably not same idea but it can be achieved
-
-
So I can just take a photo of someone’s vaccine QR-cert and use that to jump over the paywall? No, I won’t do that because that would be lying, and I’m a good person who does not lie.
You could, but identity makes “limit one per customer” easy to enforce.
that just means the real person who owns the ID may get locked out if their thing is “stolen” and used before they use it.
Also some people were sharing pictures of theirs after vaccination - and we have an instant problem.
This seems a bunch like SSNs. A unique but easily copied fact.