News for hackers. Stuff that matters.
Re:The trouble with symbolic links by rwmj on Friday July 22, 2022 @05:58AM (#32190315)
I always thought Unix v7+ should have added some kind way to do atomic groups of syscalls, eg:

  begin_transaction ();
  lstat ("/path", ...);
  lstat ("/path/foo", ...);
  commit ();
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.

It could also 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-a...).

Re:The trouble with symbolic links by bhawks on Friday July 22, 2022 @07:59AM (#32191006)
A general purpose transactional interface widene the error space to include cross process deadlocks / denial of service not to mention performance issues.
Re:The trouble with symbolic links by amaranth on Friday July 22, 2022 @08:13AM (#32191118)
Wasn't making userspace handle these kinds of things a big part of "worse is better"?
Re:The trouble with symbolic links by masklinn on Friday July 22, 2022 @08:49AM (#32191352)
Turns out when facing adversarial actors worse is just worse.