Pfft, of course not! These weren’t Clinton sponsored suicides! ;)

That explains a lot of what I’ve been experiencing for quite some time now. Laptop’s internal keyboard types fine in grub, but usb keyboards the password is wrong more often than not.

Sure. It was from a dumb play on words I came up with a really long time ago. It was something that amused me greatly, but literally no one else ever found it funny. “I’m Pseudo Spock, a.k.a not the real McCoy.” Either no one understands my genius, or I’m to stupid to see how stupid I am. Probably the latter.

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

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

348. You are missing two assassinated whistle blowers.

Same, hence my extreme disbelief.

Obviously a fictitious one.

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.

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

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

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

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.

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.

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.

More like over baked but still only half done.

Wayland is set of protocols.

Oh my god! It’s like hearing the same on hold greeting again and again. WE KNOW!

Oh you had me going in the first half. Sly devil you. Wayland still doesn’t work on the fleet of equipment we have.

no…nonono… AHHHHH! - Vegita DBZA

That’s what somethin’ somethin’ said lastnight, Trebek! ;)