Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs
Op 17 okt. 2013, om 11:02 heeft Nicolas Dechesne <nicolas.deche...@linaro.org> het volgende geschreven: > On Thu, Oct 17, 2013 at 10:20 AM, Koen Kooi <koen.k...@linaro.org> wrote: >>> right now, auto-serial-console does 3 things: >>> >>> 1- figure out the serial console port from /proc/cmdline >>> 2- start a console on #1 >>> 3- automatically login as root >>> >>> I believe that we should 'do something' to split them into several >>> packages so that we get more granularity. At least #3 needs to be >>> separated out, as #3 is a 'policy'. >> >> The recipe itself is already a policy thing, so we should look into a way to >> have different images for proper builds (using BSPs) and hwpack based >> deployments. This will also make non-linaro users of our layers happy. > > well, i am a non happy, linaro user ;-) > >> >>> I would almost expect that 'being able to automatically login as root >>> on the console' is a feature that could (should?) be added to oe-core >>> somehow. What do you think koen? >> >> I agree >> >>> I looked into that, but there isn't >>> any obvious (and trivial) way to do that, but it's certainly doable >>> inside an IMAGE_FEATURE for example. >> >> Right. But keep in mind that sysv is not the only init system supported in >> oe-core. FWIW, systemd already autospawns a getty on every entry listed in >> the console= kernel cmdline. > > ok. so why then do we have this: > > http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd-serialgetty.bb > > it's 'just in case' the kernel does not have console=xxx but > SERIAL_CONSOLE is defined? what's the use case? It's as you say, to spawn a serial console regardless of console= parameters. It's analogous to having a getty in inittab. > if systemd-getty-generator finds a console=xxx and if SERIAL_CONSOLE > is defined, i assume we don't get 2 getty, but one. is > systemd-getty-generator taking care of such situations? So far it seems to work, so I guess the clash of 2 rules trying to run a getty on the same port is somehow resolved internally in systemd. Since it "just works" for me I haven't looked into it :) regards, Koen _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
