• 4 Posts
Joined 1 year ago
Cake day: June 11th, 2023


  • Yeah, I’ve always found terms like “content” (and by extension “content creator”) to be degrading and corporate-focused. It’s weird to me that it’s such a common way to refer to the work of artists and entertainers online. I don’t do anything of the sort, but it’s got to be rough being pushed so hard into chasing the algorithms to stay relevant.

    I’ve yet to be disappointed in anything TWRP’s put out.

  • I think they got the nvidia driver accumulation thing straightened out. On Fedora 40, I had it automatically remove a bunch of older versions and now it only lists the 64 and 32 bit versions I expect it to.

    $ flatpak list | grep nvidia
    nvidia-550-76	org.freedesktop.Platform.GL.nvidia-550-76		1.4	system
    nvidia-550-76	org.freedesktop.Platform.GL32.nvidia-550-76		1.4	system

    Edit: looks like it’s fixed by this.

  • /etc is writable, so no reboots are required. That said, /etc is treated in a special way and each deployment will have its own /etc, based on the previous one.

    So if you make changes to /etc then revert to a previous deployment, your changes will be reverted as well. But if you make changes and upgrade (or do whatever to create a new deployment), your changes will bu preserved.

  • fortified_banana@beehaw.orgtoLinux@programming.devMe: Linux isn't that bad! Also me:
    3 months ago

    Looks like you’re on Fedora Silverblue (or other Atomic version). This is happening because the system groups are in /usr/lib/group rather than /etc/group and this causes the issue you’re seeing here. You can work around it by getting into a root shell with something like

    sudo -i

    and then getting the group added to /etc/group with

    grep -E '^dialout' /usr/lib/group >> /etc/group

    after that, you’ll be able to add your user to the group with

    usermod -aG dialout pipe

  • fortified_banana@beehaw.orgtoLinuxCloudLinux?
    9 months ago

    As far as I’m aware, CloudLinux is based on CentOS for older versions, and Alma Linux for newer versions, so it would be in the RHEL sphere of things.

    They’re also the company that launched and continues to sponsor Alma Linux, a community run RHEL compatible distribution.

  • I’m not sure about using xml files, but there’s also a ‘picture-uri-dark’ key you need to set instead if you’re using dark mode. I have a similar setup with a systemd user timer that runs every 5 minutes.

    Edit: I just tried it out in the terminal and it works ok for xml files, too. Also, I try to avoid parsing the output of ls in scripts. You can use find instead, something like

    find $wallpath -name '*.xml'

    should work.

  • Not quite the same issue, but similar in the sense that it was caused by a UEFI that didn’t conform to spec.

    I have an HP laptop that I installed Debian on, and it would never actually boot to grub even though I checked the boot entries several times over. You could open the settings and choose the boot entry manually, so it’s not like it was a problem with the OS or with grub. Turned out, this model was hard coded to only allow a boot entry named “Windows Boot Manager” to be loaded by default. I used efibootmgr to rename the debian entry and it booted into grub straight away.