**** BEGIN LOGGING AT Sun Apr 17 02:59:58 2016 Apr 17 12:57:17 thanks to josep, I know that I can (probably) set up a getty to be started on any console I choose. Problem is: I tried setting SERIAL_CONSOLES in my specific-custom-image.bb, and that changed nothing Apr 17 12:57:58 my suspicion is that this is due to the SERIAL_CONSOLES variable being in the machine scope. Apr 17 12:58:01 Is that lead correct? Apr 17 12:58:28 and if so, how do I set that? Apr 17 14:24:00 funkylab_: setting SERIAL_CONSOLES in the image recipe won't have an effect, the variable won't propagate to other recipes Apr 17 14:24:57 josep: workaround for that this far was putting it in local.conf Apr 17 14:24:59 funkylab_: you can set it in your local.conf, for instance Apr 17 14:25:04 :) Apr 17 14:25:05 yes Apr 17 14:25:53 Hm, but that way I can't go out and say "see, here's my soandso image.bb, which starts a console on ttyUSB0, and there's the other image, which doesn't" Apr 17 14:26:54 is there a way I can do that in a .conf that's specific to one recipe/package/image build? Apr 17 14:28:56 mmm, I don't think you can do that in an image recipe Apr 17 14:31:53 funkylab_: you can add a post process command to the image that adds the console to etc/inittab or appropriate systemd file... but that's ugly Apr 17 14:33:52 josep: agreeing on the ugliness aspect :) Apr 17 14:34:07 josep: considered copy/pastaing my machine-xyz.conf Apr 17 14:34:38 but then I'd have two machines to build for, just because I have one image with an additional serial console, which isn't exactly time-saving **** ENDING LOGGING AT Mon Apr 18 02:59:58 2016