While I agree that sometimes Uber projects happen, for efficiency or security reasons, I don’t think that Mesa is a good example as they have a scope (implement the OpenGL/Vulkan API) and stick to it.
Systemd is already confusing because of it referencing two different projects, and the overarching systemd projects scope just increases on a regular basis without what appears to external observers as a plan.
Is journald still binary? That alone made me turn away.
Yes, unreadable with a text editor. Meaning that if you have a computer problem and journald or systemd is broken you have can’t consult the log files, unless you did install rsyslog or sometimes before that. Meanwhile by default journald will eat a few GBs of disk space soon.
Storage efficiency, faster queries, more metadata, unified format, etc. If your host breaks, you can download the journals and open then elsewhere. Also, there is nothing stopping you from configuring it to output to a file.
“on nooo i’m gonna stop using what make modern linux OS good just because they save logs in binary, istead of binary w ith .txt 😭😭” go ahead them, make your life worse
“on nooo i’m gonna stop using what make modern linux OS good just because they save logs in binary, istead of binary w ith .txt 😭😭” go ahead them, make your life worse
😒
One can keep on using systemd and complain about journald and install rsyslogd and then you’d have the journalctl -f command to impress your Linux noob friends ;-) and /var/log/syslog when there’s trouble when journald would be dead.
if you can’t access journald you have a bigger problem than crying about it’s binary file format, but ok keep needing to parse every fucking log using grep and taking 30 second to find anything meaningful if you hate yourself that much
While I agree that sometimes Uber projects happen, for efficiency or security reasons, I don’t think that Mesa is a good example as they have a scope (implement the OpenGL/Vulkan API) and stick to it.
Systemd is already confusing because of it referencing two different projects, and the overarching systemd projects scope just increases on a regular basis without what appears to external observers as a plan.
Is journald still binary? That alone made me turn away. I am using PCLinuxOS hence am systemd free. Stopped reading up on it.
Yes, unreadable with a text editor. Meaning that if you have a computer problem and journald or systemd is broken you have can’t consult the log files, unless you did install rsyslog or sometimes before that. Meanwhile by default journald will eat a few GBs of disk space soon.
Compared to this what is the advantage of binary form? I thought log files being text was a no brainer.
Storage efficiency, faster queries, more metadata, unified format, etc. If your host breaks, you can download the journals and open then elsewhere. Also, there is nothing stopping you from configuring it to output to a file.
Open them elsewhere is also true for text files I guess.
“on nooo i’m gonna stop using what make modern linux OS good just because they save logs in binary, istead of binary w ith .txt 😭😭” go ahead them, make your life worse
😒
One can keep on using systemd and complain about journald and install rsyslogd and then you’d have the
journalctl -fcommand to impress your Linux noob friends ;-) and /var/log/syslog when there’s trouble when journald would be dead.if you can’t access journald you have a bigger problem than crying about it’s binary file format, but ok keep needing to parse every fucking log using grep and taking 30 second to find anything meaningful if you hate yourself that much
systemd is a group of projects, they can create as much projects inside the name systemd tho