From: Karel Zak Date: Tue, 29 Mar 2011 22:27:29 +0000 (+0200) Subject: docs: update TODO X-Git-Tag: v2.20-rc1~417 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1bc386e51343909c012e69d43b9c7799ed41d6a4;p=thirdparty%2Futil-linux.git docs: update TODO Signed-off-by: Karel Zak --- diff --git a/TODO b/TODO index a01a31a883..c903ab067b 100644 --- a/TODO +++ b/TODO @@ -2,11 +2,25 @@ dmesg ----- - - add new command line option --facility= or --loglevel= to print select - loglevel only. For example - - $ dmesg --logleve=6 - $ dmesg --loglevel=INFO + - add new command line option --facility= and --level= to print select + messages only. For example + + $ dmesg --level=ERR --facility=DAEMON + + IRC log: + + kzak: the point of --facility= is so that we can distuingish between kernel msgs and userspace msgs written to /dev/kmsg + the latter would set facility=1 (i.e. LOG_USER) or facility=3 (i.e. LOG_DAEMON) + kzak: right now, everything written to kmsg just uses on-char PRIO fields + kzak: i.e. <0> to <7> + kzak: that means facility for all of these is 0 + since facility according to the syslog spec is stored in the the bits of the value between "<" and ">" shifted right be 3 + and since that is zero for all msgs in kmsg this is identical to LOG_KERN, i.e. 0 << 3 + now, the idea is that we fix systemd, dracut and udev to use LOG_DAEMON or LOG_USER instead + instead of using <4> as prefix they'd use <12> or so + where 12 is 4 + 8 + where 8 is 1 << 3 + and 1 is LOG_USER mount -----