Re:Each socket should have two file descriptors
by cmccabe on Sunday July 21, 2013 @08:03PM
(#6081000)
Let's not confuse a bad implementation with a bad philosophy, as a lot of these comments seem to be doing.
Also, "everything is a file" is still true even when some files have additional operations possible on them. It's misleading to say otherwise.
I'm not even sure that "everything is a file" is particularly appealing as a philosophical position.
Re:Each socket should have two file descriptors
by munin on Sunday July 21, 2013 @08:11PM
(#6081035)
so I think that in an abstract world of arbitrary reality, stating "everything is a file" is okay but we have a lot of evidence that implementing something where everything actually is a file is just too hard. If the philosophy is good, why do its adherents produce so much that is crap?
Re:Each socket should have two file descriptors
by valleyer on Monday July 22, 2013 @01:37AM
(#6081964)
Well, for the PTY example above, the reason is backward compatibility. Eventually we need to decide to rid ourselves of the limitations that backward compatibility (with, e.g., bash) brings and clean up the implementation.
Here's another similar example of how "everything is a file" falls down that I wrote about in 2005 when complaining about terminals (http://www.advogato.org/person/habes/diary/6.html)