• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle


  • This is false. X is not less secure than Wayland. It does have a different security model, which can become insecure if you misuse it. I don’t think people really care about situations where multiple user accounts access the same display.

    In my opinion, the benefits of xdotool far outweigh any benefits gained by Wayland’s security model. It’s impossible to make xdotool in Wayland, because of its security model.



  • I never got Proton working on my main distro (Debian), so I probably fall into this category. I did use Wine, but Wine is a lot harder to set up, and never ran games as well as Proton did.

    Here is my major gaming history, since I started on Linux in 2007. Yes, I really could focus on a single game for years back then.

    • 2007: Starcraft, in Wine
    • 2007: Nethack, native
    • 2011: Morrowind and Oblivion in Wine
    • 2012: Minecraft, native
    • 2014: sgt-puzzles, native
    • 2016: Steam, got hundreds of native Linux games.
    • 2017: Briefly got Steam and Path of Exile working inside a Wine instance.
    • 2022: Steam deck, with the specific purpose of being able to run Proton on it.
    • 2023: New Ubuntu installation, and Proton finally worked on my PC.

    Today, I still prefer native Linux games. I mostly only use Proton when peer pressure for a multiplayer game required it. But I never use Wine any more.



  • A couple months ago, I made a Palworld server box out of a spare motherboard assembly (mobo, processor, ram) from a computer I had recently upgraded.

    I didn’t have any spare drives lying around, so I plugged in 7 USB flash drives and made them into a RAID array. Not a true RAID array, but a BTRFS filesystem with volumes spread onto each flash drive, with the data redundancy set to raid1, and the metadata redundancy set to raid1c3.

    It worked… in the sense that I never lost any data. It certainly didn’t work in the sense of having good uptime.

    The first problem was getting it to boot right. The boot line in GRUB had “root=UUID=…” instead of a specific drive named. That is normal. However, in BTRFS multi-volume filesystems, all the volumes have the same UUID. So the initrd was only waiting for a single drive matching that UUID, then trying to mount it as the root filesystem. This failed, because the kernel had not yet set up the other 6 USB drives, and this BTRFS filesystem needs all 7 volumes present. Maybe 6, if you used the “degraded” mount option.

    The workaround was to wait for this boot process to fail, at which point you get dropped into an initrd shell. Then, you look at all the drives and make sure they’re all there. And then… I don’t exactly remember what happened next. I think it was some black magic that erases your mind in the process. I somehow got it booted from the initrd shell.

    Installing Steam and the Palworld server worked ok, and it even ran for a few hours before crashing overnight.

    The next morning, I tried rebooting it. Unfortunately, the USB drives weren’t all appearing. Turns out the motherboard had some bad USB ports, some sometimes-bad USB ports, and a maybe-bad PCIe bus, because the PCIe USB expansion card I plugged in had weird problem that it had never had before.

    I found the most reliable ports and plugged the drives in there. But you can’t just replug them in the initrd. It doesn’t have USB hotplug support. So each time it tried to boot with not all the drives there, I restarted it again until one time I finally had all the drives.

    I changed the GRUB boot line to “root=/dev/sdg1” . This made it wait for all the drives to load, in any order, and whichever one was last would be mounted as the root filesystem (but the kernel would automatically include all the others too, since they were successfully initialized).

    The bad USB ports kept bringing down the server every day or two. I bought a cheap NVMe drive and added it to the BTRFS filesystem, and then removed all the USB drives except the largest. That fixed the reliability. It’s been like that since.

    Now, to boot the server, all I have to do is change the GRUB boot line to “root=/dev/sdb1” . Since the NVMe drive is much faster than the USB drive, it always initializes first. If the initrd waits for sdb2, then it will always have both drives initialized when it tries to mount the root filesystem.

    I could add that to the grub.cfg, or come up with some other more permanent solution, but I’m not planning on rebooting this server ever again. My friends fell off Palworld, and I gave a shutdown date that’s about a week away. And the electricity is pretty reliable here.


  • The good news is: the error shown there was a PCIe bus error, which means the error is somewhere between the NVME controller and your processor’s PCIe interface. Also good news: the errors you experienced were fully corrected, so you probably lost no data.

    So the flash memory in the drive isn’t failing. That’s good because if the flash memory starts failing, it’s probably only going to fail more. In this case, your errors may be correctable: by replacing the motherboard, by replacing the processor, by reseating the NVME drive in its slot, by verifying that your power supply is reliable…

    However, if your NVME controller actually does fail, it will be little consolation to tell you that your data is all still there on the flash chips, but with no way to get it. So now might be a good time to make a backup. Any time is a good time to make a backup, but now is an especially good time.

    If you keep getting these errors at the same rate, then you probably don’t need to do anything, since the errors are being corrected. If you’re worried, you could use BTRFS and enable checksumming of data.


  • You know that stuff that appears on the screen before the operating system? That is the computer’s firmware. Sometimes it shows a brief memory check, sometimes it has a silly error message like “No keyboard detected. Press F1 to continue.” Sometimes it’s just a big image of the motherboard’s manufacturer’s logo. That firmware exists independently of the operating system, and will run even if you don’t have any operating system installed.

    Most people refer to the firmware as the “BIOS”, but technically, BIOS refers to an API between the firmware and the operating system. About a decade ago, some people decided that “BIOS” was going to be replaced by “UEFI”, and operating systems would start having a new way to boot. What ended up happening is: the firmware on all recent computers supports both UEFI and BIOS interfaces (and everyone still calls it “BIOS”). Recent Windows versions seem to only boot in UEFI mode, but most Linux distros can boot in either UEFI or BIOS mode. The GRUB bootloader can also start itself up in either UEFI or BIOS mode.

    USB live operating systems are limited in size and may have less functionality than other operating systems, so maybe they are only able to boot in one method or another. Try looking around in the firmware (or “BIOS” if you prefer) to see if you can change the boot method to allow both UEFI and BIOS operating systems.

    It may help if you can take a picture of some of the firmware’s boot configuration menus.



  • It’s Apple, which is a dealbreaker for me. Everything Apple is proprietary. All the OS, all the apps, everything is locked down. Last I used it, you can’t even compile your own software for Apple platforms without paying a massive fee.

    I will wait to buy the open source AR goggles, even if it makes me 10 years late to the bandwagon.


  • Cloudflare seems to incorrectly classify my Internet connection, which is a residential Internet connection going to my house, as a datacenter connection or VPN or something.

    Many websites that use Cloudflare give me endless captcha forms. As soon as I solve one, it demands another, and never lets me access the website.

    Sometimes I solve one captcha, and then it says I’m blocked forever for sending automated queries, even though I filled it out correctly. The error message is: “You are blocked.”

    Sometimes it lets me in after one captcha, but I still resent having to enable Javascript for these assholes just to access a site that doesn’t otherwise require Javascript.

    Sometimes Cloudflare adds extra security to certain pages, just for me. The developers of the website didn’t program it to handle this extra security, so the site fails for just me, and the site developers don’t believe me, telling me I have a browser problem (in three different browsers, which I can fix by using a proxy). For example, when the site’s javascript has my browser to do a CORS operation, the first step is the browser sending an OPTIONS request. However, the extra security of the proxy introduced by Cloudflare responds slightly differently from the actual website, so the site breaks.

    Cloudflare uses a holistic approach to deciding whether you are a legitimate user or a bot. In other words, they use every single possible piece of data they can get on you, including tracking your visits across other Cloudflare sites. They do discriminate against certain user-agent strings.

    Cloudflare completely blocks many Tor users, even from having read-only access to a site.

    When you ask Cloudflare why your IP address is blocked, they falsely claim that it’s a setting created by the website admins. I strongly suspect that this setting is something like “use Cloudflare™ Adaptive Security™” and probably doesn’t explain to the site admin that they’re blocking large quantities of innocent users.

    Cloudflare has previously used Google Recaptcha, which has a ton of problems (tracking, accessibility, training AIs that will make my life worse).



    You are correct that the Desktop Environment and Package Manager are the most important part of any distro. Of those, the Desktop Environment is the most important. Switching between Ubuntu with KDE Plasma and Arch with KDE Plasma is less visible of a change than switching from KDE Plasma to Gnome in any distro.

    Most distros include all the major Desktop Environments: Mate, Gnome, KDE Plasma, and probably several more.

    The biggest missing feature between Mint/Ubuntu/Debian is Container-based package management. This is an additional installation method, for “application”-like programs, usually proprietary. Debian has the infrastructure to run these, but you have to find or make the containers yourself. Mint has more support, in the form of a graphical package manager installed by default.

    There’s really not much difference in the feature set of distros. Debian, Ubuntu, and Mint have a lot more in common than they have differences.

    Desktop environments usually include a full set of these. I just use whichever comes with it.

    Linux usually has the drivers already set up right away on first boot. You shouldn’t need to install any drivers. There’s very little bloat. Any superfluous packages are likely consuming no CPU time, just drive space. Every default installation comes with a media player and file archiver, but you can install VLC or RAR if you like them better.

    They probably had a bad experience with one or more qt-based programs, or got a negative response when they filed a bug report to a qt program or library. Or, they were using some weird mix of old and new software, and ended up in a weird dependency loop that blocked a large set of packages on their system.

    Probably. The most common distros will have the most community support.

    Spend most of your effort choosing a Desktop Environment. Fortunately, this can be changed after installation.



  • When you get to the “Installation Type” page, try selecting “Something Else” instead.

    Then, go to “Manual Partitioning”. From that point, create a single 1GB partition (unencrypted) for the “/boot” filesystem, and then use the rest of the drive as an encrypted volume. It will ask for a password, and then you will see a new encrypted drive appear. Use that newly created encrypted drive as the “/” filesystem.

    I just recently installed a system this way, and it worked well in Ubuntu. I couldn’t do it in Kubuntu though, I don’t think the Kubuntu installer supports encryption.