Brian C. Lane wrote:
On Wed, Aug 22, 2012 at 11:38:47PM -0500, David A. Marlin wrote:
Interesting. So it uses the amount of RAM on the host in its
calculation, but not the swap on the host?
Correct, the disk it is using is a disk image, not the host's disk.
Understood. Ours is probably not a typical use-case. This
particular image is for the Raspberry Pi. We try to create a small
rootfs image that can be downloaded and copied to flash (small size
is important, typically ~1GB). On first boot we grow the / (root)
partition to fill the flash device (whatever its size) and set up a
swap file (user specified size) rather than create a dedicated swap
partition. Adding a swap partition of 500 MB adds 500MB to the
image size to be downloaded and copied to flash (~50% larger).
I guess if we ran this on a builder that had 2GB memory this would
not even be an issue. Either way, we can work around it.
Can you use a raw filesystem image, or does it need to be partitioned?
When the .iso is made it copies the / out of the partitioned image into
squashfs.img for use on the iso. I could do something like that, but
without the iso step.
We don't actually create an iso image or squashfs.img. We use:
--make-disk --no-virt --image-only --keep-image
and use the disk image by copying it directly (partitions and all) to flash.
d.marlin
========
------------------------------------------------------------------------
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
