I also see the llist of post-kernel messages, which do come from sysvinit scripts:
* Setting preliminary keymap...
* Preparing restricted drivers...
* Starting early crypto disks...
* Starting remaining crypto disks...
* Starting AppArmor profiles
* Setting up console font and keymap...
* Starting init crypto disks...
* sda5_crypt (running)...
This looks like a bug in either lsb-base (which provides the common log functions these scripts are all calling), or in upstart (for not setting up the expected environment for these scripts). I'll have a look.
I also see the llist of post-kernel messages, which do come from sysvinit scripts:
* Setting preliminary keymap...
* Preparing restricted drivers...
* Starting early crypto disks...
* Starting remaining crypto disks...
* Starting AppArmor profiles
* Setting up console font and keymap...
* Starting init crypto disks...
* sda5_crypt (running)...
This looks like a bug in either lsb-base (which provides the common log functions these scripts are all calling), or in upstart (for not setting up the expected environment for these scripts). I'll have a look.