Hi @davidlekve,
Thanks for getting in touch! There’s a couple of questions in here, let me try to address them one by one:
- logging in, with empty root password.
By default, the root login on a Yocto image is disabled, in the reasoning of “secure by default”. The easiest way to get the empty password login is addingEXTRA_IMAGE_FEATURES += "debug-tweaks"to yourlocal.confor image recipe. For more details, please see 11 Features — The Yocto Project ® 5.0.999 documentation. Why is this not in the defaultkasfile? Same reason, we don’t want to encourage insecure defaults. - setting the root password.
The link which you posted seems to be quite outdated. I’d suggest to follow the documentation at 5 Classes — The Yocto Project ® 5.0.999 documentation my-raspberrypi5/build/conf/local.confversusmy-raspberrypi5/poky/.... There is no reason to ever modify anything insidepoky. Treat it as the upstream source it is - how would you manage and control any eventual changes upon checkout? My guess is that you have mixed up different Yocto tutorials here, one of them suggesting to tooe-init-build-envinsidepoky. That is definitely bad practice. If you want to have the shell initialized for building without callingkas shell, but using the setup whichkasprepared, then to correctly use themy-raspberrypi5/builddirectory, do
cd my-raspberrypi5
source poky/oe-init-build-env
- Building on Ubuntu 24.04 is a so-called “untested path” for the
scarthgaprelease of Yocto as Ubuntu 24.04 just was not around when the release was constructed. I’m at least not aware of any immediate problems, and it’s a common situation. It just tells you that there is no fully official, auto builder scale quality assurance on it.
Hope this helps,
Josef