Godot maintains a fairly comprehensive documentation that can even be fully downloaded.

Wouldn’t this still be the superior solution? The article doesn’t mention the setup for using ROCm for cards running on amdgpu.

As I found out recently myself, you should almost always set the minimum amount of reserved memory for the iGPU on modern hardware. The reserved memory is just that— reserved. The kernel still dynamically allocates memory for GPU usage as needed on iGPUs.

https://librewolf.net/

A summary from its site and known technical details:

• no telemetry by default
• includes uBlock Origin
• has sane privacy-respecting defaults
• prepackages arkenfox user.js
• relatively well-maintained fork of Firefox that keeps up with upstream
• No major controversies AFAIK

As for Windows 7, nobody should really need to install Librewolf anyway on such a device. No device running Windows 7 should have access to the internet at this point. If you are asking about compatibility intending this use case, you have bigger problems to worry about than your choice of browser. If you just need to view HTML files graphically, even Internet Explorer or an older firefox ESR will do.

Assuming you are installing your Steam library on your ext4 partition rather than ntfs one for your Windows install, BeamNG will likely be the easier game to diagnose for your game crashes on launch. The log file to find for BeamNG is located by default in steamapps/compatdata/284160/pfx/drive_c/users/steamuser/AppData/Local/BeamNG.drive/0.32/ as beamng.log. By default in a standard Steam install, your steam library is located at ~/.steam/root/. I am unsure if Bazzite installs Steam as a Flatpak. If it does, the default Steam library should be at ~/.var/app/com.valvesoftware.Steam/data/Steam/. If you chose a custom location for your Steam library, it will be wherever you chose it to be.

How are these games (Lethal Company, BeamNG) installed? If they came from a Windows install on NTFS, just reinstall them on a proper filesystem and then you will be able to play them through proton. Roblox just doesn’t work so it’s not worth testing.

Add SKSE manually, add it as an executable option in MO2.

What makes Nextcloud unreliable for your use case? I’ve used the calendar (caldav) functionality for years without issue in sync.

Tbf to cloud sync, nothing is stopping you from using your own backup/restore service with your drm-free titles compared to the other features that Galaxy offers.

GOG has DRM for many titles: see Galaxy. As I understand it, it isn’t as pervasive as Steam, but is necessary if you want multiplayer on many titles or care about extras like achievements.

Use the OCI through podman or docker.

The heated bed is coupled to a thermistor. I’d argue controlling the temperature in order to not accidentally overheat parts of the phone is a step above a hair dryer.

What compositor (desktop environment) and distro are you running for things to behave that poorly?

Based on how the script /usr/lib/kernel/install.d/99-grub-mkconfig.install (a script that runs on kernel installations) behaves, unless you are running in Xen Hypervisor or are on an architecture that doesn’t support it, Fedora by default expects to have GRUB_ENABLE_BLSCFG set to true. This script is provided by the package grub2-common, so it’s unlikely it can be removed without removing the GRUB bootloader’s management system entirely.

More than likely, most customizations will work just fine with GRUB_ENABLE_BLSCFG set to true as long as you properly run grub-mkconfig (or just update-grub) after you make those changes so that they get applied to the bootloader portion of GRUB itself.

If for some reason you do absolutely need to disable BLS in order to get the customization you want, the proper way to enforce grub-mkconfig on new kernels would be to write a script in the /usr/lib/kernel/install.d/ directory titled like 98-grub-manual-mkconfig.install that would forcibly run the proper mkconfig command after kernel installation and initramfs generation.

This seems like a terrible bandage fix rather than letting the system mechanisms do what they are supposed to.

Checking inside /usr/lib/kernel/install.d/, you can see the mechanisms in place for installing new kernel entries. Not knowing what you did to your config (did you back it up before making changes?), you should check if the entries are being populated properly in /boot/loader/entries/. If they are, you have likely toyed with the BLS config in some way that broke being able to load dynamic entries without mkconfig.

If that is indeed the case, I wouldn’t know exactly what you touched to break it, but this discussion forum might give some insight.

If this isn’t the problem, it might be helpful to post your grub config minus any sensitive details to help determine what is going wrong.

Windows does have memory compression, though you can’t really change the algorithm or how aggressive it is. AFAIK it is just a toggle of on or off.

Beyond the article being ancient at this point (in terms of AOSP and Android development lifetime), Stallman’s argument boils down to the same talking points of Free Software purism.

To the first real point being transformed here: Android is not GNU/Linux because it does not contain much of the GNU Project’s software. While it’s correct to claim it’s not GNU/Linux, how does it not make it Linux still? Is Alpine Linux not considered “Linux” because it doesn’t contain GNU? Please elaborate on this point of Linux being Linux because it has GNU.

