4 ms·

> There is a whole bunch of manuals Ah, yeah, the manual. I forgot another abysmally bad part of Yocto: the manual. Yocto documentation is the single worst do

> There is a whole bunch of manuals Ah, yeah, the manual. I forgot another abysmally bad part of Yocto: the manual. Yocto documentation is the single worst documentation I've ever dealt with. It's a huge giant wall of text which tells you... nothing concrete whatsoever. Wanna know how to change an image fs or image format? Go figure with the manual, just look at these entries: https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#ref-images https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.... https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-IMAGE_FSTYPES https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.... So concise, but even more useless. Which filesystems could I use? How to know that? Ah, don't bother. The whole manual is a huge wall of text telling you what classes, tasks, recipes and dozens of other overengineered concepts are, but nothing about how to use them beyond the basic examples. Wanna build an fs for the device with a local storage and external ssd, good luck to figure out how: decoupling where machine starts and image ends, and which part should you modify. > Without understanding the philosophy behind the whole system and the recipe language just trying to "discover" something seems indeed mission impossible to me. Yeah, it's hard to introspect something which have dozens of concepts, yet no other form of introspection but file reading. And I'm fine with file reading, but with yocto half of important stuff is concealed within the build system, leaving just strange config variables and gluing scripts on the surface, making it incomprehensible for a sane person.

usr1106 7y ago
> Wanna build an fs for the device with a local storage and external ssd, good luck to figure out how I never had to do anything even closely similar. My embedded systems have just one rootfs. I would start looking here https://www.yoctoproject.org/docs/3.0/mega-manual/mega-manual.html#creating-partitioned-images-using-wic https://www.yoctoproject.org/docs/3.0/mega-manual/mega-manua...
usr1106 7y ago
> 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.

usr1106 7y ago

> Wanna build an fs for the device with a local storage and external ssd, good luck to figure out how I never had to do anything even closely similar. My embedded systems have just one rootfs. I would start looking here https://www.yoctoproject.org/docs/3.0/mega-manual/mega-manual.html#creating-partitioned-images-using-wic https://www.yoctoproject.org/docs/3.0/mega-manual/mega-manua...

usr1106 7y ago

> 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.