Me too, mostly, but popping into a forum to ask questions is a thing. I stopped using bspwm largely because the one responsive person in the Matrix channel was a first-class self-righteous turd; that alone wouldn’t have been so bae, but none of the admins called them on it, and, well, herbstluftwm turned out to be better software anyway. The hlwm community has avoided being toxic mainly by not existing, AFAICT.
Hyprland is one of the ones I tried, and it may be closest to what I’m looking for. I’ve heard the community is extremely toxic, though. Software projects having “conmunities” is a relatively recent thing, for me, so it’s not a big deal, but what’s been your experience?
That’s good to know. TBH most of what I was talking about was my experiences at ranges and gun shops in Eastern PA, a little N of Philadelphia. A few years ago I moved to a large city in the mid-West and haven’t had a chance to visit many ranges; and the ones close to me are indoor – I’d have to travel a bit to get rural enough to find an outdoor range. So I honestly don’t know how things have changed in the past 5 years, and things tend to be more liberal it large metro areas anyway.
It’s encouraging to hear that tha NRA is losing support. I still feel that Trump is considered safer for 2A than Biden; if he’s (Trump) not actively defending 2A, he’s at least not talking about strengthening gun laws. And that hasn’t changed: 2A is still a single-issue voting decider. Relatively few of us gun owners are not passionate about gun ownership, where it’s a hobby, not a lifestyle.
It could be Linux, too. Some distros have fancy boot graphics - look for something called “plasma” - not the KDE one, but a different one - and uninstall or disable that. It’s a common thing that hides the boot log behind a logo-and-progress bar. Arch doesn’t use it, so I haven’t seen it in years, but IIRC it can cause problems on headless systems.
Oh, that plasma. Yeah, that naming conflict is totally not confusing.
You could switch all your repos to the core Arch ones. I did that by accident once, and it was fine (although, I did switch them back eventually). Maybe it’d add release stability? I’m not really clear how the EOS repos vary off the baseline, except by adding some custom packages.
Inspired by our discussion, I installed snapper on two boxen. I included snap-pac and snapper-support to get system change and grub integration; there’s probably also a utility out there that adds visudo-like snapshot-before-manual-edit of anything in /etc. If not, it’d be an easy script. snapper-gui and btrfs-assistant both look useful. While I’m comfortable with rescue SDs and restic backups, what I’m seeing with Arch’s snapper package is pretty nice, and super easy.
I suppose anything that borks grub is going to be a PITA no matter how immutable your OS, or how fancy your rollback. Or - god forbid - fucks up your BIOS firmware. I have never had that last happen, yet (knock on wood).
Ah. K, I think the differrence is that I’m the outlier. Your system has far larger components, with more moving parts, which I think is more common:
On most of my systems, I’m not running any graphical system; they’re all servers. That eliminates a huge amount of stack that can fail. On all but non-servers I run X, which is very stable (in that upgrades almost never impact it) on non-Nvidia GPUs. And of those, all but one run herbstluftwm - Gnome and KDE are both large systems with a lot of moving parts, any of which can break (or be broken) – in your case, it was Plasma, a KDE component. And the last desktop is running Budgie which, while still Gnome, is a lighter one based on the older GTK3. All of these things tend to make for more stable systems.
But, most people are probably running fancier, full desktop software. Larger, more complex, more development, more frequent changes. And, consequently, more prone to cascading packaging breakages, like the Plasma one.
I think if I were using software like that, I’d consider either giving up Arch and using an immutable distro, or using something like snapper or timeshift that allows boot-time system roll-backs.
Are you updating with eos-update, or yay? TBH, I only use yay, or pacman. I don’t imagine it makes any difference, but… IDK. I happened to upgrade and reboot two EOS machine yesterday, with again no issues. Are you running an NVidia card? I’m an Radeon guy, won’t touch NVidia, myself. How about Wayland? I’ve alwayw found Wayland to be super flakey, which keeps me on X.
I dunno. I wonder why you’re having so many issues, while for me EOS has just been Arch with an easier install.
That sounds stressfull! It’d put me off a distro, too. I had something similar happen in the early days of Gentoo - multiple times. Those trials by fire did teach me a lot, and I’m now consequently far more sanguine about the boot process, and thank god these days we have smart phones as mini-backup computers to search for solutions! Still, we’re in a time when PCs are not as indispensible, and having one down for a couple days can be a minor disaster.
Rolling updates or no, I rarely -Syu on my desktop more than once a week, and most of my machines get that TLC more like monthly. And sometimes I’ll hold out packages that require rebooting, because FTN. It probably contributes to the fact I’ve avoided these types of dramas --statistically.
Hmmm. You may be right. I have owned no Makitas. I’m going by tear-down videos. AvE may have gone a bit off the rails, but he’s done some really good tear-downs of different tools, and looked at the quality of the materials, the casting, the motors, switches, and so on. He consistently was impressed by Makita’s build quality… but all of those videos are, like, 6 years old, or older.
It’d be too bad if even the “good” makers like Makita went the quantity-over-quality commercial route.