Earlier quoted context omitted.
Roughly put: in a capability based system, if you have a valid handle for a service, then you can use that service. But the only way you can get a valid handle is to ask your parent process for one --- handles are unforgeable. So your parent gets to check that you're legitimate. ...but your parent, in turn, has limited permissions, because the only way it can get a handle is to ask its parent. And when you ask your p…
So, going back to Win32, it's as if OpenFile also took a HANDLE that represented your abilities (or capabilities if you will ) within the security model, with the explicit ability to forward these handles (or new handles that represent a subset of the original's capabilities) to other processes if you choose.
Fuchsia: a new operating system
191–200 of 324 posts
Re: Fuchsia: a new operating system
#192If I had to guess, this looks to be a strong candidate for the embedded OS market. There are still lots of folks running VxWorks, QNX, ThreadX, Mentor Graphics' Nucleus, Green Hills' Integrity. In fact, it looks a lot like the same general design as Integrity, a microkernel capability-based architecture with as much as possible in user space.
Its modern rendering pipeline would suggest it has uses for far more than the embedded OS market.
Re: Fuchsia: a new operating system
#193Earlier quoted context omitted.
You make open source drivers sound like a bad thing.
offering no alternative but "open source" on Linux is certainly not the most business friendly way to go about it.
Re: Fuchsia: a new operating system
#194Re: Fuchsia: a new operating system
#195Earlier quoted context omitted.
In addition to the other comments, I would be excited about a graphics driver not being able to take out my system.
Does this actually happen with enough regularity to care? In the cases where it does, I imagine it's a situation where you're actually doing 3D-accelerated renders of the user interface. In which case, when the graphics subsystem craps out, hasn't your running system been rendered effectively unusable anyway? I get that this is a nice idea in theory, but does it actually improve anything practical in practice?
Re: Fuchsia: a new operating system
#196Earlier quoted context omitted.
You make open source drivers sound like a bad thing.
offering no alternative but "open source" on Linux is certainly not the most business friendly way to go about it.
Re: Fuchsia: a new operating system
#197Are there enough clues to figure out if this is intended to eventually displace Android, ChromeOS, the Ubuntu distribution most googlers use on their company machines, or the Linux they run their data centers? As far as I know, Google hasn't telegraphed the purpose of it. I can't tell if it's targeted at all, none, or some of the above.
Re: Fuchsia: a new operating system
#198Earlier quoted context omitted.
Does this actually happen with enough regularity to care? In the cases where it does, I imagine it's a situation where you're actually doing 3D-accelerated renders of the user interface. In which case, when the graphics subsystem craps out, hasn't your running system been rendered effectively unusable anyway? I get that this is a nice idea in theory, but does it actually improve anything practical in practice?
Yes? I haven't played games in a while, but when I did, crashes were frequent enough to be annoying, and ~100% of the time it was video drivers.
If not, how exactly do you plan to restart the graphics process?
Re: Fuchsia: a new operating system
#199Earlier quoted context omitted.
Have you ever used a Microsoft product? Have you ever tried to get support for a Google product? You do not want these companies involved in your operating system.
Who does that leave to help with your OS? Apple? Their support is pretty bad too.
The support I've had from companies like Red Hat is unparalleled.
Re: Fuchsia: a new operating system
#200Earlier quoted context omitted.
UNIX, as a viable OS model, isn't the last word in operating system design. It has too much design decisions and other baggage rooted in technology dating back to the 1970s. As Rob Pike, one of the people who worked on UNIX, said " Not only is UNIX dead, it's starting to smell really bad. " On top of that, Linux essentially sucked all the air out of the UNIX development space by killing off all the commercial UNIXes.…
> Google and Microsoft are the last two companies with the talent to build a future OS and enough resources and clout to push it enough to get traction. I think that is a stretch. Apple has significant investment in Darwin and are a huge contributor to LLVM. Also, don't count out Amazon ... they have their fingers in so many pies these days ...
Apple could make the next OS for Apple (presuming they were willing to take the leap to do something other than incremental improvements to their existing stable of OSes), but they aren't likely to make OSes for anyone else, so they aren't really relevant to the discussion.
> Also, don't count out Amazon ... they have their fingers in so many pies these days ...
Amazon seems to be pretty consistently plucking the low-hanging fruit from their current position. They might have the right talent to build a future OS, butz for a slightly different reason than Apple, it doesn't seem to be consistent with their orientation.