To the second point of including proprietary drivers, firmware, and appplications: we once again meet the questionable argument of transforming an OS to something else. Points are made that Android doesn’t fit the GNU ideals due to its usage and inclusion of proprietary kernel modules, firmware, and userland applications. These are valid points to be made in that these additions muddy the aspect of Android (as packaged by Google and major smartphone manufacturers) being truly free software. However the same can be said about traditional “GNU/Linux distributions”. Any device running on x86 (Intel, AMD) will be subject to needing proprietary firmware in order to function with that firmware having a higher control level than the kernel itself, just as Android would. There is also the note that while it is less necessary now to have a functioning desktop, a good portion of hardware (NVidia, Broadcom, Intel, etc.) require proprietary kernel modules and/or userland drivers in order to have full functionality that the average user may want. Finally, there is proprietary applications as well. Some Linux desktops include proprietary applications like Spotify, Steam, Google Chrome by default. Are we really to also exclude an overwhelming majority of the biggest Linux distros as Linux as well being that they include proprietary software or rely on proprietary code in some fashion? GNU itself lists very few distros as GNU-approved.

To note, AOSP does have a different userland environment than your standard Linux distro running X11 or Wayland. That is by far the best reason I could think of to classify Android as a different category of ‘Linux’ from say Debian, Fedora, OpenSUSE, Arch, Gentoo, Slackware, and others. However, AOSP is still capable of running with no proprietary userland software and can even be made to still run cli applications as well as run an X11 server that is capable of launching familiar desktop Linux applications. I really think that the arbitrary exclusion of Android from being Linux by virtue that RMS doesn’t think it fits with GNU ideals is silly. If there are better arguments to be said for why Android (especially AOSP) shouldn’t be seen as Linux with a different userland ecosystem rather than not Linux entirely, I’d love to see them. However, I remain unconvinced so far.

I have been utilizing BunkerWeb for some of my selfhost sites since it was bunkerized-nginx. It is indeed powerful and flexible, allowing multi-site proxying, hosting while allowing semi-flexible per-site security tweaks (some security options are forcibly global still, a limitation).

I use it on podman myself, and while it is generally great for having OWasp CRS, general traffic filtering targets and more built on top of nginx in a Docker container, the way Bunkerweb needs to be run hasn’t really remained stable between versions. Throughout several version upgrades, there have been be severe breaking changes that will require reading the setup documentation again to get the new version functional.

A few things Fedora centers itself around:

• Wayland-oriented Workstations
• SELinux support OOTB
• BTRFS as default filesystem
• General attitude toward using close to bleeding edge packages as defaults
• Package order of Fedora rpm repos, Fedora Flatpak -> RPMFusion, Flathub -> copr -> external installation
• Immutable variants of Fedora exist for the major desktops

Fedora generally prides itself on being a Wayland-focused and oriented workstation distro. There is still active support for desktop environments/window managers that run on Xorg, but you should consider moving toward a Wayland-supporting environment (Gnome, KDE, Sway, Hyprland).

SELinux (a Mandatory Access Control system) is enabled by default and has pretuned policies installed that should support most use cases out of the box. SEApplet is a useful utility to find active SELinux denials in case an application is getting permission denied issues for seemingly no reason.

If you intend to use BTRFS as your filesystem of choice and want to utilize it to its fullest (encrypted partitions, subvolume encryption, automatic snapshots), it is best to read up how BTRFS and subvolumes work before partitioning so that your subvolumes will be correct the first time. It can be tedious to edit subvolumes, move their contents, and remount portions of the filesystem after they have already been populated.

I’m sure you’re used to how things on Arch with bleeding edge works, and understand that on Arch you should always read patch notes before updating. Generally, updates on Fedora are fine to just push through. It is worth generally reading what is new when performing system upgrades to a new version of Fedora, I have noticed occasionally in over five years of usage the first target release of a new version of Fedora can sometimes have breakages that tend to get fixed within the next couple of weeks. There is extensive testing for system upgrades that can be openly viewed, but the testing doesn’t always catch everything before a new release.

By default, the best way to grab packages on Fedora is from the official repos or from the Fedora Flatpaks. Barring that or if you aren’t satisfied by a default package for whatever reason (some stuff in default repos doesn’t have ffmpeg support or others due to codec licensing issues), you can add the second-party RPMFusion repos or add Flathub to grab additional or alternative packages as well. If those avenues fail, you might be able to find someone maintaining the package you need or want to test on Copr, which is essentially like Ubuntu’s Launchpad PPA platform. Barring all else, you could manually install a given application externally, though obviously this typically isn’t the best solution in most cases. Some cases where you might want RPMFusion packages are for things like audacity-freeworld, which includes proper ffmpeg support for Audacity. This package comes from rpmfusion-free. Or you might want something like akmod-nvidia to install the proprietary NVidia drivers or steam to install Steam. These packages come from rpmfusion-nonfree. Also, if you are not familiar with Flatpak, it might be worth becoming familiar with how it works (Flatseal is an excellent application that lets you modify how certain Flatpaks are sandboxed).

Immutable variants of Fedora (Silverblue, Kinoite, Sway Atomic, Budgie Atomic) also exist and provide an immutable base image that won’t typically get modified across boots. Most of the custom user installation of programs is intended to be installed via Flatpaks (Fedora or Flathub) or through using toolboxes to create sandboxed environments for certain workflows. If you absolutely need to rebase the system image with extra utilities, rpm-ostree is available to modify the system package selection, though this method is not recommended to just be used to install everything (needless rebasing of the immutable image defeats the point of using an immutable distro). Obviously these spins aren’t for everyone, but are there for those who want to use them.