systemd recap++ (part 3 of 3) did what?

[Ed]

Want to know what's going on with your systems? now you get more than
dmesg and /var/log/mess...  ok I have no news about this, but if you
are new to systemd then this changed too.  The most apparent change is
that the display of log data was broken out from its simple collection
and "jounalctl" is how you work with it. Things you may notice: output
is paged, errors are highlighted (red), long lines are
trucated(ellipsis), and you get everything from the beginning of time.
Oh, and there are different formats, like JSON. Go ahead try it:

journalctl

and you start from the beginning, and thus the kernel begat the system
and lo, the first boot did happen...  (don't panic)

journalctl -r

same stuff, just from the other end of time. As expected, -f does a
follow and to see the truncated bits use -l. If you want jounalctl to
meld together multiple (not necessarily local) journals, you want to
look into the -m option.

I like to see the current boot with any extra notes from the dev
people, so I use:

journalctl -xb (it's like dmesg, but with Haiku)

and for the nostalgic, dmesg is emulated with:

journalctl -k  (the -b is inferred)

The most interesting, and something I'm looking forward to, is being
able to have logs in JSON format. For that use the -o option:

journalctl -o json-pretty

Just the thing for playing with jq (http://stedolan.github.io/jq/)
You should be good to go with basic systemd - start stuff, start stuff
the way you want and see for yourself what it did - what more could an
Admin want? no really, rtfm or more like rtfblogs  8)

thx to Hans for asking for a recap, hope it helps - Ed