IssueRaiser

UNIX file locking is broken.

UNIX file locking is broken. Requiring all processes to play along. It suffices one process to ignore fcntl calls to corrupt files. All non-POSIX OSes with proper file locking use the same approach as Windows does. You can install telnet via the add features option from the control panel. Who wants to have such insecure program available anyway? Commercial UNIX systems were know to charge at least $2000 for their SDKs, something that made many join the effort to improve GCC back in the day. Windows NT family has had multi-threading since the day one, even at the kernel level. Which took ages for UNIX systems to catch up. The only UNIX that matches Windows IO completion ports is Solaris. The init is so bad that part of its design has been copied by UNIX systems, instead of using spaghetti init scripts.

Posted by pjmlp on May 11, 2015, 7:31 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments

pricing (Other)

UNIX file locking is broken.

pjmlpMay 11, 2015, 7:31 PM

UNIX file locking is broken. Requiring all processes to play along. It suffices one process to ignore fcntl calls to corrupt files. All non-POSIX OSes with proper file locking use the same approach as Windows does. You can install telnet via the add features option from the control panel. Who wants to have such insecure program available anyway? Commercial UNIX systems were know to charge at least $2000 for their SDKs, something that made many join the effort to improve GCC back in the day. Windows NT family has had multi-threading since the day one, even at the kernel level. Which took ages for UNIX systems to catch up. The only UNIX that matches Windows IO completion ports is Solaris. The init is so bad that part of its design has been copied by UNIX systems, instead of using spaghetti init scripts.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue