#bitbake — Public Fediverse posts

Создаём простейший киоск при помощи Yocto

Я уже рассказывал, как можно собрать минимальный Linux под различные архитектуры. Также я описывал свой эмулятор известной игры «Ну, Погоди!». В этой статье я хочу рассказать, как создать дистрибутив Linux с моим эмулятором, который будет работать в режиме киоска. Вы сталкивались с операционными системами, работающими в режиме киоска, когда снимали деньги в банкомате, взвешивали продукты в супермаркете или покупали товар на кассе самообслуживания.

https://habr.com/ru/companies/ruvds/articles/1072714/

#linux #yocto #openembedded #kiosk #ну_погоди #recipes #layers #bitbake #ruvds_статьи #дистрибутив

@moreentropy I'm actually fine with processes running as root in an unprivileged Podman container because the root user inside the container is mapped to the user running Podman on the host which is sufficiently secure for my use cases. Some applications (looking at you, #Bitbake), however, refuse to run as UID 0. And that's the point where it gets funny. Not.

It's been sometime since I last messed with #bitbake (a long time ago in an embedded job far far away). While system build systems do do useful things its often very hard to find out what's going on deep down in their guts. So frustrating when trying to replicate and debug a #qemu bug.

@ross since I have your attention has anyone looked at sccache integration for #bitbake? Looks like it should be pretty straight forward leveraging the ccache and icecream plumbing that already exists.

> this would be my version of a logo for #BitBake

Brought to you by "but why is my shared #Yocto cache corrupted when two machines build off of it at the same time" debugging sessions while #Bitbake actually uses locks (flocks :) ). This eventually got "resolved" by mounting a local NFSv4 and making the servers all use the cache over NFSv4 instead of one over ext4 (on the server the disk is physically connected to).