Skip to content

lamfold 0.1.4 and lamfold-cpio 0.1.1

Choose a tag to compare

View all tags
@glamberson glamberson released this 15 Oct 18:00
· 2 commits to main since this release
v0.1.4
d81a160

lamfold 0.1.4 and lamfold-cpio 0.1.1: Every archive of an initramfs is read, and lamfold's dependencies become minimum versions.

lamfold-cpio 0.1.1

  • Only the first archive of an initramfs was read. An initramfs is often an uncompressed early archive (CPU microcode) followed by the main one, and reading stopped at the first TRAILER!!!, so /init and the rest of the main archive were missing, with no error. Every newc or CRC archive in the chain is read now, skipping the zero padding between them as the kernel does.
  • Hard links read as empty files. newc stores the data once, on the last link; every link reads it now.
  • A compressed archive in the chain (most distributions compress the main one) is refused as Unsupported("cpio_compressed_member") instead of leaving a tree with only the microcode archive. Reading it needs a streaming decoder in lamfold.
  • CRC-format files are checked against their checksums, and anything but padding between archives is refused.
  • New GNU cpio fixtures (crates/lamfold-cpio/tests/fixtures/regenerate.sh) each fail on 0.1.0.

lamfold 0.1.4

  • Dependencies are minimums at the versions in the Debian archive instead of exact pins, so Debian builds lamfold against what its archive holds and crates.io users get bug-fix releases.
  • lzma-rust2 0.16.4 to 0.19.0, Debian's version, with no source change.

The other frontends are unchanged. Changelogs: lamfold, lamfold-cpio. lamfold is the media stack of LamBoot, from Lamco Development LLC.

Assets 2
Loading