Hi there! On Tue, 28 Jul 2009 10:40:23 +0200, Lionel Elie Mamane wrote: > On Tue, Jul 28, 2009 at 10:28:56AM +0200, Steffen Moeller wrote: >> Lionel Elie Mamane wrote: >>> That's not it, it is configure-uboot.sh
configure-uboot.sh is not part of install.sh. Instead, look at the action_uboot function, which IMHO should be *completely* removed, together with configure-uboot.sh: http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-July/001588.html >>> "rootfstype=ext2". Changing that to rootfstype=ext3 solves the >>> problem. > >> Ah. ok. I never touched the uboot parts since I don't use it. I >> recall that there was a constraint towards ext2 somehow - whoever >> could clarify the issue for the archives (again?), please step >> forward. > > Grub has the following "problem" with ext3 (and journal filesystems in > general), which by similarity uboot may have: it does not know about > the journal, so if the filesystem is not cleanly unmounted, it runs > the risk of not being able to read it. I can imagine that as long as > the file (and the directory it is in and the parent directory and its > parent, etc) are not touched by the journal, it would still work, I'm > not sure. On my desktops / laptops I usually have an ext2 /boot > partition mounted "sync" for this reason. We are talking about the rootfsype, not the /boot partition, thus there is no problem at all WRT the boot loader since the kernel is in /boot. FWIW, the Debian kernel for Openmoko will be based on the standard Debian kernel infrastructure, which means that it will be configured to load an initrd by default. Basicallly, the uImage.bin will contain both the kernel and the initrd. This means that this file can be on any partition (including vfat). Thx, bye, Gismo / Luca
pgp1HPdcMq672.pgp
Description: PGP signature
_______________________________________________ pkg-fso-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint
