** Description changed: + During early boot, plymouth captures writes to /dev/console. As I + understand it, it is supposed to re-play that content later. Whether or + not it intends to is not the issue. In our cloud-images (and in other + cases) users may write data to /dev/console that needs to be seen on the + other side (ie a serial logger or 'get-console-ouptput' api call). + + See the attached 'my-logger.conf' for an upstart job that simply writes + data early in boot to /dev/console. Sometimes data "lost" is available + in /var/log/boot.log, but sometimes it doesn't even seem to make it + there. + + Related bugs: + * bug 682831: lost console output early in boot + + == Original bug report == On precise cloud images, I get a console output line like this: ci-info: eth0 : 1 192.168.122.204 255.255.255.0 52:54:00:7f:d8:ca^M On saucy cloud images, this is missing.
** Summary changed: - ci-info: eth0 not reliable in latest saucy images + plymouth loses output to /dev/console (such as ci-info: messages) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
