On Sun, Feb 25, 2018 at 9:44 PM, CM <crusader.m...@gmail.com> wrote: > On Friday, February 23, 2018 at 9:52:39 AM UTC-6, Ben Noordhuis wrote: >> The file descriptor may not be open and even if it is, the UNIX >> semantics of tty file descriptors are such that you don't want to keep >> them open unnecessarily. > > Can you elaborate a bit? I am not familiar with finer points of tty > behavior.
Controlling tty, basically. The risk is that we'd unintentionally acquire (or hang on to) a controlling tty when we shouldn't. >> Apropos blocking operation: in a technical sense, yes; in a practical >> sense, no. /dev/null is not an on-disk entity and neither is / in >> that its inode data is effectively always in memory. > > I.e. we are making an assumption here which is proven to work for Linux (as > of now), but isn't guaranteed in general case. No, it's pretty much a given on the platforms we support. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to libuv+unsubscr...@googlegroups.com. To post to this group, send email to libuv@googlegroups.com. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
