ncdu 2.6

.gitignore

@@ -70,7 +70,9 @@ dat/ncdu/man/2_2.pod
 dat/ncdu/man/2_3.md
 dat/ncdu/man/2_3.pod
 dat/ncdu/man/2_4.md
-dat/ncdu/man/2_4.pod
+dat/ncdu/man/2_4.mdoc
+dat/ncdu/man/2_5.md
+dat/ncdu/man/2_5.mdoc
 dat/nginx-confgen/changes.log
 dat/nginx-confgen/changes.md
 dat/nginx-confgen/man.md
@@ -150,6 +152,7 @@ pub/ncdc/install.html
 pub/ncdc/man.html
 pub/ncdc/scr.html
 pub/ncdu.html
+pub/ncdu/binfmt.html
 pub/ncdu/changes.html
 pub/ncdu/changes2.html
 pub/ncdu/feed.atom
@@ -181,6 +184,7 @@ pub/ncdu/man/2_1.html
 pub/ncdu/man/2_2.html
 pub/ncdu/man/2_3.html
 pub/ncdu/man/2_4.html
+pub/ncdu/man/2_5.html
 pub/ncdu/scr.html
 pub/nginx-confgen.html
 pub/nginx-confgen/changes.html

Makefile

@@ -51,9 +51,11 @@ PAGES=\
 	"ncdu.md"\
 	"ncdu/changes.log           https://g.blicky.net/ncdu.git/plain/ChangeLog?h=master          Ncdu 1.x Release History"\
 	"ncdu/changes2.log          https://g.blicky.net/ncdu.git/plain/ChangeLog?h=zig             Ncdu 2.x Release History"\
+	"ncdu/binfmt.md"\
 	"ncdu/jsonfmt.md"\
-	"ncdu/man.mdoc              https://g.blicky.net/ncdu.git/plain/ncdu.1?h=v2.5               Ncdu 2.5 Manual"\
+	"ncdu/man.mdoc              https://g.blicky.net/ncdu.git/plain/ncdu.1?h=v2.6               Ncdu 2.6 Manual"\
-	"ncdu/man/2_4.pod           https://g.blicky.net/ncdu.git/plain/ncdu.pod?h=v2.4             Ncdu 2.4 Manual"\
+	"ncdu/man/2_5.mdoc          https://g.blicky.net/ncdu.git/plain/ncdu.1?h=v2.5               Ncdu 2.5 Manual"\
+	"ncdu/man/2_4.mdoc          https://g.blicky.net/ncdu.git/plain/ncdu.1?h=v2.4               Ncdu 2.4 Manual"\
 	"ncdu/man/2_3.pod           https://g.blicky.net/ncdu.git/plain/ncdu.pod?h=v2.3             Ncdu 2.3 Manual"\
 	"ncdu/man/2_2.pod           https://g.blicky.net/ncdu.git/plain/ncdu.pod?h=v2.2             Ncdu 2.2 Manual"\
 	"ncdu/man/2_1.pod           https://g.blicky.net/ncdu.git/plain/ncdu.pod?h=v2.1             Ncdu 2.1 Manual"\

dat/guestbook.md

@@ -17,6 +17,12 @@ respective issue tracker or send a mail to
 
 # Entries
 
+`2024-08-17` - Young Lee
+:   hey, thanks for the nice app!
+
+`2024-08-08` - raksO
+:   Thanks! It is really helpful! ❤️
+
 `2024-07-12` - DIANA PUNKY
 :   ncdu rocks!
 

dat/index.md

@@ -10,9 +10,14 @@ crap I've written over the years. :)
 <!-- These announcements are parsed by mkfeed.pl, see that file for formatting -->
 ## Announcements <a href="/feed.atom"><img src="/img/feed_icon.png" alt="Atom feed"></a>
 
-`2024-07-24` - 2.5 released <!-- tags: ncdu, link: /ncdu -->
+`2024-09-27` - ncdu 2.6 released <!-- tags: ncdu, link: /ncdu -->
+:   Adds a new binary export format that better works with parallel scanning,
+    offers built-in compression and supports browsing directory trees that are
+    too large to fit in memory. [Homepage](/ncdu) - [Changelog](/ncdu/changes2).
+
+`2024-07-24` - ncdu 2.5 released <!-- tags: ncdu, link: /ncdu -->
 :   Adds support for parallel scanning, improves import/export performance and
-    fixes a number of bugs. [Ncdu homepage](/ncdu) - [Changelog](/ncdu/changes).
+    fixes a number of bugs. [Homepage](/ncdu) - [Changelog](/ncdu/changes2).
 
 `2024-07-18` - ncdc 1.24.1 released <!-- tags: ncdc, link: /ncdc -->
 :   Just fixes a build error. [Homepage](/ncdc) - [Changelog](/ncdc/changes).

dat/ncdu.md

@@ -1,34 +1,49 @@
 % NCurses Disk Usage
 
-Ncdu is a disk usage analyzer with an ncurses interface. It is designed to find
+Ncdu is a disk usage analyzer with a text-mode user interface. It is designed
-space hogs on a remote server where you don't have an entire graphical setup
+to find space hogs on a remote server where you don't have an entire graphical
-available, but it is a useful tool even on regular desktop systems. Ncdu aims
+setup available, but it is a useful tool even on regular desktop systems. Ncdu
-to be fast, simple and easy to use, and should be able to run in any minimal
+aims to be fast, simple, easy to use, and should be able to run on any
-POSIX-like environment with ncurses installed.
+POSIX-like system.
 
-**NEWS FLASH!** Ncdu 2.5 adds support for parallel scanning, but it's not
+## Notable updates
-(yet?) enabled by default. To give it a try, run with `-t8` to scan with 8
+
-threads. If you're running an unusual setup, such as networked storage, odd
+Parallel scanning
-filesystems, complex RAID configurations, etc, I'd love to hear about the
+:   Ncdu 2.5 adds support for parallel scanning, but it's not enabled by
-performance impact of this new feature. Feedback is welcome on the [issue
+    default. To give it a try, run with `-t8` to scan with 8 threads. If you're
-tracker](https://code.blicky.net/yorhel/ncdu/issues) or through mail @
+    running an unusual setup, such as networked storage, odd filesystems,
-[projects@yorhel.nl](mailto:projects@yorhel.nl).
+    complex RAID configurations, etc, I'd love to hear about the performance
-<br>
+    impact of this new feature. Feedback is welcome on the [issue
-If you want to run benchmarks, `-0 --quit-after-scan` can be useful to disable
+    tracker](https://code.blicky.net/yorhel/ncdu/issues) or to
-the browser interface, or run with `-0o/dev/null` to benchmark JSON export.
+    [projects@yorhel.nl](mailto:projects@yorhel.nl).[^1]
+
+Binary export
+:   Ncdu 2.6 adds a new binary export format that better works with parallel
+    scanning, offers built-in compression and supports browsing directory
+    trees that are too large to fit in memory. To give it a try, use the `-O`
+    flag instead of `-o`.
+
+Colors
+:   Ncdu has had color support since version 1.13. Colors were enabled by
+    default in 1.17 and 2.0, and then later disabled again in 1.20 and 2.4
+    because the text was not legible in all terminal configurations.
+
+    If you do prefer the colors, add `--color=dark` to your [config
+    file](/ncdu/man#configuration). Maybe at some point in the future we'll
+    have colors that *are* readable in every setup.
 
 ## Download <a href="/ncdu/feed.atom"><img src="/img/feed_icon.png" alt="Atom feed"></a>
 
 Static binaries
 :   Convenient static binaries for Linux. Download, extract and run; no
     compilation or installation necessary:
-    [x86](/download/ncdu-2.5-linux-x86.tar.gz) -
+    [x86](/download/ncdu-2.6-linux-x86.tar.gz) -
-    [x86_64](/download/ncdu-2.5-linux-x86_64.tar.gz) -
+    [x86_64](/download/ncdu-2.6-linux-x86_64.tar.gz) -
-    [ARM](/download/ncdu-2.5-linux-arm.tar.gz) -
+    [ARM](/download/ncdu-2.6-linux-arm.tar.gz) -
-    [AArch64](/download/ncdu-2.5-linux-aarch64.tar.gz).
+    [AArch64](/download/ncdu-2.6-linux-aarch64.tar.gz).
 
 Zig version (stable)
-:   2.5 (2024-07-24 - [ncdu-2.5.tar.gz](/download/ncdu-2.5.tar.gz) - [changes](/ncdu/changes2))
+:   2.6 (2024-09-27 - [ncdu-2.6.tar.gz](/download/ncdu-2.6.tar.gz) - [changes](/ncdu/changes2))
 
     Requires Zig 0.12 or 0.13.
 
@@ -106,3 +121,8 @@ There's no shortage of alternatives to ncdu nowadays. In no particular order:
 - [K4DirStat](https://github.com/jeromerobert/k4dirstat) - Qt, treemap.
 - [xdiskusage](http://xdiskusage.sourceforge.net/) - FLTK, with a treemap display.
 - [fsv](http://fsv.sourceforge.net/) - 3D visualization.
+
+
+[^1]: If you want to run benchmarks, `-0 --quit-after-scan` can be useful to
+    disable the browser interface, or run with `-0o/dev/null` to benchmark JSON
+    export.

dat/ncdu/binfmt.md

@@ -0,0 +1,364 @@
+% Ncdu Binary Export File Format
+
+This document describes the new binary file format added in ncdu 2.6.  This
+format offers the following advantages compared to the [JSON export file
+format](/ncdu/jsonfmt):
+
+- Support for exporting data from a multithreaded filesystem scan with minimal
+  thread-local buffering and minimal synchronisation between threads.
+- Support for reading the directory tree in depth-first, breath-first and mixed
+  iteration order, thus permitting interactive browsing through the tree
+  without reading the entire file.
+- Cumulative directory sizes are included in the exported data, allowing
+  readers to display this data without walking through the entire tree.
+- Built-in support for compression.
+
+These features come at the cost of increased complexity. The JSON format is
+generally easier to work with and therefore still the recommended approach for
+external tooling to interact with ncdu's export/import functionality.
+
+A binary export can be created with the `-O` option to ncdu. It is also
+possible to convert to and from the JSON format:
+
+```
+ncdu -O export.ncdu /         # Scan root, write to 'export.ncdu'
+ncdu -f in.json -O out.ncdu   # Convert from JSON to binary
+ncdu -f in.ncdu -o out.json   # Convert from binary to JSON
+```
+
+# Format description
+
+## File signature
+
+An exported file starts with the following file signature (in hex):
+
+```
+bf 6e 63 64 75 45 58 31
+```
+
+Formatted as a C string, that is `"\xbfncduEX1"`.
+
+Non-backwards compatible changes to the export format should use a different
+file signature. N.B. A different compression algorithm is a non-backwards
+compatible change.
+
+## Block format
+
+The file signature is followed by one or more *blocks*. A block has the
+following format:
+
+-------  -------   ---------------
+TypeLen  4 bytes   Big-endian type + length of this block
+Content  n bytes   n = Length - 8
+TypeLen  4 bytes   Repeat of TypeLen
+-------  -------   ---------------
+
+The high 4 bits of the *TypeLen* indicate the block type, the lower 28 bits
+encode the length of the block, including the header and footer.
+
+The *TypeLen* is repeated at the end of the block to allow for reading the file
+in both forwards and backwards direction.
+
+The block type determines how the *Content* should be interpreted. There are
+currently two block types:
+
+Type  Meaning
+----  --
+   0  Data block
+   1  Index block
+----  --
+
+Parsers should ignore blocks with an unknown type.
+
+A valid file must have at least one data block and exactly one index block. The
+index block must be the last block in the file.
+
+## Data blocks
+
+Data blocks have the following contents:
+
+----------------  -------  ------
+Number            4 bytes  Big-endian unsigned block number
+Compressed\_data  n bytes
+----------------  -------  ------
+
+Every data block must have a unique number, starting from zero and ideally (but
+not necessarily) allocated without gaps. Data blocks may appear in a different
+order than their numbering.
+
+Data is compressed with [Zstandard](http://www.zstd.net/). Data must be
+compressed in a single frame and the uncompressed size must be available
+through `ZSTD_getFrameContentSize()`, so that readers can pre-allocate a
+properly-sized buffer for decompression.
+
+The total length of a data block, including block header and footer, must not
+exceed 16 MiB minus one byte. The total size of the decompressed data must also
+not exceed 16 MiB minus one byte.
+
+The decompressed data consists of a stream of one or more *Items* (see below).
+
+## Index block
+
+The index block provides a lookup table for data blocks and a reference to the
+root item:
+
+---------------  ----------
+Block\_pointers  n\*8 bytes
+Root\_itemref    8 bytes
+---------------  ----------
+
+*Block\_pointers* is an array containing an 8-byte pointer for each data block
+in the file. Pointers are indexed by block number, so the first pointer is for
+block number 0, the second pointer for block number 1, etc. Each pointer is
+interpreted as a 64bit big-endian unsigned integer. The higher 40 bits indicate
+the byte offset of the data block header, relative to the start of the file.
+The lower 24 bits indicate the block length and must be equivalent to the
+length in the *TypeLen* of the corresponding data block. An all-zero value
+indicates that there is no block with this number in the file.
+
+The last 8 bytes of the index block represent an unsigned big-endian integer
+that refers to the root item of the directory tree. See *Itemref* below.
+
+## Itemref
+
+An *Itemref* encodes a reference to an *Item*, there are two types:
+
+Absolute
+:   An absolute *Itemref* is a 64bit unsigned integer that encodes a block
+    number in the higher 40 bits and a byte offset of the start of the item
+    within the block in the lower 24 bits. Every item in the file has exactly
+    one absolute *Itemref* value. The *Root\_itemref* in the index block must
+    be absolute.
+
+Relative
+:   A relative *Itemref* is a negative integer that represents the byte offset
+    of the referenced item relative to the start of the item containing the
+    reference. Relative references can only reference a previously written item
+    within the same block.
+
+## Item
+
+An *Item* represents a file or directory entry, encoded as a
+[CBOR](https://cbor.io/) map.  Key/value pairs may be encoded in any order and
+unknown keys are ignored.  Summary of keys recognized by ncdu:
+
+ Key  Field     Value
+----  --------  --------
+   0  type      i32
+   1  name      String
+   2  prev      Itemref
+   3  asize     u64
+   4  dsize     u64
+   5  dev       u64
+   6  rderr     bool
+   7  cumasize  u64
+   8  cumdsize  u64
+   9  shrasize  u64
+  10  shrdsize  u64
+  11  items     u64
+  12  sub       Itemref
+  13  ino       u64
+  14  nlink     u32
+  15  uid       u32
+  16  gid       u32
+  17  mode      u16
+  18  mtime     u64
+----  --------  --------
+
+**Common fields for all items**
+
+type
+:   Mandatory. A negative value indicates that the item that has been excluded
+    from the size calculations for some reason, positive values are used for
+    different item types:
+
+    ---  --
+     -4  Excluded with `--exclude-kernfs`
+     -3  Excluded with `-x`
+     -2  Excluded by pattern match
+     -1  Error while reading this entry
+      0  Directory
+      1  Regular file
+      2  Non-regular file (symlink, device, etc)
+      3  Hardlink candidate (i.e. stat().st_nlink > 1)
+    ---  --
+
+    Unrecognized negative values are treated as equivalent to -2, unrecognized
+    positive values are treated as a non-regular file (type=2).
+
+name
+:   Mandatory. Ncdu always encodes the name as a byte string, but also accepts
+    UTF-8 text strings. Ncdu does not support indefinite-length CBOR strings,
+    the name must be encoded with a known length.
+
+prev
+:   Reference to the previous item in the same directory. This field must be
+    absent if this is the first item in a directory. This field forms a
+    singly-linked list of all items in a directory.
+
+**Fields for type >= 0**
+
+asize
+:   Apparent size of this file/directory as reported by `stat().st_size`.
+    Optional, defaults to 0.
+
+dsize
+:   Disk usage of this file/directory as reported by `stat().st_blocks`
+    multiplied by the block size. Optional, defaults to 0.
+
+**Fields for type = 0**
+
+dev
+:   Device number. Optional, defaults to the same device number as the parent
+    directory, or 0 of this is the root item.
+
+rderr
+:   Whether an error occurred while reading this directory. When *true*, an
+    error occurred while reading the directory list itself and the list may
+    therefore be incomplete. When *false*, an error occurred while reading a
+    child item. This implies that somewhere in this sub-tree there must be at
+    least one item of `type=-1` or a directory with `rderr=true`.
+
+cumasize
+:   Cumulative apparent size of this directory. Optional, defaults to 0.
+
+cumdsize
+:   Cumulative disk usage of this directory. Optional, defaults to 0.
+
+shrasize
+:   Shared apparent size. Optional, defaults to 0.
+
+shrdsize
+:   Shared disk usage. Optional, defaults to 0.
+
+items
+:   Cumulative number of items in this directory. Ncdu currently caps this
+    number to `2^32-1` when reading, but supports larger numbers when
+    exporting. Optional, defaults to 0.
+
+sub
+:   Reference to the last item in this directory, or absent if the directory is
+    empty.
+
+**Fields for type=3**
+
+ino
+:   Inode number.
+
+nlink
+:   Number of links to this inode.
+
+**Extended information**
+
+These fields are only exported when the `-e` flag is passed to ncdu. They are
+relevant to all items with type >= 0.
+
+uid
+:   User id.
+
+gid
+:   Group id.
+
+mode
+:   File mode.
+
+mtime
+:   Last modification time as a UNIX timestamp.
+
+# Limitations
+
+Compressed data block size
+:   16 MiB minus 1 byte. This limit comes from *Block\_pointers* in the index
+    block using 24 bits to encode the block length.
+
+Uncompressed data block size
+:   16 MiB minus 1 byte. This limit comes from *Itemref* encoding item offset
+    in 24 bits.
+
+Largest data block number
+:   33,554,428. The size of the index block is limited by the 28-bit length in
+    the block's *TypeLen* header, which limits the number of *Block\_pointers*
+    it can hold to `((2^28 - 1) - 16) / 8` (subtract one to get the maximum
+    block number because counting starts at 0).
+
+Compressed data size
+:   Excluding block overhead, the total amount of compressed data is limited to
+    about 1 TiB. This is limited by *Block\_pointers* using 40 bits to encode
+    the data block offset within the file.
+
+Uncompressed data size
+:   Limited by either the maximum number of data blocks or the compressed data
+    size, depending on compression ratio and the chosen data block size.
+    Assuming the number of data blocks is the limit, about 512 TiB of
+    uncompressed data can be stored with the maximum data block size of 16 MiB.
+    Ncdu's adaptive block size selection has a limit of about 40 TiB.
+
+The real question is how many items an export can hold with the above limits in
+place. This will heavily depend on the average encoded item size and the
+compression ratio, both of which can vary wildly from one directory structure
+to another.
+
+I've had one report with ~1.4 billion files resulting in a ~21 GiB file.
+Extrapolating from that and assuming the compressed data size is the limiting
+factor, this format could hold ~68 billion items. Increasing the compression
+level and using larger data block sizes to further improve compression ratio,
+one could perhaps store about 100 billion items. On the one hand, that sounds
+like an insane number nobody will ever reach. On the other hand, a decade ago I
+couldn't imagine people having more than 100 million files, yet here we are.
+
+On the upside, all the major limitations can be attributed to the maximum size
+and format of the index block. It's possible to implement an alternative index
+format in the future that can be automatically switched to whenever any of the
+above limits are exceeded, thus providing a seamless upgrade path without
+breaking compatibility for the existing exports that do fit within the limits.
+
+# Security considerations
+
+Directory trees can get very large and you can easily exceed available RAM when
+attempting to read everything into memory. Reading only small parts of the tree
+can help cut down on memory use, but it's still a good idea to implement limits
+or detect and handle when you're about to run out of memory.
+
+There are several places in the format where byte offets are used to refer to
+blocks or items. These offets must be validated to ensure that they stay within
+the bounds of the respective file or block. In particular, itemref offsets
+could potentially refer to memory before (in the case of a relative itemref) or
+after (absolute itemref) the decompressed data, and pointers in the index block
+could refer to offsets beyond the end of the file.
+
+The CBOR encoding used for items is self-delimiting, but a badly formatted item
+may not be properly terminated before the end of the decompressed block
+contents. Readers should take care that this does not lead to reading past the
+allocated buffer.
+
+In a well-formed directory tree, each item is referenced exactly once by either
+the *Root\_itemref* or a *pref* or *sub* field. However, it is also possible to
+construct a file where this is not the case, and implementers should be aware
+that itemref loops are possible.
+
+# Implementation notes
+
+Data block size
+:   It is up to the file writer to choose a suitable data block size. This is a
+    compromise between compression efficiency and memory use: larger blocks
+    compress better but also require more memory, both for reading and writing.
+    Ncdu currently keeps 8 uncompressed blocks in memory when reading and one
+    block per thread when writing. Ncdu starts with blocks of 64 KiB, but
+    gradually increases the size to 2 MiB for very large directory trees in
+    order to not bloat the index size too much and to prevent running into the
+    maximum data block number limit.
+
+Testing
+:   If you're implementing a custom writer for this format, make sure to check
+    out the
+    [ncdubinexp.pl](https://code.blicky.net/yorhel/ncdu/src/ncdubinexp.pl)
+    script in the git repository. Ncdu only reads the parts of a file that it
+    actually needs, so passing a file to ncdu is no guarantee that it is
+    well-formed. The ncdubinexp.pl script is more thorough in validating file
+    correctness but misses a few invariants that ncdu does check for, so
+    the best way to verify a file is to run both:
+
+    ```
+    ncdu -f file.ncdu -o/dev/null   # Read entire tree and export to /dev/null
+    ncdubinfmt.pl <file.ncdu        # Read and verify the entire file
+    ```

pub/download/ncdu-2.6-linux-aarch64.tar.gz.asc

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEdEYNMrgIEOupr6LpYjlMaYwnOfoFAmb2dBYACgkQYjlMaYwn
+Ofpb/w/5AdIemzXq9dhGIB81pUqh730fZ8E6aV6YxvCMqnzJWZD/MFuiEoDGsX3/
+edMQJgfSXhEMfAOHwPL53YhqKorRdYRPGLbq+yVknCf1ePhEK/CoMiVVzwu6mC2R
+apYY5EMUDPWdlBUKp4Is6z5LaxHRAWPKdOndbNG2iAQ8QS8ww5GWNmXbxEunuhpy
+KtyZtArl9DsyD5SEe4Gvypdj74f99CEMB0IebNftduOR7u2HaAljVZGETo/F69BM
+x4LkDUgTECtgDazcDtqOZpGBfPGaw0EEp4TiNpXOTtNqAbbQ0T32yGQt+MJ5HqDz
+xmqS2JYXHAw6sPjMkWKgLizRGwBRyab4uzyrrzh4qtmt9xk8+h0pdKIdu7BhjVlN
+uL59qYMaWB0Gl3S1uWSze1lhRY5X2dedboainOyjkYDJu8JIhoNKSic09CCA7569
+tKeywg9714+QQQU9Y82yyysFCGEUWzE/jb9AIVN+0OrF6kVUFSJwC7jVRlsdAV3j
+G3MJwzgOCvM+u1ZbYBJ7J7m35UQhSWA7vAi8ajtFJHS0EkJn7+TQHCYPP+FLMCHE
+BqIDlL4dZ8nNW6HbGD0xPzJM3SpP1WLb5fEsRE5a0K5hkLcNTjA22Dhae+aPWsRl
+seY68xqVAPK7A3DvI+i1nyM33sorbjEkqUrLDIGgdX4mr5ucJyU=
+=m9kG
+-----END PGP SIGNATURE-----

pub/download/ncdu-2.6-linux-aarch64.tar.gz.md5

@@ -0,0 +1 @@
+cf0b7435bc71eebf92572000ea687c36  ncdu-2.6-linux-aarch64.tar.gz

pub/download/ncdu-2.6-linux-aarch64.tar.gz.sha1

@@ -0,0 +1 @@
+7805b682ea4b9e808848d467e361854ccc3b3a91  ncdu-2.6-linux-aarch64.tar.gz

pub/download/ncdu-2.6-linux-aarch64.tar.gz.sha256

@@ -0,0 +1 @@
+bca391ca8890ef152947e55a74088868a86ab12c9372b2155f0eea79a22184ff  ncdu-2.6-linux-aarch64.tar.gz

pub/download/ncdu-2.6-linux-arm.tar.gz.asc

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEdEYNMrgIEOupr6LpYjlMaYwnOfoFAmb2dBkACgkQYjlMaYwn
+Ofr7+g//aH9USeqI4jWLrQZXb+vdqJ+zvayHfc38KXl6eOR9xxspFbvxq0g4DsJ3
+qBpy9SDSacbRUqc6AOLQ2qj/maKoxIewS2IHOgBynjuVwrHYa6my3Pyh1VNDKOCz
+QnWpIgGlNa7vtwN25YDAq2zeMxfiGny+ywLjWH/wYdrMCuF/d9RdwtSk+4kdWp7m
+PBnj4lUoOiZq2iFysLnuee6bx6f8at+Dw5yoi2CRokNCX6kKrhSD9qRdnWQLMCvc
+i0BV63CF18jzd/3q4b6WpNrXOMTQrgJfyFmOGdO7A99vhqO3o7cvlbrzKcgFgWeP
+MMrrgBHn7wxSUzFrL0FRlaWPGYUKaZ3sMOMz1yaPi4YzL8M81hsjViRfToecixlj
+PQM9LAedoU7ZBR8T/WAqtyRGm0HUJMUbrd9n7KWb4b7ctTvglRzKKGbTKvOCCNAN
+eGt9oAY3iKtY9prAkDJlh3rq3Ig/AyZtUFVEUGXx4q0VG9MgOEAV9/N+Zn1Dhk5A
+TABUuoxwUzDzbpjzMRTFb8aVVuRCJAQG+Euo91ZMBjmdCm71OWjbCAB0odDEzv+P
+2LHaWpUmBhgVcLi4nbR39upsSKdSEkTUmvJCk86Znlf5D9VuQFN3vkQtEEk4lCbW
+OQnb8hDFxRv2cVVf9NQZEg2PWc/dRp24nTrCM2vopfrPDOzSOIQ=
+=5Qpf
+-----END PGP SIGNATURE-----

pub/download/ncdu-2.6-linux-arm.tar.gz.md5

@@ -0,0 +1 @@
+4f3a49fd981669ad4ebb356fdd37be76  ncdu-2.6-linux-arm.tar.gz

pub/download/ncdu-2.6-linux-arm.tar.gz.sha1

@@ -0,0 +1 @@
+43b4c63acf22bafc39e375cff7986c13ab1adeb9  ncdu-2.6-linux-arm.tar.gz

pub/download/ncdu-2.6-linux-arm.tar.gz.sha256

@@ -0,0 +1 @@
+efcdc50bdf2f05deda1a30159972c933e9894bec79aef8df0de2bc8beea09f46  ncdu-2.6-linux-arm.tar.gz

pub/download/ncdu-2.6-linux-x86.tar.gz.asc

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEdEYNMrgIEOupr6LpYjlMaYwnOfoFAmb2dBkACgkQYjlMaYwn
+OfpFnw//ZN65/XCEMl2Ys/g1GbDPW9+nAJpuExVdM9a7oOQC2mQ99rkOG051MrkV
+qDjTrv/0w++Lkb9VCmyhv4WTEKwY2PIAcZ/EbszuHm/kGlLAJpiN96AD7PusrTSn
+rtHtsrpFzOgMQ7wFL8/Ph6Rxb9/feMMuzpF5KA7FMcpzDaB/Q4vRpi0Wj7ipZazu
+/MviKhpjO+47HmQUVAIm1dzzNn76nxaDwer08TMs7Q6yrcdRR/4DAR/phIVBnFl8
+xQOJJV75SH8ygsNYWYvteTL22/DkcA9FJIcmK6pQLGB52266bTc5/iCXWPplAZEg
+UjQFW94DluMT8Nc8ONhj3SrMbh2MwMOe6AQpfMMwMno+xlVwnSfMQoDI+Y55S7Oc
+ZXJNB/KSaN9GzeblA+CMmyUEaUJWeQSfaBnI6H/f2PfBaJ5yv3YmJ4TpFqaxFcBG
+qwMFW94kQmNNAWF3raoK+G3dmPCa7mSpmiULozpXJRNp7x0rl51YeOz+YXCYnons
+/Q0JvGU6IzSeh8L/f9VSiNnaWmp8w+OUspSu+Etx3Y74lQ7b6Fy5dE/Q1axVi0yH
+WEDn99Pip/Y5lebsVvskKNKvGrM3kCqbUG6BmD4aIfLZNboe3gymYI1cr8hzjH8B
+1K1GQ3T9dk177W+3gB9IGiKyQcefbllDAvNvkjwwGInwXNxvrlk=
+=USGI
+-----END PGP SIGNATURE-----

pub/download/ncdu-2.6-linux-x86.tar.gz.md5

@@ -0,0 +1 @@
+94b8d9c7f076444acd14ca3bcb56ed1b  ncdu-2.6-linux-x86.tar.gz

pub/download/ncdu-2.6-linux-x86.tar.gz.sha1

@@ -0,0 +1 @@
+fe59de52ec84206f47a6466e7ce3e9b68836dbf7  ncdu-2.6-linux-x86.tar.gz

pub/download/ncdu-2.6-linux-x86.tar.gz.sha256

@@ -0,0 +1 @@
+eb2345744578c390d02364988dad18ba3c14cb5dce96143ba3085abfce40f366  ncdu-2.6-linux-x86.tar.gz

pub/download/ncdu-2.6-linux-x86_64.tar.gz.asc

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEdEYNMrgIEOupr6LpYjlMaYwnOfoFAmb2dBkACgkQYjlMaYwn
+OfonvhAAzZ8VSGho+2TW3o9Val9+V7366M5UVapi5TOwCZ8t+SliiioZxV/bsciT
+2LFbPtuU7OxiyQT4xyw1pu54WZTGCWB4xl1g0i3fAq8jPUrQedV3JqHQgaC1QL5s
+AYKcooWB9s34iWfQRyAj9UAibFuh8T4ezvYDLPCmAkvt5Imu7WkBdmSk1V9v2+wM
+zEG8aJ3cI51koQoJbEV6EIRt5KDZJ1AtIvAkGo4qwOekQUuQXnfANlF8Rroksf07
+J/CPBVH89VneWQJLexqKVBVZM28Jk6F7M2eNz+0cK1vFKPv8aFCFQ1RWb3zs2915
+pft6Nt7DvO+BCVZI72aiHcUO5VTZAcKtxX7523k1kdbH+wfYJX5ACiL/QGVZVr0I
+9X9Oh+Ycm6dXrsp4eEMZHSNe5X6z++yiCOFNUALtPVfP4wT0F/LhtRC7A6mmP2MB
+LzqrxpYTjAPO4a2IBVOyJ1y5m7ihsFRL4cqro8Ropl71823JMxfS8WO4lwFW6gsT
+0RtNiS2fU399880OdRyGjbqZavjk4zqoalArn/LP+HKN5a6nugFwaBWirRFn4nKe
+ZfH3Nsfi8nVUU3iumTwksskI+roqQbKC+07JU2mVDAxAfBS7mscJq4xJ/M1nVbrc
+JZDPVJzjTAaBUuOy7wIf/5cR7gexQjq+3y0n1gj1tGMfYviuOT4=
+=WAKu
+-----END PGP SIGNATURE-----

pub/download/ncdu-2.6-linux-x86_64.tar.gz.md5

@@ -0,0 +1 @@
+6a6e25de0827f0a422f7997ef2075573  ncdu-2.6-linux-x86_64.tar.gz

pub/download/ncdu-2.6-linux-x86_64.tar.gz.sha1

@@ -0,0 +1 @@
+f8348cc0c25c434874e136411fcaf8f13e1da08d  ncdu-2.6-linux-x86_64.tar.gz

pub/download/ncdu-2.6-linux-x86_64.tar.gz.sha256

@@ -0,0 +1 @@
+cd8539fdfeea1920174ba408b1be88e4c8579d5443b71178fb6841469f92b527  ncdu-2.6-linux-x86_64.tar.gz

pub/download/ncdu-2.6.tar.gz.asc

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEdEYNMrgIEOupr6LpYjlMaYwnOfoFAmb2dBkACgkQYjlMaYwn
+OfplKhAAxLF2ZSE+INlgjsjOZStwFfWLVmGRhtJVRvQdGeWVgt9me6XwtpbVIh7z
+BQH7M334yinJLjKATLci/Jbto6LQadq9tdYp+ZkOxS7cOoSrhwgsQFHBlerQdIVw
+fEMnfsRYsssylMgJTmZijNhq4bbTYn69idNroMrTvPM+Cd4iVThlywaA8JkfHo3s
+7aGeVvcln6cCOC2Ilb37HJ+i/FYxJrS/JcqCyOSox01Ulf1ngnLXsrae7iHyCHB4
+rMrLrk2ZaFkONJoRzo7LdlCt/VTIGDGS7cExAieDygd7Xv72/60jJlZIWHjLitI7
+FPXmBf/xNH3ZUaDOMwY6CzuNm/LqvyxUgGjL7aE5jwO/3Z3LQVqCMWk4erx5dJnh
+hge/ttH+BLXExINtZHyTSCkqXtflFNKijw9bfwe5p2YlX/cdy1p6ga1aH7zY4Omw
+lf4lhN6c7jqxIYD4PA9EEEXZKUvtqGy/G51BxDQ9YFfL9ZL52zFn7U1ZNVZpiVnw
+oBp26a8BoTsJfvHDgjUobRFp+46OA3FD5+mM+o+LpwZtmmbBuuY3cLUlCtaBKD5d
++3BY4DIixHaUTaeISqikeUHn0hq5WPijs1qLMmlbsONLwKjKtNyu36al4rdI8Wks
+JNHj7PxkDbMy//c2ajRGAQ7qgkyQ3vddALv+/U6cVcaZbmTG1Us=
+=qgu7
+-----END PGP SIGNATURE-----

pub/download/ncdu-2.6.tar.gz.md5

@@ -0,0 +1 @@
+5f9d3bdc13b5e5fe4d36058b3001d1ba  ncdu-2.6.tar.gz

pub/download/ncdu-2.6.tar.gz.sha1

@@ -0,0 +1 @@
+699a2804fd7109d990e6283212d3e39329ebf13f  ncdu-2.6.tar.gz

pub/download/ncdu-2.6.tar.gz.sha256

@@ -0,0 +1 @@
+3f471ebd38b56e60dab80c27e3af1d826666957f02d9e8419b149daaf7ade505  ncdu-2.6.tar.gz

template.html

@@ -66,7 +66,8 @@
                         <li><a href="/ncdu" class="item2-ncdu">Info</a></li>
                         <li><a href="/ncdu/man" class="item2-ncdu-man">Docs</a>
                             <ul>
-                                <li><a href="/ncdu/jsonfmt" class="item2-ncdu-jsonfmt">File Format</a></li>
+                                <li><a href="/ncdu/jsonfmt" class="item2-ncdu-jsonfmt">JSON Format</a></li>
+                                <li><a href="/ncdu/binfmt" class="item2-ncdu-binfmt">Bin Format</a></li>
                             </ul>
                         </li>
                         <li><a href="/ncdu/changes2" class="item2-ncdu-changes2">Changes (2.x)</a></li>