wcampbell

Surely. I already have `backhand-cli` for the next release, I could just extract the cli as-a- llibrary.

I haven't thought much about where the code would be, or what the API would be. But I expect the duplication to be the most between this package and `backhand-cli`....

The API would mostly have the `main` of the bins, with the Clap argument structs as arguments? Just thinking out loud.

Thanks! I'll see when I get around to this. But looks like a never ending adventure.

Some TP-Link gpl code has the following patch to the kernel ``` $ diff -bur ./fs/squashfs ~/projects/linux/fs/squashfs > patch ``` ```diff --- /fs/squashfs/xz_wrapper.c 2021-11-09 09:57:38.000000000 +0000 +++linux/fs/squashfs/xz_wrapper.c 2023-01-17 04:18:38.293147873 +0000...

@qkaiser starting to look into supporting custom compression algorithms. Do they use the *same* custom compression for everything, as in all data and metadata blocks?

> Some TP-Link gpl code has the following patch to the kernel > > ``` > $ diff -bur ./fs/squashfs ~/projects/linux/fs/squashfs > patch > ``` > > ```diff > ---...

Yep, its a different block length

Also linked: https://github.com/alexcrichton/xz2-rs/issues/105

You are right, we currently don't have any methods that spawn multiple threads for writing a new filesystem. You would just need a new lock on the `writer` in this...