The difficult thing is, how can we tell the size of the image will be larger than 4 GB.
It's not easy to estimate the size before compressing.
Do you have any good suggestion?
Thanks in advance.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as I'm aware an iso file isn't compressed, so we can just sum the images files and the clonezilla boot files and warn the user that they could exceed 4gb.
The iso already warns when it will be over 4.7gb (won't fit on a dvd), so we change that warning to include if we are copying the iso to a FAT32 partition.
The zip is much the same. If the user chooses default options, the image will already be compressed with gzip, and so we can use the same process as iso file size estimation as I don't think zip will compress much more than gzip.
What do you think?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The difficult thing is, how can we tell the size of the image will be larger than 4 GB.
It's not easy to estimate the size before compressing.
Do you have any good suggestion?
Thanks in advance.
Steven.
As far as I'm aware an iso file isn't compressed, so we can just sum the images files and the clonezilla boot files and warn the user that they could exceed 4gb.
The iso already warns when it will be over 4.7gb (won't fit on a dvd), so we change that warning to include if we are copying the iso to a FAT32 partition.
The zip is much the same. If the user chooses default options, the image will already be compressed with gzip, and so we can use the same process as iso file size estimation as I don't think zip will compress much more than gzip.
What do you think?
So you did not mean to estimate the iso/zip file _before_ it's created, instead you meant to warn users that _after_ it's created?
Steven.