Fix Resource interact with other Subsystems #137
Description
I previously added a part of the book talking about a resource management system, however, there was a misunderstanding of how it should work with the VFS system and the IPC. Here is a place for a discussion on how to resolve them, to be later implemented in a PR.
For the VFS:
This VFS is built on top of the previously defined resource API (see Resource Management). The VFS creates a file-specific resource_t for each open file and returns a handle that is then used with the resource manager's generic read, write, and close functions that will perform the proper handle-to-resource lookup and call our VFS functions.
"I think this paints the wrong picture. The resource api and vfs are separate subsystems that interact but the vfs doesnt depend on the resource api, it can (and should) exist without it. The two would only actually interact when something higher level connects them (like a syscall request). The resource subsystem makes little sense for in-kernel operations, as you can use raw pointers to things, so why incur the extra cost?"
For the IPC:
Would be a simple update similar to what is currently in the VFS where I would adapt the IPC functions to take a resource_t paramater but would introduce simmilar depedancy issue as above.