-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, Can we add support stdin or pass fd as src_device? #2
Comments
Hi, thank you for your interest in the blocksync-fast program. After reviewing the issue, I have already implemented functionality to handle input from STDIN as the source image. You will only need to provide an additional parameter for data size, as that was the only problem. I am currently testing the program and making a few minor adjustments. The new version should be available within 24 hours. ✅ 😃 |
Hi, I haven't tried yet, As busy with other things. I just saw your reply, So an enhancement, Is it possible to remove the additional data size requirement? Thanks. |
Yes, I understand this request. The problem is that the program needs to know the size of the synchronized data in advance, e.g. for writing the header in the Digest file, if it uses such functionality. The functionality requires some rethinking and rewriting of some program functions. I will try to include this functionality in future versions. |
Now, I tried with something like,
xzcat /path/to/image.xz | blocksync-fast -s - -d <dst_device>
doesn't work.blocksync-fast -s <(xzcat /path/to/image.xz) -d <dst_device>
doesn't work either.The reason this feature will be useful is, We can have compressed image archives, with unused spaces to be zero, The source image will be very tight. Without stdin support, We have to use a large tmp folder with a more time consuming step.
Thanks.
The text was updated successfully, but these errors were encountered: