On Tue, Oct 09, 2012 at 04:30:24AM -0500, Dennis Gilmore wrote: > El Tue, 9 Oct 2012 08:54:26 +0100 > Peter Robinson <pbrobinson@xxxxxxxxx> escribió: > > On Mon, Oct 8, 2012 at 10:56 PM, Till Maas <opensource@xxxxxxxxx> > > wrote: > > > It seems that the disk image boots on the dockstar, but a first "yum > > > update" got oom-killed and there seems to be no swap and not LVM on > > > the image to easily change this. IMHO a problem with the Fedora ARM > > > documentation is, that it is only a collection of reports from > > > people how they did it. It is lacking information about why > > > something was done as described or how it should be done. For > > > example the Debian documentation clearly states which uboot version > > > is required and how to update it. The Kirkwood documentation in the > > > Fedora ARM wiki only says that the proper uboot config depends on > > > the uboot version and gives an example that is supposed to work on > > > a Guru Plug Server Plus. Comparing it with the Debian documentation > > > it also shows that different hex values (addresses?) are used in > > > the uboot config for the kernel and initramfs. But why do they need > > > to be different? Or do they not need to be different? Also as far > > > as I can see there are no instructions about how the images are > > > created and why they have been chosen the way they are (no LVM, no > > > swap, device dependent names for kernel and initramfs, vfat > > > for /boot). > > not that it will explain everything but Debian ships uboot for the > kirkwood devices and add features not found in the stock uboot. ext2 > support being one of them which is why /boot is vfat we support the > stock uboot and only ship uboot where we have to preferring instead that > the vendors be responsible for supporting and supplying uboot binaries. > we are still evolving the image creation process. in f17 it was a shell > script that used yum. we are moving to use kickstarts and anaconda via > livemedia-creator Thank you for the vfat history. Are the image creation scripts available somewhere? Is there a bug tracker for them? Regards Till _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
