Skip to content

Releases: CalebQ42/squashfs

Fix stray println

10 Dec 22:12
e9fdd89
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.0.3...v1.0.4

Bug fix

26 Nov 23:14
Compare
Choose a tag to compare

Fixed issue with fragment, id, and indode reference table values on block borders reported by @willmurphyscode in #30.

Offset

21 Sep 01:14
Compare
Choose a tag to compare

Re-added NewReaderAtOffset

Improved performance

17 Jul 14:32
Compare
Choose a tag to compare

Improved extraction performance slightly by changing some pointers to normal values.

v1.0.0

28 Dec 06:20
e9de9e6
Compare
Choose a tag to compare

This is the first version I'm considering "stable" (ish). I think most parts of the library is now in a stable enough spot that no changes to the actual API should be necessary from now on. This version does have some small changes to the API compared to v0.8.4, but it should be fairly easy to switch over.

  • Separated out the FUSE implementation into it's own library (as requested by #25).
  • Separated out a "low"-er level library from the main library.
    • This library is located at github.com/CalebQ42/squashfs/low and is named squashfslow
    • The main library is largely just a easier to use implementation of the low library.
    • This was necessary to expose a lot of information that's needed for the FUSE library without making the library overly complex for must use cases
  • Re-wrote a lot of the extraction code to fix lingering issues where CPU and RAM get completely devoured
    • Allow setting how many goroutines are used during extraction, with defaults based on runtime.NumCPU()
    • Added FastOptions() to attempt to extract archives as quick as possible
      • This will pin your CPU to 100% for the duration
    • This does seem to slightly improve extraction speed, but only marginally.
    • Fixed #27

Sparse Fragments?

12 Aug 18:32
Compare
Choose a tag to compare
Sparse Fragments? Pre-release
Pre-release

Added the ability for a fragment to be sparse (filled with zeroes). This is not documented as being possible, but as with #24 it might be possible and might be the cause of #22.

Additional fix

11 Aug 23:18
Compare
Choose a tag to compare
Additional fix Pre-release
Pre-release

Applied fix from v0.8.2 to file's Read in additional to WriteTo

Fix sub blocksize sparse files

11 Aug 20:33
Compare
Choose a tag to compare
Pre-release

Fix #24

Fix

17 Apr 16:41
Compare
Choose a tag to compare
Fix Pre-release
Pre-release

Fixed an error not being reported correctly.

Large file fixes

17 Apr 15:48
Compare
Choose a tag to compare
Large file fixes Pre-release
Pre-release

This release has some minor breaking changes:

  • ExtractWithOptions now uses a *ExtractionOptions instead of ExtractionOptions. DefaultOptions now returns a pointer as well.
  • ExtractionOptions.FolderPerm is now ExtractionOptions.Perm and is only used when ExtractionOptions.IgnorePerm is set.

Fixes:

  • Extracting files is now properly limited. This prevents out of control memory usage when extracting larger archives.
  • Folder's permissions are only set after all it's contents are extracted.
    • Fixes issues relating to the user not having permission to write the folder's contents

Other:

  • Added ExtractVerbose and ExtractIgnorePermissions for improved ease of use.