This PR adds split_lock_detect to the preserved_arguments list in anaconda.conf.
Currently, on recent kernels, if an x86 split lock is detected, it can cause the kernel to crash (#AC: crashing the ...
How long have you been around in the linux world? All of them were absolute dogshit when they came out and everyone complained (for Gnome, that means Gnome 3), but redhat kept pushing them anyway. For instance, when pulseaudio was new it caused crackles, noise, high cpu etc. everywhere, but they used their business connections to have vendors support pulseaudio exclusively, which meant you had to install it if you wanted to use Skype or for various games, even though ALSA was (and is) just fine. Nowadays it gets replaced by pipewire.
I guess I don’t need to explain the systemd drama; it has gotten much better, but what still sucks is that it drops you into a rescue mode when it can’t mount some filesystem that is not even necessary for boot (e.g. /mnt/data). And when you do not have a root password set up, but use sudo for everything, you are screwed because systemd demands the root password nevertheless, meaning you gonna need to boot from a live usb or similar just to fix one line in fstab. That is the stupidest shit imaginable.
How would business connections work? And it was only problematic on some systems, and only for a while
the audio situation before it was a total fucking disaster lol. The only real f up was no low latency really which pipewire now fixes apparently
And systemd consolidated and fixed everything too
Credit where credit is due. Writing a systemd script was so much easier than initd and it resolved so many race conditions and such
People just don’t like change. It’s the same when Wayland. People are pretending like x11 wasn’t problematic 😂
The distros didn’t choose this stuff because of business connections lol. And I’d love to see what red hat offered other distros to cause them to switch(I’m sure you have receipts)
Ubuntu even had upstart and even they dropped it eventually
I must be lucky. I had no issues with pulseaudio. In fact I thought it was so wonderful how you could hear multiple applications at the same time!
I thought gnome 3 was really cool as well. I didn’t use it as long as I did 2, but that’s because I found out about tiling window management (and later scrolling window management). But I liked the design of Gnome 3, not sure why. Felt modern, like a bold step in a modern direction. 😊
Systemd I just have no feelings about. I’m not well-read about the drama or how or why it’s a badly designed system. I don’t write my own units or whatever. I just start/enable and stop services. 😅
But these were just examples. Maybe you mean more stuff have been bad coming from Redhat.
Still it worked really well for me, and the experience I have is basically that a working system (pulse) was replaced by another (pipe). Must’ve been lucky.
Things like pulse audio also exposed a lot of driver bugs in audio hardware. In fact, in Windows, I discovered my awe64 was massively slowing down my system
I suspect some people are confusing the issues with windows 7 too though, where some people also had audio issues initially
Not really, it matches the Redhat software quality that we had a joy to experience for the last 10+ years (systemd, pulseaudio, Gnome, …)
GNOME is getting bad but in my experience systemd is just drama (and fine) and pulseaudio is still just fine
What would you say is low quality in those projects you listed there?
Also didn’t know Redhat developed those.
How long have you been around in the linux world? All of them were absolute dogshit when they came out and everyone complained (for Gnome, that means Gnome 3), but redhat kept pushing them anyway. For instance, when pulseaudio was new it caused crackles, noise, high cpu etc. everywhere, but they used their business connections to have vendors support pulseaudio exclusively, which meant you had to install it if you wanted to use Skype or for various games, even though ALSA was (and is) just fine. Nowadays it gets replaced by pipewire.
I guess I don’t need to explain the systemd drama; it has gotten much better, but what still sucks is that it drops you into a rescue mode when it can’t mount some filesystem that is not even necessary for boot (e.g. /mnt/data). And when you do not have a root password set up, but use
sudofor everything, you are screwed because systemd demands the root password nevertheless, meaning you gonna need to boot from a live usb or similar just to fix one line in fstab. That is the stupidest shit imaginable.How would business connections work? And it was only problematic on some systems, and only for a while
the audio situation before it was a total fucking disaster lol. The only real f up was no low latency really which pipewire now fixes apparently
And systemd consolidated and fixed everything too
Credit where credit is due. Writing a systemd script was so much easier than initd and it resolved so many race conditions and such
People just don’t like change. It’s the same when Wayland. People are pretending like x11 wasn’t problematic 😂
The distros didn’t choose this stuff because of business connections lol. And I’d love to see what red hat offered other distros to cause them to switch(I’m sure you have receipts)
Ubuntu even had upstart and even they dropped it eventually
I’m a user for about 20 years.
I must be lucky. I had no issues with pulseaudio. In fact I thought it was so wonderful how you could hear multiple applications at the same time!
I thought gnome 3 was really cool as well. I didn’t use it as long as I did 2, but that’s because I found out about tiling window management (and later scrolling window management). But I liked the design of Gnome 3, not sure why. Felt modern, like a bold step in a modern direction. 😊
Systemd I just have no feelings about. I’m not well-read about the drama or how or why it’s a badly designed system. I don’t write my own units or whatever. I just start/enable and stop services. 😅
But these were just examples. Maybe you mean more stuff have been bad coming from Redhat.
That was possible with ALSA and the “dmix” plugin years before pulseaudio came out.
Alright. Nothing I knew about at the time.
Still it worked really well for me, and the experience I have is basically that a working system (pulse) was replaced by another (pipe). Must’ve been lucky.
Yeah. I’ve been using Linux for at least 20 too
Things like pulse audio also exposed a lot of driver bugs in audio hardware. In fact, in Windows, I discovered my awe64 was massively slowing down my system
I suspect some people are confusing the issues with windows 7 too though, where some people also had audio issues initially
Ah, so they blamed pulse for driver and firmware bugs? I guess that happens easily.
Not all of when of course, but I seem to remember it was a factor. But it was so long ago now
Windows also had a lot of similar accusations at the time too