[systemd-devel] systemd console messages (crippled)
Nikolai Zhubr
n-a-zhubr at yandex.ru
Tue Jan 6 03:51:50 PST 2015
Hi people,
I'm now fighting with opensuse 13.2 failing to mount some or all disks
at boot, obviously resulting in unusable system. This distribution is
systemd-based, hence I'm here. While I haven't yet exactly understood my
disks problem, one other thing is absolutely clear: systemd messages as
displayed on text-mode console are crippled and there is no option to
decripple them. This is my favourite (real-life example):
[FAILED] Failed to start File System Check on
/dev/disk/by-uu...5-eaedc37c1852.
See "systemctl status 'systemd-fsck at dev-disk-by\x2duuid-729...ce'" for
details.
[DEPEND] Dependency failed for /sysroot.
Now what's the point of crippling them so hard? And what's the use of
such hints ("See systemctl status...) if actual uuid value got truncated
away? Ok, I had to use a pen and a piece of paper to write down this
uuid first, after that I could actually try to make some use of
systemd's hint.
I just fail to understand who this truncating is good for. Those who
like pretty-pretty boot screen would have graphical logo with colorfull
animations, so they'd never see systemd's boot output and wouldn't care.
Those who prefer more usefull diagnostic info over screen prettiness
could probably tolerate line-wraps. Or do line-wraps explode LCD
monitors these days?
Ok, sorry, could some kind soul maybe just apply the diff below?
Thanks in advance,
Nikolai
------------------ cut -------------------------
--- src/core/manager.c.orig 2015-01-06 04:16:06.740811061 +0300
+++ src/core/manager.c 2015-01-06 04:16:19.154811459 +0300
@@ -2810,7 +2810,7 @@
return;
va_start(ap, format);
- status_vprintf(status, true, ephemeral, format, ap);
+ status_vprintf(status, false, ephemeral, format, ap);
va_end(ap);
}
------------------ cut --------------------------
More information about the systemd-devel
mailing list