Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ON
Posts
15
Comments
228
Joined
2 yr. ago

  • distrobox: Tool for creating one-off containers of a different Linux distro.

    container: A virtual OS environment that runs on your computer, but doesn't know that it's running in your computer. It's not the same as a VM or emulator.

    flatpak: A tool designed by RedHat for running sandboxed Linux programs in any environment. Flatpak can either refer to the system as a whole (eg: "You need to install flatpak on your machine to use our tools") or an individual program packaged for the flatpak system (eg: "You must download the latest flatpak of Firefox").

    AUR: The Arch User Repository. A collection of installation scripts to add software to Arch Linux. These scripts are not owned or maintained by anyone officially affiliated with Arch, so you can find AUR packages for almost anything.

    So, the comment becomes: Stick it in a dedicated environment designed to run Debian. Then package it so anyone can run it. Then make it easy for anyone running Arch Linux to install it.

  • It moves the old kernel modules to the right location for the old kernel to still find them after you've upgraded. When you restart the system to use the new kernel, the old kernel module symlinks are cleaned up.

    From what I understand, live kernel patching is only recommended for critical security fixes to server environments where you can't just boot off every user. https://wiki.archlinux.org/title/Kernel_live_patching

  • The user and group id inside the container doesn't have to match any user on your host machine. It's possible that user:70 is configured as the user to launch inside the container, in which case you should set the ownership of the directory to match what the container expects.

    Eg: The container for my torrent client runs as user 700 group 700. My host machine does not have either of those IDs defined. My torrent directory must be chown'd by 700:700 or else the container can't read/write torrents.

  • Agree with the other user that using tar and then zipping the tarball will preserve permissions.

    Alternatively, you could open an ssh connection and rsync the files between machines.

    Last option would be to export your recipes from the old host, build a new container from scratch on the new one, and import them back again: https://docs.tandoor.dev/features/import_export/

  • Have you checked for compatibility with the programs that are crashing? Before you go through the effort of installing everything, it's worth checking if anyone else got it to work: https://appdb.winehq.org/

    As for upgrading, that would depend on the distro you're running. What do you use?

  • Happened at my workplace. An phishing email went out to test how likely people were to click the link.

    Anyone who clicked the link had to take phishing training. Anyone who forwarded it to our internal "hey this is a phishing email" service also had to take training... because the internal service would automatically click the link.

  • The type of hobby club you join will impact how easy it is to meet people: Something like a hiking club is good, because you have to drive to the destination (free conversation if you car-pool with other members) and then there is the opportunity to talk to people during the hike itself.

  • I use Linux because all the games I want to play run just fine through proton, wine, or native builds. I used to have a dedicated windows partition, but maintaining windows got tedious. After testing that my games worked, I fully defenestrated and never went back.

    Sure, steam is proprietary and has flaws, but I'd rather run a proprietary and flawed userland application than a proprietary and flawed OS.

  • Granted, security isn't much my background, but that algorithm basically sounds like a TOTP, so I'd look into how people protect those secrets. You'd generally use a kind of vault/secrets storage. Also, whatever authentication secret that the API uses should be independent from the password to any user account, such that it can be easily revoked in case of a leak.

  • I actually like the QR button. It detects them faster than my phone's default camera app, and since I already know I'm going to open a link, it's nice to not have to switch apps.

    What I really want from fennec is the ability to selectively wipe browsing history over a long period of time. I changed the domain of a service on my home network years ago, but the address bar always suggests the old domain because it's a substring of the new one, and thus a "better match".

    My options are to scroll through years of history and individually remove every occurrence of the old domain... or wipe my entire browning history.