bestorworse

6 ms·

1.
by bestorworse 1y ago
I want that as well, but I don't think it's practical to do that on the Linux desktop ecosystem. Too slow, too much politics. The gist of it is done by Android though, but that required extensive re-engineering of the user space.
2.
Fuchsia RFC: fast and efficient user space kernel emulation(fuchsia.dev)
3 points by bestorworse 1y ago|0 comments
3.
by bestorworse 2y ago
Sure, like you said, having control of the endpoints you could communicate anything if you can transmit bits. That’s unavoidable. But don’t lose the perspective on the benefits of such an architecture. Considering the networking access exam
4.
by bestorworse 2y ago
Yeah, it's brand new as far as you would consider in practice (they use existing libraries and the like). The answer is not much time. The real question is how long to develop good quality drivers for a give platform (say, an x64 lapto
5.
by bestorworse 2y ago
The joy of having a properly implemented capability system is that, well, you can create arbitrary capabilities. You don't need to give a process/component the “unrestricted network access capability” -- you could give it a capabi
6.
by bestorworse 2y ago
Yep. It's anyone's guess what's been going on there. Lots of theories out there. IMO Google doesn't consider this a high priority and the cost to keep the development going on considering the engineers working on it is l
7.
by bestorworse 2y ago
It's technically a general-purpose OS. They had a workstation build target sometime ago which was used for the desktop use-case. They've shipped only for an IoT device so far (Google Nest Hub). Main goal would be to replace the co
8.
Comparing Fuchsia components and Linux containers [video](fosdem.org)
217 points by bestorworse 2y ago|184 comments
9.
Fuchsia already runs Java code with Android's DalvikVM(fuchsia-review.googlesource.com)
52 points by bestorworse 5y ago|12 comments
10.
by bestorworse 5y ago
> On mobile devices, the proprietary drivers are in user space. So, the situation would stay the same regarding that. > The drivers will probably be back in the kernel Manufacturers putting drivers back into the kernel would be a step
11.
by bestorworse 5y ago
But that seems to be exactly what they are doing. They're surely porting the Android runtime to Fuchsia, or even already ported it. Remember there are Android APKs containing native Linux banaries (made with Android's NDK) that yo
12.
by bestorworse 5y ago
Isn't this growth pattern a straightforward consequence of disorderly growth? When microorganisms divide, the children "appear" in the same location. Our species growth dynamics kind of has this same property in that it'
13.
by bestorworse 5y ago
"And you exist only because of us" - Neo I think this pattern of exponential growth of human beings is a curse of their intelligence. All other animals end up being controlled by these large ecosystem dynamics because they can&#x2
14.
by bestorworse 6y ago
This can be done with a proper capability system.
15.
by bestorworse 6y ago
Outch! Thanks for the refs.
16.
by bestorworse 6y ago
Thanks! I searched for this rewritten version and couldn't find anything.
17.
by bestorworse 6y ago
Functionally it's the same. The functions called could live in the kernel (a system call), in the process itself or in a shared lib loaded into the process address space. Interpreting bytes is message passing and this communication hap
18.
by bestorworse 6y ago
IMHO this is the main objective. They even mention in the RFC the case of running Android native code.
19.
by bestorworse 6y ago
This wouldn't solve the problem. It would push the problem one level lower.
20.
by bestorworse 6y ago
> In Fuschia's case it will be like that but the exploitation either gives you access to that driver's capabilities, or simply that driver is giving out handles with permissions insufficiently removed from them Yes, and then yo
21.
by bestorworse 6y ago
When looking more closely on Fuchsia architecture you might well be back into OS design obsession. As the kernel is, IMHO strongly based on a microkernel design, the OS APIs presents itself as userspace APIs. They are in fact, defined by
22.
by bestorworse 6y ago
That is true. I think this is the greater challenge now for Google. A system being very well designed and implemented only attracts enthusiasts and people like that with free time. Even the 'better security' aspect doesn't co
23.
by bestorworse 6y ago
> for malicious software you’re just looking for a process handing out high privilege handles In the end, that is true. But the thing is the way Fuchsia's implementation of the 'capability security model' is done. The capa
24.
by bestorworse 6y ago
I see it as better way of developing a product. Or actually, a foundational system , if Fuchsia really ends up becoming something like that. You see, lots of things that today are fundamental were just "developed organically", an
25.
by bestorworse 6y ago
This resumes the desktop app development drama. I hope Flutter will solve that