DefederateLemmyMl @ SpaceCadet @feddit.nl

* Gen𝕏

---

Read more

Posts

1

Comments

585

Joined

2 yr. ago

Typical rookie mistake :D

I also agree sed and some regex is your best bet

Nah, regexes are okay if you really have no other choice, but they're a bit of a hamfisted tool. For a json file, which is a neatly structured format, I would always try to do it with jq first.

I really did like the feel of alma. Rocky I thought felt like every other GNOME system

Unless you used different versions of each, shouldn't they feel exactly the same?

Depends on your symptoms.

• Paracetamol for a general feeling of malaise
• Ibuprofen for fever and muscle and joint aches
• A decongestant like pseudoephedrine if your nose is clogged up, but not the "alternative" phenylephrine that's often pushed now in over the counter decongestants. It just doesn't work. A xylometazoline spray works too, but I try to avoid it because it can easily lead to rebound congestion.

I don't want to change back, but I still thought it added a sense of adventure, and having to be actively involved with the navigation gave you more awareness of where you were and where you were going. Now you just slavishly follow instructions and then some hours later you are there.

Like, we drove to Austria last summer and when we came back my dad asked me: so did you drive over Stuttgart or Nuremberg? And I honestly didn't know.

stty -ixon to disable ctrl+s/ctrl+q flow control shortcuts that randomly freeze my terminal when I accidentally activate them

bind Space:magic-space this expands special bash variables like !!or !$ to their actual value when you press space.

FWIW I use an elastic stack for that: filebeat, journalbeat to collect logs. Logstash to sort and parse them. Elasticsearch to store them. Not sure if it satisfies your FOSS requirement, as I don't believe it's entirely open source.

I guess it depends on how you define "breakage". The system being completely b0rked and unsalvageable? No, that has never happened.

Bugs, regressions or other gotchas or annoyances that needed to be dealt with? Yeah, several since I started using Arch in 2014.

• netctl hanging on boot (it was some systemd config issue)
• Very slow throughput issue with the Intel AX wifi driver (needed to rollback kernel and firmware until upstream fixed it)
• Intel NIC disconnecting under high load (was eventually fixed in a firmware update)
• Graphical artifacts in chrome and firefox after certain mesa updates (amdgpu related, eventually fixed)
• Black screen in google maps after a mesa update (amdgpu related, eventually fixed)
• Mesa update breaking high refresh rates in vkQuake (mysteriously fixed after several months)
• Grub introduced an incompatible update last year, so had to boot from USB and re-run grub-install
• An issue with vim syntax highlighting being broken for bash scripts. Was caused by upstream, and quickly fixed.
• A new readline version introducing bracketed paste by default. I'm not counting this as regression or bug, but it's an instability because a default behavior suddenly changed
• mpv's pipewire audio output was broken a few weeks ago leading to muted videos. It was an upstream bug that was fixed a couple of days later.
• mpv's default subtitle handling behavior was changed around the same time as well, had to add subs-with-matching-audio=yes to the config to revert to previous behavior
• Currently still struggling with an issue with virtiofsd: my VMs can't re-mount virtiofsd filesystems when they are rebooted.

And there were probably several more which I can't remember.

Mind you, I'm not blaming Arch for this. It's just what you can expect from a rolling release distribution, and if you are not able or willing to occasionally diagnose/fix things like this, Arch is not for you.

Yeah but I think you're unfairly blaming Arch for not being ready for a new GPU on release day, especially when there are still known issues with the upstream packages that are required for it.

I think you may also misunderstand what Arch is. It isn't meant to be absolute bleeding edge. It's meant to be a distro that's as up-to-date as possible yet stable enough for everyday use. So the Arch team does curate upgrades and does QA before they release it to the stable repos.

And "Good Times" by Edie Brickell, but for some reason nobody ever remembers that lol

LLVM was held back for a good reason, it was breaking things left and right. Even so, if you really needed it there were always AUR packages for it, or lcarlier's mesa-git repo if you prefer prebuilt packages, so it's not as if you were just SOL. I got my 7900XT in december, and instructions on how to get it running were already all over the forums and subreddit at the time and it was working on the same day that I got it.

I don't know when you got your 7900XT, but it was broken on Ubuntu too for a good while, I'm not even sure that it currently works on 22.04 without using external PPAs. In the mean time, it now works with Arch out of the box.

As for the grub thing, I'm not sure how that could have been handled differently. Upstream introduced a change that created a compatibility issue, so Arch could either not update to a newer version of grub ever, or update anyway and tell its users how to handle the compatibility issue. The latter is what they did.

Good on you, I was a long time slackware user myself. I just wanted to make the point that just using any Linux doesn't suffice to escape these shennanigans, the choice of distro matters as well.

It wasn’t because Corporate decided to use their OS to force their app store or cloud services onto people.

Ubuntu and the snap store say hi!

CentOS is dead.

It's almost 9 years ago, I think we're good.