On 05/17/2015 01:01 AM, Gordan Bobic wrote: >> But, as the pi normally boots without an initrd (which I like) and >> adjusting it to have an initrd seems non-trivial (according to google) I >> decided to leave it at ext4. > > How is it non-trivial? What boot loader does it use? U-boot handles > this reasonably gracefully.
It doesn't use uboot. There are a couple of binary blobs that need to be with the right filename on the first partion (vfat of course). The last one will look for 'kernel.img', 'cmdline.txt' and 'config.txt'. Apparently it is possible to specify an initrd in the cmdline.txt and config.txt, but there are many stories that it stopped working after normal kernel updates. One of the things is that, apart from a filename, you need to tell it at what memory location it should be loaded and the filesize in hex. Another option is to somehow put your initrd inside the kernel. I have never seen how that should be done. But, more importantly, that would require custom kernels. I'm not saying it cannot be done, only that there are lots of people having issues getting it to work reliably. >> Things I'm still considering are nodiratime and data=writeback for ext4. > > Is fiddling with FS options really that advantageous over letting the > user just configure it the way they want, including picking the FS > they want themselves? > Of course everybody is free to choose their own FS. And they already are. I would advocate to have one good image for each device. That includes our best choice of FS (with reasonable options), ntp/chrony on for devices without hwclock, appropriate sysctl settings (if they differ from default), the right (extra) modules loaded or blacklisted, etc. This will enable users to get up-and-running quickly, which is something i think is important. Having more than one image (per device) to maintain will be quite a burden on us. For all 'special' setups, we might just explain how to do that on the wiki. In the end, it is not that difficult. Thinking about this, if we create a better comps.xml, we could instruct people to 'yum groupinstall base --installroot=xxx --config=yyy' instead of creating all kinds of tar.gz files. Jacco _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
