You’re not doing it right. There’s absolutely a reason why enterprise linux works with a version that’s more-or-less locked in place (but for security updates, like a maintenance fork). You need to understand the value you’ve been overlooking.
ten years of a stable platform. Because, yeah, it’s not this week’s release with the glitter, but it’s also not a moving target of broken suck you have to constantly chase, and you can actually do dev.
dependencies are figured out
updates are trivial when security stuff comes out. Honestly – yum+cron is so stable and reliable, and the compatibility is part of the guarantee; so you - and your customers - don’t have to worry or - please god no - delay updates to gauge risk. Since updates are 99% of the work to avoid exploits, this goes from ‘huge risk’ to ‘no-brainer’. And you don’t have to worry that your dev environment is non-trivial to replicate on the daily.
your requirements for your software becomes ‘EL7’; maybe ‘EL7+EPEL7’ or so. Your installation process becomes ‘add repo RPM which pulls in other repo RPMs. yum install’ , and you’re already onto mere config work.
validating the install isn’t ‘did you install this ream of apps from this particular week in time, then run some wget|sh bullshit? Now run this other set of commands to confirm your installation’ – but in our case is just ‘rpm -qa|egrep’ or even an snmpwalk.
not working? Give me your one config file and your rpm-qa and we’ll replicate here trivially and find out why. (I didn’t work in support, but I liaised with them a bunch in the security work, and that was common practice) Tossing 4 lines and a <<EOF construct into a vagrant config is just so easy, now, and gives the entire machine to play with.
As someone who used to dev a notable app in the past, cross-distro problems alone made so many of the fringe OSes impossible to support, and so we didn’t. EL was the backbone because we respected what we had.
I just can’t figure out why this-week’s-glitter is more important than losing the install/support/update/validate burden by choosing a stable platform to work within. Life’s too short to support dependency hell or struggle just to replicate a failing setup in your lab for testing. Do you just not support customers?
Wayland gaming is great, especially on KDE, you can go into display settings/compositor and switch from smoother animation to lower latency for a latency that’s even lower than X11, without any of the X11 issues.
While I disagree with Red Hat’s decision to hinder source access, this move from Rocky (a commercial company!) seems even more disingenuous, imho.
Why on earth is it disingenuous? RedHat is openly stating its intent to violate the GPL. Rocky is telling them “good luck with that.” RedHat wants to be the only game in town providing service contracts. Rocky is saying “no thanks; we’re sticking around.”
You can use about any laptop with Linux. I would say take a current laptop and boot into a distro using a live usb. This will let you try it without installing it. You do occasionally run into issues with some hardware: fingerprint, wifi, trackpad, etc. So this is a good test.
But otherwise if you want a laptop that guarantees Linux support: Framework, System76, Tuxedo
Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
No it’s almost always been derived from people’s behinds.
Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
Yes.
Systemd is spectacular in many ways. Every modern OS has a process management system that can handle dependencies, schedule, manage restarts via policy and a lot more. Systemd is pretty sophisticated on that front. I’ve been able to get it to manage countless services in many environments with great success and few lines of code.
I’ve read this can depend a lot on the bluetooth card. Personally after replacing my cheapo dongle from like 2012 that probably just didn’t do a recent enough BT version I didn’t have any issues connecting to them.
What card do you have? Might be useful for anyone else who has the same issue.
Got no issues with AirPods Pro and arch. Installed blueman and it’s dependencies and it connected just fine. Managed to configure pipewire to automatically switch between a2dp sink and hsp depending on the current usage.
I haven’t had any problem on Garuda with my AirPods. I saw another guy say he had no problems with manjaro and arch. I didn’t know people were having problems on other distros or setups.
They’re a pretty big contributor to Linux, so even if you don’t see their work you’re probably using it anyway. lwn.net/Articles/915435/
added value that cannot be fulfilled by independent experts or FOSS community
Wrong question IMO. It’s more relevant to ask “without Red Hat, would independent experts or the FOSS community have added the same value?”. Sure, it’s possible that Red Hat has some highly skilled developers that possess unique skills required for their contributions, but in general contributing to FOSS projects is more about willingness to spend large amounts of time and resources on something that doesn’t give you money in return.
Lots of large companies “could” have spent thousands of hours contributing to Linux, but unless they actually do it then it is irrelevant.
I do not think systemd is bad, I (and personal preference here) much prefer it over the older style of init systems.
Quite frankly, one of the things that has always irked me about a portion of the Linux community is that as far as I know, a strength and selling point of Linux has always been the freedom of choice. And yet, people start wars over your choices. For example, I know at least on r/Linux if you were to make a post saying that you liked Snaps over Flatpaks you’d get torn to shreds over it. Wouldn’t matter what reasons you had either.
It is always something. Whether its about Arch vs other distros, Snaps vs Flatpak vs AppImage vs Traditional packaging, X11 vs Wayland, systemd vs Sys V/init.d, pulseaudio vs pipewire, etc.
I never understood why it mattered so much what someone ran on their own computer. Assuming they’re the only one using it, what is the big deal if they choose to run OpenRC, X11, Snaps, and Alsa?
And I get a bad feeling the next one is going to be immutable distros vs non-immutable distros, but I guess we’ll see.
It’s a massive question, and I think quite a lot of the argument comes from the fact that it depends what direction you’re answering it from.
As a user, do I like being able to just systemctl enable --now whatever.service , and have a nice overview of ‘how’s my computer’ in systemctl status ? Yes, that’s a big step up from symlinking run levels and other nonsense, much easier.
As an administrator, do I like having services, mounts and timers all managed in one way? Yes, that is very nice - can do more with less, and have to spend less time hunting for where things are configured. Do I think that the configuration files for these are a fucking mess of ‘just keep adding new features in’ and the override system is lunacy? Also yes.
As a developer trying to do post-mortem debugging, who just wants all the logs in front of him for some server that’s gone wrong somehow, which I often have to request via an insane daisy-chain of emails and ‘Salesforce nonsense that our tech support use’ from our often fairly non-technical end users, on some server that I’ve no other access to? No, I do not find having logs spread between /var/log and journalctl (and various CloudFormation logs in a web console) makes my life easier. I would be pleased if that got sorted out.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.