On Sat, Aug 10, 2013 at 5:47 PM, Glenn Fowler <[email protected]> wrote: > > On Sat, 10 Aug 2013 17:43:25 +0200 Irek Szczesniak wrote: >> On Fri, Aug 9, 2013 at 6:58 PM, Glenn Fowler <[email protected]> wrote: >> > >> > this will be in the next alpha as >> > /dev/fcntl@... >> > because it works on all types of paths, even /dev/fd >> > >> > the patch happened quickly because the background work in pathdev() and >> > syscall restart intercepts (both part of the stability/debugging flurry >> > this summer) >> > were already in place >> > >> > it handles relative paths like this >> > /dev/fcntl@direct/./file_in_pwd > >> I don't like the name. It implies that all fcntl operations are >> possible which is not the case. For example, how do you pass the >> return value of fcntl() back to the user and what does it mean? How do >> you implement locks, shares, leases with /dev/fcntl? The name is >> misleading. > > fair enough > how about "oflags"
apropos oflag yields nothing. /dev/file was better than that one. /dev/open would be a choice but that's already taken: ls -l /dev/open lrwxrwxrwx 1 root root 46 Apr 5 2010 /dev/open -> ../../devices/pci@0,0/pci1022,1102@18,2:mc-open Irek _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
