> Which filesystems could I use? How to know that? A simple git grep IMAGE_FSTYPES brings you up a long list. File meta/classes/image_types.bbclass seems p

> Which filesystems could I use? How to know that? A simple git grep IMAGE_FSTYPES brings you up a long list. File meta/classes/image_types.bbclass seems particular promising. And there it is https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image_types.bbclass?h=zeus#n260 https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/cl... I'm very far from claiming that Yocto is easy to understand. But you get much more than you pay for. What alternatives do you suggest with a similar functionality? Do you think the Linux kernel documentation is better? The systemd source code easy to grasp? Still, they are widely used. I tend to say the price you pay for those is that you need to employ an expert and the expert needs to spend quite some time on it. If you buy a product you are entitled to request something from your vendor. Good luck if you are a small company. I even tried when working for a 50,000 people corporation in the past and we got very little after many years of paying huge fees. In open source it's take it or leave it. Preferably take it and contribute to make it better.