Agreed.<div><br></div><div>Should be able to use dd or truncate to enlarge the img file, then use a partition tool to enlarge the tables, then expand the filesystem.</div><div><br></div><div>Considering the image has the rootfs resize package, it might be possible to simply enlarge the image file and be done.</div>
<div>Give it a try and let us know.</div><div><br></div><div>-Jon Disnard</div><div>irc: masta</div><div>fas: parasense</div><div><br><div class="gmail_quote">On Thu, Jan 3, 2013 at 12:49 PM, Sean Omalley <span dir="ltr"><<a href="mailto:omalley_s@rocketmail.com" target="_blank">omalley_s@rocketmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:12pt;font-family:times new roman,new york,times,serif">Seems like you should be able to dd an empty file and cat the image over a loopback interface, or maybe simply dd it. then boot and do an fdisk/resize2fs once it is booted. sort of like how you dd the image files to an sd card but to a loopback device instead. Not sure it works. :) <br>
<div><br></div> <div style="font-family:times new roman,new york,times,serif;font-size:12pt"> <div style="font-family:times new roman,new york,times,serif;font-size:12pt"> <div dir="ltr"> <font face="Arial"> <hr size="1">
<b><span style="font-weight:bold">From:</span></b> David Marlin <<a href="mailto:dmarlin@redhat.com" target="_blank">dmarlin@redhat.com</a>><br> <b><span style="font-weight:bold">To:</span></b> Jerry James <<a href="mailto:loganjerry@gmail.com" target="_blank">loganjerry@gmail.com</a>> <br>
<b><span style="font-weight:bold">Cc:</span></b> Fedora ARM <<a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a>> <br> <b><span style="font-weight:bold">Sent:</span></b> Thursday, January 3, 2013 12:46 PM<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [fedora-arm] More storage for vexpress (QEMU)<br> </font> </div><div><div class="h5"> <br>
<br>Jerry James wrote:<br>> I am on a quest to fix two of my packages that fail to build on ARM<br>> (gcl and latte-integrale). I need to get an ARM virtual machine going<br>> so I can debug the issues. It has to be an F-18 VM, too, since the<br>
> build breakage only shows up on F-18 and Rawhide.<br>> <br>> The recent f18-beta-tc3 release works, in the sense that I can boot up<br>> successfully and do some work. However, the vexpress image is much<br>
> too small. It is already 80% full as shipped. Running any yum<br>> command raises that to 86%, apparently due to downloading the yum<br>> databases/indexes. I need to install a pretty large pile of BRs to<br>
> build my packages, and there just isn't room.<br>> <br>> Is there some way of enlarging the shipped image? Thanks,<br><br>I do not know of an easy way to enlarge the shipped image, but it should not be difficult to make
a larger image. You would need a 'build' system (ARM platform with at least 1GB memory and sufficient external storage, i.e., disk) running F17 with anaconda and lorax installed from my xpfa repo. The instructions are available on the wiki:<br>
<br> <a href="http://fedoraproject.org/wiki/Architectures/ARM/Installer" target="_blank">http://fedoraproject.org/wiki/Architectures/ARM/Installer</a><br><br>The exact command I used for the Beta TC3 image was:<br><br> livemedia-creator \<br>
--make-disk --no-virt --image-only --keep-image \<br> --armplatform=None \<br> --ks=./F18-ges-beta-kickstarts/F18-vexpress-xfce.ks<br><br>The kickstart file is in my git repo:<br><br> <a href="http://fedorapeople.org/cgit/dmarlin/public_git/arm-kickstarts.git/" target="_blank">http://fedorapeople.org/cgit/dmarlin/public_git/arm-kickstarts.git/</a><br>
<br>You would only need to change the partition layout to make the root of the image as large as necessary:<br><br> part /boot --size 200 --fstype ext3 --label=boot<br> part swap --size 500 --asprimary --label=swap<br>
-part
/ --size 2200 --fstype ext4 --label=rootfs<br> +part / --size <DesiredSize> --fstype ext4 --label=rootfs<br><br><br>The only other option I can think of would be to manually create a disk image with the partitions sized to meet your needs, loop-mount both the shipped and new images, and then copy (rsync) the contents of the shipped image partitions to the new image partitions.<br>
<br>Please let me know if you have any questions.<br><br><br>d.marlin<br>==========<br><br>> --<br>> Jerry James<br>> <a href="http://www.jamezone.org/" target="_blank">http://www.jamezone.org/</a><br>> _______________________________________________<br>
> arm mailing list<br>> <a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a><br>> <a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br>
_______________________________________________<br>arm mailing
list<br><a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a><br><a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br>
<br> </div></div></div> </div> </div></div><br>_______________________________________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><br>-Jon
</div>