Hello I’m Doctor_Rex I’m the OP of this post:
My Windows 10 install broke, but I’m hesitant to switch to Linux.
I’d like to start by thanking everybody who responded to my questions. Your answers have helped a lot when it came to my worries on switching to Linux.
I’ve taken in a lot of your recommendations: Fedora, Fedora Kinoite, Nobara, Bazzite Linux, VanillaOS,
I’ve decided on Fedora Kinoite, as it has everything I want from a distro.
It was very kind of you all to answer my questions but after making that post and reading your answers new questions propped up.
These questions are a little more opinionated than the last ones, and a little better thought out, but please take some time to answer them.
Questions:
- Is Wayland worth using? Especially when you consider all the issues that may come from using an NVIDIA card.
Are there any real noticeable advantages/improvements to using Wayland over Xorg.
- Does bloat actually matter or is it just a meme?
Does bloat actually have a noticeable negative impact on your system or are people just over reacting/joking.
- What are some habits I should practice in order to keep my system organized and manageable?
Any habits or standards that I should abide by in order to save myself headaches in the future?
- Any other resources besides the Arch Wiki that I should be aware of?
Self explanatory.
- What do you wish you knew when you first started using Linux that would have saved you a headache in the future?
I’m not referring to some skill but instead something pertaining to Linux itself. Feel free to skip this question.
I’ll be going to sleep soon, so apologies if I don’t reply but please take a moment answer any questions you think you can.
Thank You!
Edit: AUR = Arch Wiki. Fixed a typo
For a first dive into the Linux ecosystem, I recommend Xorg. I use Wayland myself (Hyprland), and that’s why I know that it’s simply not ready for general adoption. There are many features that are missing, won’t be implemented, or are done much differently compared to X. Some say Xorg is old and bloated - I say it’s a mature technology.
There are also some applications that need root privileges to work (Veyon Configurator is one that I struggled a lot with) and you have to do some weird
pkexec
hackery to launch them.Wayland’s development has more drama and bickering than an average sitcom - I recommend Brodie Robertson’s channel if you’re interested.
Wayland is better for gaming. It has a noticeably lower latency because the entire Wayland stack is implemented in a single program (what they call the compositor) as opposed to several in the X11 stack (X server, compositor, window manager) that need to communicate with each other. Unfortunately Steam and some other applications often produce graphical artifacts on Wayland+Nvidia.
Compared to Windows, it is insignificant. My work laptop is a Macbook Air from 2015 running Linux Mint on just 4G RAM without issues.
Install the
tldr
program. It’s a bit likeman
but lists practical examples of a command instead of a full documentation.Make use of your home directory. Most user applications will have a config file in several places - usually in
~/.config
(user config) and/etc
(systemwide config). You should only edit the systemwide config when it makes sense, and always prioritize the user config.A common practice is to have your
/home
directory on a different partition, or a different physical device. If the system breaks or you decide to distrohop, you can unmount/disconnect/home
and only wipe the root partition while retaining your user files.I also recommend using
Timeshift
to back up your system. It’s even better if your root partition uses btrfs since it natively supports snapshots.I needed to leave the Windows ways behind me. On Windows, I had a hard drive mounted as F: and an external HDD mounted as H:. Moving to Linux (Manjaro at the time) was basically a snap decision since Windows had obliterated the boot partition during an update and then broke itself, and I
had no idea how to properly set up the filesystemdidn’t consider how I wanted to set up the filesystem, so I mounted them to/mnt/f
and/mnt/h
on a whim. It caused me many hours of headache later.Can you elaborate? What kind of headaches? How would you set it up now? While I’ve been using Linux quite a while I don’t have multiple hard drives and am always interested in best practices.
I should correct myself - it wasn’t a bad way to mount my drives, but it was a very Windowsy solution that I came to regret anyways.
I used that HDD as basically my home directory on Windows. It had all of my projects on it (mainly C# and Blender). When I installed Manjaro on my 240G SSD, I decided to leave my
/home
directory on the root partition, but it soon filled up. I later wanted to move it to the HDD, which meant that the mount point had changed, which meant that I had to relink all external files in my projects to the new mount point.I could’ve just used a symlink that pointed
/home
to/mnt/f
, but/mnt
is generally used for manually mounted filesystems, and I wanted to at least have that and/home
done properly.Right now I have a 2T NVMe SSD, one 200G partition mounted as root, the rest mounted as
/data/games
(and it really only has Windows games and my Steam library), a separate 1T SSD mounted as/home
, and a 3T HDD on/data/hdd
that contains my backups, disk images, and large media files, each symlinked to appropriate places.Don’t know if you saw this but you can mount devices multiple times in Linux. And you can mount directories in different locations as well (bind mounts). These can also be helpful in moving around where things are mounted since both the old and new paths will work. But symlinks are probably simpler.