<story><title>Disorderfs: FUSE-based filesystem that introduces non-determinism into metadata</title><url>https://salsa.debian.org/reproducible-builds/disorderfs</url></story><parent_chain></parent_chain><comment><author>danbst</author><text>Sorry for plugging in. NixOS has a plan to use DisorderFS in making 100% reproducible build.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;r13y.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;r13y.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;As I understand it, currently several packages are not reproducible (like, python, pytest, gcc), so it is not priority, but when those large packages will be done, r13y will start using DisorderFS to uncover remaining reproducibility bugs.&lt;p&gt;This is too idealistic, but gives lots of pleasure about package space.</text></comment>
<story><title>Disorderfs: FUSE-based filesystem that introduces non-determinism into metadata</title><url>https://salsa.debian.org/reproducible-builds/disorderfs</url></story><parent_chain></parent_chain><comment><author>EdSchouten</author><text>Buildbarn, a build cluster implementation for Bazel that I maintain, can also run build actions (compilation steps, unit tests) in a FUSE file system. Though the primary motivator for this is that it reduces the time to construct a build action&amp;#x27;s file system to nearly instant, it has the advantage that I can also do things similar to disorderfs. Shuffling directory listings is actually something that I also added. Pretty useful!&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;buildbarn&amp;#x2F;bb-remote-execution&amp;#x2F;blob&amp;#x2F;eb11502902afa733356d7f2027bd41ed3872766e&amp;#x2F;pkg&amp;#x2F;proto&amp;#x2F;configuration&amp;#x2F;fuse&amp;#x2F;fuse.proto#L59-L70&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;buildbarn&amp;#x2F;bb-remote-execution&amp;#x2F;blob&amp;#x2F;eb1150...&lt;/a&gt;</text></comment>