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

help-circle



  • Unfortunately this won’t happen until October 31st 2600. Starting on March 1st in the year 2600, the Julian calendar (popular in centuries past, and still used in a few places) will differ by 18 days from the Gregorian calendar (the current worldwide standard calendar).

    It happens that October 31st in the year 2600 lands on a Friday, and so the Julian October 13th, which lands on that same day, is also a Friday.

    There may be a sooner Friday the 13th that lands on Halloween, if you know of other obscure calendars like the Hebrew, Islamic, or Chinese calendars. I don’t know enough about those to check.


  • The easiest way to disable unnecessary services is to uninstall them with aptitude, or whichever package manager you like. Try terminating services one by one, and see if anything bad happens. If nothing bad happens, you can probably uninstall it. On the other hand, if the system does get wonky a reboot should fix it. Or, you can research the services by name and decide whether to uninstall them. (avahi-daemon for example is a good idea to uninstall.)

    To make the GUI not run, uninstall your display manager (gdm, xdm, nodm, or whatever) and uninstall your xorg server or wayland server. There may be GUI programs remaining after that, but they will only be consuming disk space, not RAM or CPU.

    If the battery is old and holds little charge, you may save a few watts by removing it and throwing it away, instead of letting the system keep it topped off.

    Get a power meter, such as a Kill-a-watt device. Then, experiment with different settings. If it’s consuming less than 30 watts, you’re probably fine. If you live in the US, one watt-year is about one US dollar (or a little more), so for every watt it consumes, that’s about how much you will pay per year for its electricity.






  • No, it’s not dead. The number of players is irrelevant.

    A “dead game” is a game that needs work but is not under any development. It could be in Early Access, and incomplete. Or, it could be released, but still incomplete (looking at you, 7 Days to Die). Or, it could be an MMO that needs ongoing server maintenance, but they shut the servers down.

    A game that is being worked on and making good progress isn’t dead. A game that is complete and relatively bug-free, but not being worked on, is not dead. An MMO getting no new content, but just enough labor to keep the lights on and the servers up, is not dead.

    I guess an MMO or multiplayer game that has mandatory multiplayer aspects could be considered Dead if there aren’t enough players available to reasonably play the game. But Palworld is a single player game, or co-op with friends, not really an MMO.



  • I have three ideas: First, you could switch the desktop environment to one of the ones that has a GUI settings tool to set passwordless automatic sign in. I think Gnome 3 on Ubuntu, and Mate Desktop on Linux Mint have that feature. There are probably others.

    Second, you could switch your display manager to “nodm”. The display manager is the thing that runs the X server or Wayland, and it starts the greeter (the greeter is the program that shows the login screen). nodm is a special display manager that doesn’t use a greeter or ask for a password. It immediately starts the session using the username and desktop environment specified in its configuration file.

    I use nodm for my HTPC and it works very well. The only downside is that you have to edit its configuration file, /etc/default/nodm , using a text editor. I’m not aware of any GUI configuration tool for it. However, it’s pretty easy to configure.

    Third, you could abandon all display managers, and start the session manually, either from a shell script, or over SSH. This is a little more complex. You will probably want to get comfortable with SSH before trying this (SSH is the command-line analog of remote desktop).



  • I cannot recommend any USB-connected drive for long-term use. (Only for portable devices that get plugged in for a little while at a time.) In the long term, any USB drive will randomly reset during periods of heavy use – including heavy writes, meaning some data will get lost.

    USB enclosures tend to just crap out completely after a year or two, if used continuously on a server. I know because I twice used 1TB external drives with OpenWRT (home router) devices. The data will be safe on the drive, but you’ll have to replace the enclosure.

    1. My first recommendation would be to look very carefully at the chassis and see if there’s any way at all to fit another SSD inside it. 2.5" SSD’s are usually thinner than 2.5" hard drives, so it may be possible, and most motherboards have more SATA ports than they need.

    Is there possibly an NVMe slot on the motherboard? Or an open PCIe slot where you could put an NVMe adapter?

    1. My second recommendation would be using a 2.5" hard drive. Newegg has a 5TB one for $135, but unfortunately that’s as large as they seem to go. It will be a bit slower than an SSD, but still probably around 150MB/s for sequential access.

    2. My third recommendation, if money is really tight, would be an additional server, with a large 3.5" hard drive. This will be a lot cheaper than an 8TB SSD, but adds complexity, electricity use, space use, and possibly fan noise.



  • 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.


  • Haha. I sent them an opt-out notice by email, and it bounced!

    They are using Google email servers for discord .com and Google has apparently shadowbanned me. It gives an error message saying “The account [my email address] is disabled.” but I have never created a Google or Gmail account, and my email address is on a domain not associated with Google at all.

    So I’ve completed my obligation to opt-out. Discord will have no record of it, but I have the email server logs to prove I sent it.

    If, in the future, anyone needs to sue Discord and forgot to opt-out, feel free to use this same excuse.


  • 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.