Re: Bug#727708: Fsck SystemD and its developers and its users. GR to override this please.

[Gergely Nagy <algernon@balabit.hu>]

The Wanderer <wanderer@fastmail.fm> writes:

> Also because when writing a parser, it's easier to determine the format
> (in terms of meaning and start/stop of each field) of a text file than
> it is of a binary one, when working without known-reliable
> documentation. (And I'm not willing to assume that I'll always have such
> documentation.)

Stop right there. You're so very wrong there, you cannot even imagine.
Without documentation, you cannot assume *anything* about neither text
nor binary. If you think you do, think again, you will be wrong.

> There's a *reason* the vast majority of kernel userspace-interface files
> are in plain-text form, after all.

Interface? Yes. You give textual commands to journalctl, and it gives
you text output back. Same way you echo something into files under /sys,
or cat them, and something behind it *translates* that. The only
difference is that journalctl is a user-space program, while the files
under /sys are translated by the kernel.

-- 
|8]