PseudoSpock

joined 1 year ago
[–] PseudoSpock@lemmy.dbzer0.com 1 points 6 months ago

I get it. Sometimes thinking of a handle is all mental block. Thank you for responding.

[–] PseudoSpock@lemmy.dbzer0.com 8 points 6 months ago (4 children)

Explain your username, please. I have a hard time with someone using that handle making posts in here.

[–] PseudoSpock@lemmy.dbzer0.com 4 points 6 months ago

Same, hence my extreme disbelief.

[–] PseudoSpock@lemmy.dbzer0.com 5 points 6 months ago (5 children)

Obviously a fictitious one.

[–] PseudoSpock@lemmy.dbzer0.com 1 points 6 months ago

Text is compatible with all the grep, awk, sed, text editors, what have you. As for the argument of it binary saving space, not on modern filesystems with compression, like zfs, btrfs, and bcachefs. The entire resistance against tampering is bogus, any systems where that is a concern already live scrape logs to an off server indexing service. If you are concerned about poorly formatted logs, that is an application configuration issue. Address it directly with the application. There are no benefits to a binary log, especially when journalctl is absolutely no faster at jumping to the end of the long log than standard less is. Poettering has you chasing phantoms. He always does. He's like the politician who justifies horrible bills by saying it's to protect the children.

[–] PseudoSpock@lemmy.dbzer0.com 2 points 6 months ago (2 children)

Standard updates on RHEL can sometimes break yum / dnf due to updating python.

[–] PseudoSpock@lemmy.dbzer0.com 1 points 6 months ago (2 children)

The issue is logs are suppose to be text. Seriously, wtf. You some Poettering fan boy or something?

[–] PseudoSpock@lemmy.dbzer0.com 1 points 6 months ago

Having the logs twice is saving space, got it. Do you hear yourself?

[–] PseudoSpock@lemmy.dbzer0.com 1 points 6 months ago (4 children)

Yes, and many distros have that out of the box... But they don't have it sent to keep the binary journal as close to empty as possible. So you end up with twice the space in use for logs. As for the issue with binary logs, text logs can be read by far more tools and utilities, rather than just journalctl and pipes.

[–] PseudoSpock@lemmy.dbzer0.com 3 points 6 months ago (8 children)

By itself, solely doing init, it would have been fine, however, binary logging (even if you eventually end up with a text log, that's wasting disk space on a binary format no one wants or needs), and it didn't stop there. He keeps replacing Linux subsystem after subsystem, and many of those replacements are not progress, just duplication of effort and creates more ways for configuration drift.

[–] PseudoSpock@lemmy.dbzer0.com 2 points 6 months ago (1 children)

It is ridiculous. Nothing like says f you to a large percentage of your user base like pushing out a solution that doesn't work for them.

view more: ‹ prev next ›