[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f4e72e6-ad1e-4626-a9de-c67f569526ca@riseup.net>
Date: Wed, 15 Jan 2020 18:09:33 +0000
From: Patrick Schleizer <adrelanos@...eup.net>
To: lkrg-users@...ts.openwall.com
Subject: Re: LKRG complains about battery being automatically
unload
> Btw. Do you think that these messages are ambiguous?
Yes. These are less than ideal. Here's my view. If nobody else agrees
with me on some or all point(s), if I am the only one seeing it that
way, it's probably best to keep as is. I'd suggest to discuss any output
messages with the most (reasonable) laymen person you can have a chat
with. Here are some suggestions. During my 7 years of development of and
user support for Whonix, I've written, revised quite some output
messages. My suggestions may not be perfect, I am not an UX designer,
but perhaps an iteration of improvement.
Generally, I would suggest to use all uppercase sparingly.
> ALERT !!! FOUND LESS[1] MODULES IN DB IN MODULE LIST[54] THAN IN
CURRENT MODULE LIST[55]
Since that is to be expected as you explained, that does not sound like
that deserves all upper case. Also not the the word "alert".
"in db": superfluous, not useful for user.
INFO: There were 55 module(s) resident. There is now 1 module(s) less
resident. There are now 44 module(s) resident. Module(s) 'battery',
'jitterentropy_rng', '...' was unload.
Or maybe:
INFO: Modules list: Was: 55 Change: -1. New: 54. Changes: 'battery',
'jitterentropy_rng', '...'
Or maybe:
INFO: Modules list: Was: 55 Change: -1. New: 54. Load: 'battery',
'jitterentropy_rng', '...' Unload: 'fuse', 'soundcore', '...'
Or maybe:
INFO: modules amount: Was: 55 Change: +1 New: 54.
INFO: modules load: 'battery', 'jitterentropy_rng', '...'
INFO: modules unload: 'fuse', 'soundcore', '...'
(These ones could even be parsed with scripts if that was useful for
anyone.)
> EXTRA MODULE: name[battery] module at addr[00000000aae59f0b] module
core[00000000d5bd1fc8] with size[0x2000] hash[0xcc42714bdd4f6be7]
unload module(s): name 'battery', addr '00000000aae59f0b', module_core
'00000000d5bd1fc8', size '0x2000', hash '0xcc42714bdd4f6be7'
That should probably not be the spadeful output level. Only at the next
higher debug level.
> EXTRA MODULE IS THE SAME AS ON-GOING MODULE ACTIVITY EVENTS
That one I don't understand. MODULE ACTIVITY EVENTS?
> !! MOST LIKELY SYSTEM IS STABLE !!
No upper case. No "!!". If previous output was just "INFO:", then there
is no need to mention that either.
INFO: There were 54 modules resident. There is now 1 module more
resident. There are now 55 modules resident. Module(s) 'battery',
'jitterentropy_rng', '...' was load.
Kind regards,
Patrick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
