KubeRoot

I got the impression that the PolyMC situation was quite different, with that developer masking it and doing a minority of the work, but after one change made by the rest of the developers they snapped, used their control over the repository to remove the rest of the maintainers and take sole control over the repository.

I was aware of some shenanigans and hostility from PolyMC and never used it, but I got the impression there were no major outward signs before that happened?

I’m not sure if this is what you mean, but I do want to clarify - the drivers in the repository are still proprietary drivers from Nvidia, just tested and packaged by the distribution maintainers, dkms is just some magic that lets them work with arbitrary kernels with minimal compilation. Unless you’re using nouveau, which I don’t think is ready for most uses.

I’d definitely recommend against using drivers downloaded from a website, on general principles.

custom kernels don’t work with the drivers from apt

Check if there’s a dkms version - I know that’s the way it’s set up on Arch, if using a non-standard kernel you install the kernel headers, and dkms lets you build just the module for your kernel.

…Brave is just chromium by techbros, right?

Archlinux is good if you accept that you’ll need to spend time to learn it, and that those moments might be frequent and unavoidable early on. Definitely wouldn’t recommend it to somebody who needs their computer to work, since a new user with no experience might find themselves breaking their boot images and spending hours trying to figure out how to fix their computer not booting.

So yeah, I think that’s an important caveat: if you don’t know Linux already, and you can’t afford to spend time learning and fixing your system, don’t use Arch.

One could argue that “based” covers this kind of inspiration 😉

On the bottom of the page you have a tree representation of replies, with clickable links to each message. The layout might not work well on mobile with limited screen width though, but you can just click through them.

I don’t think arch does much to make commandline easier to use it understand - instead I’d say it aims to teach you how to use it, because it might be easier than you realize, but importantly it tries to tell you why. Instead of just giving you the command to run, the wiki explains various details of software, and the manual installation process tells you which components you need without forcing a specific choice. As a result, hopefully after using arch you’ll know how your system works, how to tweak it, and how to fix issues - not necessarily by knowing how to fix each individual issue, but by understanding what parts of your system are responsible and where to look.

Since your issue is specifically wanting GUI, I’d recommend installing something like pufferpanel or pterodactyl/pelican, which give you a browser interface for running game servers. Pterodactyl/pelican is more popular, has more features and supports more games, while pufferpanel is simpler/lighter and easier to make your own templates for.

Pretty sure what you’re describing isn’t floating-point numbers, but fixed-point numbers… Which would also work just as well or better in most cases where floats are used.

echo ‘🎁’ | tee /dev/🏠

Anticheat is good. Intrusive anticheat, in this case kernel-level anticheat, is something that’s being made only for windows that will stop you from playing a game on Linux and increase attack surface for your Windows.

I’d say having a GUI is not inherently stupid. The stupid part is, if I understand it correctly, the GUI being a required component and the primary access method.

The wiki tells you what you need on arch, and what you need it for. Those packages also don’t seem to have kernel-specific or dkms versions, so seems like they’re not kernel modules.

Mind you, the setup is clearly not monolithic, with different components for different purposes, including alternative options. On top of that, each distro will make different choices - Arch provides the components as packages and puts the responsibility of installing the right ones on you. Some features might be built into kernel drivers, like working video output, but Vulkan support clearly wants a dedicated driver.

Here’s what you need for Arch, for more context: https://wiki.archlinux.org/title/AMDGPU

I think on mutable distros, or at least arch, you can run a command to reinstall all installed packages, which will verify integrity of the package files (signatures) and then ensure the files in the filesystem match package files? And I think it takes minutes at most, at least for typical setups.

I do think it’s also possible to just verify integrity of all files installed from a package, but I don’t remember if it required an external utility, pretty sure it’s on the arch wiki under pacman/tips and tricks

I also recommend rEFInd for the bootloader if you don’t want to set anything up (and risk messing up). You don’t need to configure your boot entries, it scans for boot options and shows them with a graphical interface, so your Linux and Windows should just show up.

The issue is, when doing sudo, you have to put in the password when doing sudo. In this case, you put in your password, some flag is set, the computer does a full reset, and then after it reads the flag and decides to bypass the password system. That sounds like just a step away of figuring out how to set this flag without a password to bypass logging in.

I think an issue is, this sets up your computer to have a way to bypass putting your password in on boot. If you don’t care about security too much and don’t have things like secure boot and encryption, then that’s bypassable anyways… But otherwise, I’d be concerned about introducing systems that specifically bypass security.

Why does every distro need yet another package manager?

I think most package managers - the ones actually part of a distro - are old. It’s not a question of why they all use different package managers, it’s a matter of them having developed them long ago before any single one matured.

That said, there are other considerations, which is also where new ones come from - different distros will have different approaches to package formats, dependency management, tracking of installed packages and system files, some might be implemented in a specific language due to the distro’s ideology, some might work in a different way (like NixOS), and there’s probably a whole bunch that just want a different interface.

You wouldn’t ask why Linux has a different way of viewing installed programs from Windows, and in the same vein packages are not a universal aspect of Linux, so each distro has to make its own choices.

Also I like pacman, some people complain about the commands being obscure, but I feel like they’re structured in a much more logical way. Don’t confuse it with yay though, pacman doesn’t build packages, and yay is specifically a wrapper around pacman that has different commands, while adding the ability to interact with the AUR.