Narcissus: generated rootfs does not fit the corresponding sd image.

Hi!

First of all, there seems to be something wrong with the wiki/faq. None of it works, just sayes "Page not found" under the top bar.

Anyway, sorry to intrude, but I just wanted to make a quick report before the images get automatically erased. It's a small matter, really, but the generated rootfs:...

"beagleboard-panu1-xfce-image-beagleboard.tar.bz2 [230.74 MiB]: This is the rootfs 'beagleboard-panu1-xfce' for beagleboard you just built. This will get automatically deleted after 3 days." ... "Current uncompressed image size: 863M"

...does not fit the generated SD image ...

"The raw SD card image(s) below have a vfat partition populated with the bootloader and kernel, but an empty ext3 partition. You can extract the tarball to that partition to make it ready to boot. The intended size for the SD card is encoded in the file name, e.g. 1GiB for a one gigabyte card. beagleboard-panu1-xfce-image-beagleboard-sd-1GiB.img.gz [4.1 MiB]"

...which has 893388 1K-blocks set for the root fs. There's a "no space left on device" error at some point in untarring. 863M is awfully close to 893M, perhaps the limit to select which SD card size to use needs to be adjusted. I'll proceed to work on it on my own, but cannot do it today, so I wrote this email in case someone wants to have a peek at the images on server before they get deleted.

PS. Great job on the Beagleboard demo image! It's working beautifully, just got DVD subtitles working on mplayer (sub track indexing error), library issue solved which prevented booting Abiword and installed vncviewer and emacs. But the demo image is getting a little bit old. That's why I am trying to poke around in hope of building a newer image. My goal is to have gcc running onboard so I can make a "self-standing" system.

Greetings,
Panu







_______________________________________________
Angstrom-distro-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to