I wouldn’t call all this hoop jumping to reading common log files “doing it better”.
This is exactly the kind of arcane tinkering that makes everything a tedious time wasting chore on linux.
At this point it’s accepted that text files get zipped and that should be handled transparently and not be precious about kilobits of logic storage as if we were still stuck on a 80386 with 4 megs of ram.
Here’s what we’re gonna do. We’re going to do the equivalent of x11 application network transparency but with wayland.
Kind of like streaming a desktop with sunshine, but on an app by app basis.
Also we’re gonna make a client that work for it on android, windows and in a browser.
Then I’m going to fuck you in the ass
Bad trigger discipline
Not improving existing software leads to stagnation.
It’s certainly a good part of why so much of linux is an awkward kludgy idiosyncratic mess to use.
Whatever the first implementation does ends up being a suicide pact by default.
Another option is to change cat to auto decompress compressed files, instead of printing gibberish.
Where is it? I can’t seen to find it https://github.com/zCat?tab=repositories
Even a corrupt compressed files has a very different structure relative to plain text. “file” already has the code to detect exactly which.
Still, failing on corrupted compression instead of failing on plaintext would be an improvement.
Just don’t sit then, ever again!
Got it, stop interacting with the world
I was already mostly doing this so
Thanks, didn’t know that existed
That’s basically everything I was looking for !
Thanks !
But still we shouldn’t have to resort to this !
Also, can’t get the output through pipe
for i in $(ls); do zcat $i || cat $i; done | grep mysearchterm
this appears to work
find . -type f -print0 | xargs -0 -I{} sh -c 'zcat "{}" 2>/dev/null || cat "{}"' | grep "mysearchterm"
Still, that was a speed bump that I guess everyone dealing with mass compressed log files has to figure out on the fly because zcat can’t read uncompressed files ! argg !!!
for i in $(ls); do zcat $i 2>/dev/null || cat $i; done | grep mysearchterm
Same but western digital, 13gb that failed and lost all my data 3 time and 3rd time was outside the warranty! I had paid 500$, the most expensive thing I had ever bought until tgat day.
The Switzerland approach isn’t going to work. It’s datacenters must be rendered inoperable and disconnected from the grid and its billionaires made to flee to their bunkers.
We can stop talking about after we’ve destroyed it
Explained by chatgpt
https://chatgpt.com/share/6760e8bc-24ec-8005-be3c-241aa6bf4aaf
Cumulatively pen and paper will add up to more effort. And I would person give up at some point. It would probably never enter my daily jabits. Realistically if on the scale everyday, the changes are so minute you won’t notice the monthly and longer duration trends.
It’s really surprising there isn’t a no bullshit option you could just buy
How do you automatically compile the daily readings into an excel file with graphs? Raspberry pi running opencv sending the time series to influx db and then grafana generate graphs for you home assistant health monitoring dashboard, along with the blood pressure monitor, continuous glucose monitor, pee ketone content, the pills dispenser and the rest of your fitness regimen?
Actually the question was, “which animalbcan I breed with?”. I think it’s important not to misrepresent the facts.
As for rogers, they didn’t have to pay Alliant because the court changed its mind after reading the french version of the contract. In the french version, it is clear the english contract means the plainly obvious interpretation, not the lawyery silent american comma bullshit!
The deal was a five year term, that auto renews for five years unless you cancel it a year in advance.
Alliant wanted to cancel the contract inside the first five year term, the gall of these lawyers!
https://www.bbc.com/worklife/article/20180723-the-commas-that-cost-companies-millions
Just create one account per comment. Lemmy can’t anything as it was designed for the convenience of moderators.
Wwit until lemmy falls and hope the successor makes moderation a crowd effort and a subscriotion service
Well in this particular case, zcat failing with error on uncompressed text isn’t a behaviour worth preserving.
It should do the expected zcat behaviour, which is just print the text.
I have a hard time imagining a scenario where you call zcat and would prefer an error rather than a useable output