I don’t believe it will work. To do so it requires to maintain their own repository of RPM specs for a stable release distro. In this case Alma will became an active independent distro downstream to Fedora and CentOS Stream, and could steal the focus from RHEL. I don’t think RH will allow that. Not to say I requires significant effort and Alma is a small community funded project. It’s to good to be true and I have skepticism about the positive attitude of the blog post.
I guess RH tries to “embrace” Alma and Rocky as it was with CentOS.
I don't think this will be viable for the people who really are looking for direct RHEL compatibility, but lots of people like me just use the basic structure of RHEL because we're familiar with the config locations and tooling, and we like the stability over time. If Alma can replicate that aspect then it's still good for me even if they're not bug for bug compatible. Rocky still seem to be going for 100% compatibility and I think that will be harder to maintain over time if RedHat actively fight it.
Go with XFCE, it is perfect to start from. You will get a feeling for linux in a fairly intuitive environment. Then you can easily move on to other stuff if you want to. You can install multiple DEs/WMs and choose which one you want from the log in screen. You can install as many as you have disk space for.
One thing to know about the concept of "customization" in linux. It is on a whole other level than you may be thinking of. On linux when people say something is customizable, especially when you start reading phrases like "infinitely customizable" what it might means is that you must configure it to even open it. And to do that you will first have to spend a bunch of time learning about the application's conventions, history, weirdsies, development environment, etc. You may also have to understand and be able to manipulate the underlying system architecture.
It's fun to do once you reach the basic required skills, if you are interested in that kind of thing. but you can only learn so many things at a time, so set yourself up for success by starting easy. You can move on to a more complex situation at any time you are ready for it. Like imagine learning to drive in a place you've never been with totally different traffic laws than you are used to, and also it's on the moon so gravity don't work as expected. Better learn to drive in an empty parking lot close to where you live.
First thing is make sure linux will run at all on your computer. You can install it, boot it, shut it down, connect to the internet, play audio, make a backup, un/install applications, and other simple tasks. Just go path of least resistance. Don't try to find the perfect set up. Just try something out.
SSD ASAP
Make a separate /home/ partition when you install --- this will keep your actual files (documents, user configurations) safe(r) from screw-ups
Find a way to make regular backups of your user and system configuration files, keeping past versions in case you screw something up but don't realize it right away
I very recently (like last week!) stuck a new drive in my PC to run Pop!_OS, with the aim of switching over from Windows entirely if it pans out. So far I've only tested Steam for games, but it's worked flawlessly for the games I've tried using Proton.
I've had a Steam Deck for some time which convinced me to make the jump. My desktop was my only Windows machine and I'd love to properly switch it to Linux.
AppImage is a lot better than Flatpak because it isn't a walking security nightmare (http://flatkill.org).
But yeah, I got a build working with the PR. I'm not on my computer right now, but it's a pinned PR in the GitHub issues for the WebCord project. You go to the fork with the branch, you run a couple of quick npm commands and then you can do a build.
I did have to remove a few of the package makers because they'd set it up to do a .deb build, and I haven't used apt in years. I vaguely think they had a Flatpak or a Snapcraft package maker in there too, but I don't use those.
You run the make and package commands which you can find in the package.json file, then it outputs a built application for you.
One thing that annoys me about discord is the screenshare popout, ideally I’d like to pop each screen out individual instead of only being able to popout the entire block. For example I’d like to keep webcams on my left monitor and have someone’s shared screen in full screen on the right. I get round this by having two accounts but would be good to have a native solution
The Devs had also upgraded a lot of Electron stuff and security problems that the official Discord client doesn't do, as well as fix a lot of bugs and issues that Discord haven't bothered with.
Oh, and if you're using KDE Plasma, it uses the Qt file picker and not the GTK one.
I installed Garuda on my main desktop PC and have been absolutely loving it. I'm not a linux expert, this is the first time I've dived in with my main pc on linux only (but I have been "trying" linux every so often for as long as I can remember basically). It is amazing how far Linux has come in just the last few years. It is very close to what I would consider a full replacement mainstream OS. I am on a fully AMD system though, so I can't speak for nvidia issues (but honestly I've been sick of them even under windows for a few years now...).
Honestly, I wouldn't make any specific recommendation. Because when you do, you instantly become most peoples personal support technician, when they can't sort something out.
I'd probably make the general suggestions of Fedora/Silverblue/Kinoite, openSUSE Tumbleweed/Aeon/Kalpa, and maybe Pop!_OS if somebody put a gun to my head. But no recommendations.
It is doable to install an OS onto a flash drive or external drive, but from my experience it was really slow. Just need to make sure to then boot the machine to the USB device. Some machines you might find it difficult to change that in the BIOS.
Linux
Top