Comment 3 for bug 606373

Revision history for this message
Scott Moser (smoser) wrote :

On a whim, I modified /usr/share/initramfs-tools/init to not redirect output on exec of root's /sbin/init. Ie:

| # Chain to real filesystem
| echo "==== running init but not redirecting ===="
| #exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console >${rootmnt}/dev/console 2>&1
| exec run-init ${rootmnt} ${init} "$@"

My intent was to leave stderr, stdout going to the same places they were when the ramdisk loaded, as *its* messages go to the console. However, the result is the same as without the change. In the console I see:

| Begin: Running /scripts/init-bottom ... done.^M
| ==== running init but not redirecting ====^M
| ^[%G2010-07-16 18:05:56,155 - cloud-init-run-module[ERROR]: user-scripts already ran once-per-instance
| user-scripts already ran once-per-instance

There should be 'cloud-init' output in after the 'running init' but before the cluod-init-run-module output.