Comment 4 for bug 712703
Revision history for this message
| Loïc Minier (lool) wrote Re: please install clear text version of boot.scr to /boot/boot.script on rootfs | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Yes, that's exactly Guilherme's point: /boot is on rootfs, and we have separate rootfs and bootfs; bootfs is typically the first partition and a vfat which holds MLO, u-boot.bin, uImage, uInitrd and boot.scr. rootfs is extN or btrfs and contains /boot/vmlinuz, /boot/initrd. The bug asks for /boot/boot.txt, but it might or might not make more sense to use a boot.txt file on the bootfs rather than a /boot/boot.txt file on the rootfs.
BTW my preference is to have u-boot read a text file script rather than this weird boot.scr format; a patch was sent upstream 10 days ago to implement this. We need to be careful to not overwrite a custom boot.txt with an automatically generated one though; think of the update-grub mechanism for instance. There's some non-trivial amount of work to support it in the rootfs (flash-kernel etc.). I'm not sure this is a linaro-image-tools thing though; eventually, we'd just call this mechanism from linaro-image-tools rather than generating a boot.scr, but currently we mimic what flash-kernel is doing, and that's where we ought to fix this IMHO.