Merge lp:~pali/ubuntu/oneiric/initramfs-tools/initramfs-tools into lp:ubuntu/oneiric/initramfs-tools
Status: | Work in progress |
---|---|
Proposed branch: | lp:~pali/ubuntu/oneiric/initramfs-tools/initramfs-tools |
Merge into: | lp:ubuntu/oneiric/initramfs-tools |
Diff against target: |
164 lines (+76/-6) (has conflicts) 3 files modified
debian/changelog (+12/-0) init (+12/-0) scripts/functions (+52/-6) Text conflict in debian/changelog Text conflict in init Text conflict in scripts/functions |
To merge this branch: | bzr merge lp:~pali/ubuntu/oneiric/initramfs-tools/initramfs-tools |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pitt | Needs Fixing | ||
Review via email: mp+64373@code.launchpad.net |
Description of the change
Write boot log messages to plymouth.
This patch add support for writing boot mesages like "Running /scripts/local-top" on plymouth screen (like old usplash).
This patch/merge depends on these plymouth merges:
https:/
https:/
When plymouth is running, it write boot log messages to console too - without drm/framebuffer splash renderer. Then plymouth use detail text output to console. So this is reason why _log_msg is not called when plymouth is running (it would be in console 2 times).
Unmerged revisions
- 241. By Pali
-
Fixed writing messages to plymouth
- 240. By Pali
-
Write boot log messages to plymouth
- 239. By Scott James Remnant (Canonical)
-
Create /run in the initramfs, move to the real filesystem before
exec'ing init so that it survices. /dev/.initramfs is a symlink to
/run/initramfs, and the old /dev/.initramfs/varrun path just points to
/run (via two symlinks).
This is blocked on landing https:/ /code.launchpad .net/~pali/ ubuntu/ natty/plymouth/ plymouth/ +merge/ 61897 upstream first, and then needs an update to the current package. I'm setting this to "work in progress", please set back to "needs review" once above happened. Thanks!