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
v0.6 .img improvements (shrink) #86
Comments
None of the images you can download has 16GBs in size. Not sure what you mean. On the first boot, the image will expand the third partition to the maximum available size just as you suggested. 16GB are a pain in the ass when copying the entire SD card, but other than that it does not have a disadvantage. |
https://github.com/DroneBridge/DroneBridge/releases/tag/v0.6.0 Download link on 5GB archive with 16GB .img file in it. |
Ah sorry, did not check the content. I must have forgotten to shrink the img file. You can use the truncate command to shrink the third partition. I did that with the prev. releases. |
Hi, i was wondering, why does image size is 16 GB ?
I looked partable of .img file and file size on partitions and I see
The third partition is ExFAT (why?), using 13GB and contain files only for 18MB!
Writing this image to SD card with
dd
will take "insane" amount of time for writing this empty space.Why don't just make this partition 100 MB, and resize by script on first boot to end of disk ? (Is this OS limitation where debian can't resize ExFat parts? Why not use FAT32 instead ?)
Why does ExFAT needed ? Can't those file be stored on ext4 in
/DroneBridge
Folder instead of mounting this ExFAT partition ?Thanks.
The text was updated successfully, but these errors were encountered: