nbdkit-release-notes-1.6(1)

πŸ’– nbdkit-release-notes-1.6 πŸ’–

okay bestie, welcome to the NBDKIT manual page for nbdkit-release-notes-1.6 β€” yes this is a whole manpage just for the tea on one release, and honestly? iconic behavior. 🫢


✨ NAME ✨

nbdkit-release-notes-1.6 β€” the release notes for nbdkit 1.6, aka the glow-up era 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

So these are the release notes for the nbdkit stable release 1.6. It's the whole rundown of the major changes since 1.4, no crumbs left behind. πŸ’…

And mark your calendars: nbdkit 1.6.0 was released on 28th August 2018. πŸŽ‚

🌈 New features 🌈

okay so THIS is the section, the main character moment, the part we're all here for:

  • You can now write plugins in the Lua scripting language β€” go check nbdkit-lua-plugin(3) 🧚
  • nbdkit and the common plugins are now "63 bit clean": the maximum disk size supported is 2⁢³-1 bytes, and the core server plus plugins now have extra tests to make sure this actually works β€” even on 32 bit machines. slay πŸ’ͺ
  • Multiple improvements to the nbdkit-file-plugin(1) so that zeroing and trimming perform better, work correctly with block devices, and work on older Linux kernels β€” big ups to Nir Soffer and Eric Blake 🫢
  • New nbdkit-pattern-plugin(1) β€” it generates a simple, fixed test pattern for testing nbdkit filters and NBD clients. cute and useful ✨
  • New nbdkit-truncate-filter(1) which can: truncate or extend the size of plugins, or round the size up or down to the next multiple of a power of 2. Lowkey a lifesaver for NBD clients like qemu that can only handle NBD sizes that are a multiple of 512 bytes πŸ‘‘
  • New nbdkit-error-filter(1) β€” use it to inject errors into the protocol, so you can test how clients handle and recover from errors. chaos as a service, but for science πŸ’€
  • New nbdkit-data-plugin(1) lets you specify (small) disk images directly on the command line. tiny disk, big energy πŸ“
  • Enhanced error reporting in the Python plugin β€” full tracebacks from errors are now displayed instead of being lost like before. no more "where did my error go" era 😭
  • "NBD_OPT_GO" is now supported, so we can return errors when negotiating the export name πŸ”₯
  • Support for logging error messages to syslog πŸ“
  • nbdkit can now be compiled with Clang (as well as GCC) 🌟
  • nbdkit can now be compiled on FreeBSD 🐧
  • nbdkit-vddk-plugin(1) is compiled unconditionally. You no longer need to install the proprietary VDDK to compile it. the way that just works now πŸ™ˆ
  • Debug messages now include the name of the filter when invoked from a filter context πŸ”
  • Debug flags (the -D option) provide lightweight debugging for plugin authors πŸ’œ

πŸŽ€ Acknowledgements πŸŽ€

Thanks to everyone who contributed, and especially to Nir Soffer and Eric Blake. literal legends, no cap πŸ‘‘


⭐ SEE ALSO ⭐


🌸 AUTHORS 🌸

  • Eric Blake
  • Richard W.M. Jones

Copyright Red Hat


πŸ“œ LICENSE πŸ“œ

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name of Red Hat nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY RED HAT AND CONTRIBUTORS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 😀 (yes bestie, the ALL CAPS is load-bearing, do not skip it)

and that's a wrap 🫢 this page came from nbdkit-1.48.1, dated 2026-08-29, and it's filed under nbdkit-release-notes-1.6(1). k byeee πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from