On Mon, Oct 07, 2013 at 01:05:44PM -, Scott Moser wrote:
> Steve thinks its not entirely unreasonable to just disable plymouth via
> .override files in cloud-images. I think he would suggest that that be
> done at the package level and be handled by cloud-init. That wasn't
> clear to me thoug
** 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
So, some more information..
this bug is "fixed" by doing:
for x in /etc/init/plymouth*; do sudo mv $x $x.disabled; done
after doing so 100% of /dev/console output makes it to the console
(whoohoo!).
that lays this squarely on plymouth.
There is some conversation with slangasek, smoser and utlem
Upstart certainly changed, but none of the changes affect console
handling. Could the kernel change be the culprit maybe?
--
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:
ci-info: eth0 n
Heres a simple reproduce that shows the issue.
it seems racy condition like.
rel="saucy"
dimg="$rel-server-cloudimg-amd64-disk1.img"
dbase_url="http://cloud-images.ubuntu.com/$rel/current/";
mylogger_url="https://launchpadlibrarian.net/152522734/my-logger.conf";
## get files and prereqs
sudo apt
I just put this on upstart. I assume its probably really plymouth related.
but between alpha3 beta1, upstart changed to 1.10 from 1.09.
plymouth did not change.
Note, that even on saucy, with the my-logger.conf job in place, some
output is lost. (ie, you do not see all 'X=' values).
--
You re
I just booted a m1.small image on EC2 and 'euca-get-console-output' of
each of alpha1, beta1 and beta2 and the ci-info is present in all of
them.
** Summary changed:
- ci-info: eth0 missing from latest saucy images
+ ci-info: eth0 not reliable in latest saucy images
--
You received this bug no
