4 ms·
I always thought it would be a good idea for system calls to support transactions. Probably in a limited way because implementing general transactions would re
by rwmj 10y ago
I always thought it would be a good idea for system calls to support transactions. Probably in a limited way because implementing general transactions would require massive changes to the kernel. But it would be nice to be able to do [error checking omitted]:
begin ();
fp = fopen ("file", "w");
fputs (content, fp);
fclose (fp);
commit ();
It could solve the whole thing with ending up with zero-length files because you didn't use the right incantation to update a file atomically on ext4 (https://thunk.org/tytso/blog/2009/03/12/delayed-allocation-and-the-zero-length-file-problem/ https://thunk.org/tytso/blog/2009/03/12/delayed-allocation-a...).
In Unix v7 mkdir was not a system call. It was a setuid program implemented using mknod + link. That was racy so the mkdir(2) system call was added. But it could have been solved more generally (and more elegantly) by adding transactions.
- tobias3 10y agoWindows has it, but not many people seem to use it: https://msdn.microsoft.com/en-us/library/windows/desktop/aa363764%28v=vs.85%29.aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
- krylon 10y agoBeware, it appears to be deprecated: "Microsoft strongly recommends developers utilize alternative means to achieve your application’s needs. Many scenarios that TxF was developed for can be achieved through simpler and more readily available techniques. Furthermore, TxF may not be available in future versions of Microsoft Windows."
- SolarNet 10y agoWindows has this.