From Fedora Project Wiki
(New page: * The part limits don't actually guaranty that the resulting image (iso or squashfs) will be a desired size. It will depend on the amount of compression you get. Using larger values will s...) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
* The part limits don't actually guaranty that the resulting image (iso or squashfs) will be a desired size. It will depend on the amount of compression you get. Using larger values will slow down a build at least somewhat, so we don't want them to be way larger than needed. | * [[User:Bruno]]: The part limits don't actually guaranty that the resulting image (iso or squashfs) will be a desired size. It will depend on the amount of compression you get. Using larger values will slow down a build at least somewhat, so we don't want them to be way larger than needed. | ||
** [[User:Kanarip|Jeroen van Meeuwen]]: You're right, it doesn't. Because of this compression however, we need some way to prevent the compose from ending up oversized. These two sizes very roughly indicate where that magic boundary is. Of course if you fill 8192MB with a lot of plaintext files you're gonna end up with a smaller squashfs then when you fill it with a few large binaries. | |||
Revision as of 15:47, 17 January 2009
- User:Bruno: The part limits don't actually guaranty that the resulting image (iso or squashfs) will be a desired size. It will depend on the amount of compression you get. Using larger values will slow down a build at least somewhat, so we don't want them to be way larger than needed.
- Jeroen van Meeuwen: You're right, it doesn't. Because of this compression however, we need some way to prevent the compose from ending up oversized. These two sizes very roughly indicate where that magic boundary is. Of course if you fill 8192MB with a lot of plaintext files you're gonna end up with a smaller squashfs then when you fill it with a few large binaries.