<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>mikeash.com pyblog/namecomment-conflict.html comments</title><link>http://www.mikeash.com/?page=pyblog/namecomment-conflict.html#comments</link><description>mikeash.com Recent Comments</description><lastBuildDate>Sun, 10 May 2026 05:23:39 GMT</lastBuildDate><generator>PyRSS2Gen-1.0.0</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>mikeash - 2005-01-25 01:07:00</title><link>http://www.mikeash.com/?page=pyblog/namecomment-conflict.html#comments</link><description>Atomic means that the operation is indivisible. In other words, you either get the complete original directory or the complete new directory, but never anything else, even if the dog trips over the power cord in the middle.&amp;lt;br /&amp;gt;
&lt;br /&gt;&amp;lt;br /&amp;gt;
&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Atomic file swaps are usually pretty easy. You get the files on the same disk, make a system call, the OS swaps the pointers around and you&amp;amp;#8217;re good. No matter what happens, you&amp;amp;#8217;ll either get the old file still there or you&amp;amp;#8217;ll get the new file. You&amp;amp;#8217;ll never get a corrupted or empty file. This technique doesn&amp;amp;#8217;t work for directories, though, so you just have to approximate it.
&lt;br /&gt;</description><guid isPermaLink="true">58833964dae2d391ffdc15f778dc7ed0</guid><pubDate>Tue, 25 Jan 2005 01:07:00 GMT</pubDate></item><item><title>avium - 2005-01-25 01:04:00</title><link>http://www.mikeash.com/?page=pyblog/namecomment-conflict.html#comments</link><description>What&amp;amp;#8217;s an atomic directory replace operation supposed to do?
&lt;br /&gt;</description><guid isPermaLink="true">9361e20e656e36e2c57bde8ae2b8d356</guid><pubDate>Tue, 25 Jan 2005 01:04:00 GMT</pubDate></item></channel></rss>
