summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/rsync
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2015-09-18 13:49:22 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-09-23 09:52:59 +0100
commitd6e40e80d178e5b1e8e63d4c65439ec114eb5d0b (patch)
tree892e595e3f2bec81c0f2ba7758d57a67cde28526 /meta/recipes-devtools/rsync
parent288a9ffcf2b4b3d5e0c5d87f84b6378494191318 (diff)
downloadpoky-d6e40e80d178e5b1e8e63d4c65439ec114eb5d0b.tar.gz
initramfs-framework: better error reporting for invalid root boot parameter
When the "boot" parameter refers to a non-existent device, the only visible output at normal log levels was a rather confusing: ERROR: There's no '/dev' on rootfs. That's because the actual error, not being able to find the root device, was only a debug message, which gets ignored in the default mode. Promoting the "root '$bootparam_root' doesn't exist." message from "debug" to "msg" gives sufficient context to understand the error. A more intrusive change would be to change also the control flow. (From OE-Core rev: 71d7803e5b13e26fd8001e87cfbac68114ddaa30) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/rsync')
0 files changed, 0 insertions, 0 deletions