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.
-
Show this thread
-
linus HATES this (http://yarchive.net/comp/linux/everything_is_file.html …)pic.twitter.com/qp9r7uxXR1
5 replies 4 retweets 52 likesShow this thread -
(so it *must* be good)
1 reply 0 retweets 59 likesShow this thread -
later in the thread linus acknowledges that this is basically how microkernels work
1 reply 1 retweet 33 likesShow this thread -
when read and write are the only syscalls, then Andy Tanenbaum wins
2 replies 5 retweets 68 likesShow this thread -
alternative method for implementing close: just kill the process when you run out of file descriptors
6 replies 1 retweet 35 likesShow this thread -
Replying to @mycoliza
by appending to the file pids_to_kill?
1 reply 0 retweets 3 likes -
Replying to @jackie_cs_ @mycoliza
Nah, you just write 0x09 to /proc/<id>/signal/send Not sure how to register a signal handler. Perhaps write the function pointer in the process's virtual address space to /proc/self/signal/<signal num>
1 reply 0 retweets 3 likes
who needs signal handlers when eventfd is a thing? and for handling stuff like SIGSEGV, give an eventfd to another process, maybe init
-
-
Because eventfd is a syscall.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.