Capability oriented systems seem to be a good idea therefore my OS is very capability oriented. Im kind of in an infinite loop over this but if I want to use capability based addressing for task switching I would have to move my mmu back into the kernel. So I was wondering whether it really is worth using capability oriented OS. My question is what are some loop holes of capability based addressing? and Why is it it is not in common use?
p.s. Maybe I should create a wiki page about capabilities and ACLs (I'll post this in the OS wiki forum)
Capability oriented systems
Capability oriented systems
Get back to work!
Github
Github
Re: Capability oriented systems
i maybe wrong, but ive always interpreted 'orientation' to be an organisation tool.. and capabilities to be about access and permissions.
how do you see them aligning?
how do you see them aligning?
Re: Capability oriented systems
yes, berkus. Kind of like EROS and its successors.
For people who don't understand: So heres the situation, everything is a capability even the addressing system. The apps get the pointer in encrypted form. The mmu and scheduler decrypt the pointer and place it in the correct location, therefore voiding the need of context switching if your still confused here are some useful pages (wikipedia's always useful):
http://en.wikipedia.org/wiki/Capability-based_security
http://en.wikipedia.org/wiki/Capability ... addressing
For people who don't understand: So heres the situation, everything is a capability even the addressing system. The apps get the pointer in encrypted form. The mmu and scheduler decrypt the pointer and place it in the correct location, therefore voiding the need of context switching if your still confused here are some useful pages (wikipedia's always useful):
http://en.wikipedia.org/wiki/Capability-based_security
http://en.wikipedia.org/wiki/Capability ... addressing
Get back to work!
Github
Github