if everything TRULY is a file, then the only syscalls you need are open, read, and write. you can implement everything else on top of open, read, and write. change my mind.
that's different. privileges for the access come from the open() call / from the fd, rather than being taken from the caller on read(); the mm_struct being accessed comes from the inode. if you read the FD from another context, you get the same data.
-
-
in other words, none of these things are defined as properties of the calling process, they just happen to match in this usecase.
-
Ah right, misinterpreted what kinds of properties you were referring to.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.