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/)L
Posts
0
Comments
105
Joined
3 yr. ago

  • Looking forward to seeing OpenGL in Wayland wine. I assume this will enable many more games to run there. Currently, I can only get 3D games to run on the new driver while 2D stuff needs the X11 one.

    Granted, none of this is urgent or super needed. But still nice progress

  • If you want to be compliant to the UEFI spec, the partition holding your EFI binaries must be formatted as a file system related to FAT (see https://en.m.wikipedia.org/wiki/EFI_system_partition). This is not something you want for you system drive, so a separate partition makes sense.

  • They aren't really designed to stop people from breaking in but rather to stop intrusive people that you talk to first before deciding to not let them in. With the chain, you can open the door a bit without allowing the person outside to force himself in without too much force, e.g. by blocking the door with your foot as the door can only be opened fully after closing it.

    Advanced versions exist where if you put strain on the chain (mostly trying to push the door open from the outside) an alarm goes off.

  • Why would you install that door chain thing like that, it makes no sense

  • The search index isn't managed by you package manager, is it?

  • OpenPGP is kind of like the opposite of that - it does a lot of things, and none of them particularly well. To quote:

    PGP does a mediocre job of signing things, a relatively poor job of encrypting them with passwords, and a pretty bad job of encrypting them with public keys. PGP is not an especially good way to securely transfer a file. It’s a clunky way to sign packages. It’s not great at protecting backups. It’s a downright dangerous way to converse in secure messages.

    minisign is more in the UNIX spirit.

  • There has even been -1% before

  • This is Russia's final warning.

  • If it's a machine you have control over you can install the terminfo. Or setting the TERM variable to something like xterm-256color when connecting, that usually works, though I haven't tried with tmux.

  • kitty is great, for me it's similar to mpv: it does what it's supposed to do, no fluff. Just straight up performance.

  • I thought so too but learned recently that Guix system is nix under the hood, basically translates everything, so it's more than a conceptual fork though obviously some more work went into it than your average Ubuntu fork.

    It uses low-level mechanisms from the Nix package manager, but packages are defined as native Guile modules, using extensions to the Scheme language—which makes it nicely hackable.

    https://guix.gnu.org/en/about/

  • Or you can add specialisations, which to be fair might require a reboot (system accounts might change during specialisations switch which will confuse the script trying to reload services for the now non-existent user) but it is how I have multiple DEs installed without their applications flooding the other ones, each with their own login manager (SDDM for plasma, gdm for gnome, greetd for sway).

  • Very good explanation. It's an often overlooked property of NixOS and why I often feel like Nix on other systems is an okay way to get packages but you're missing out on all the good stuff you get through the modules, like losing 95% of what makes the concept good.

    I don't think NixOS is the best possible solution to the problem, but it's the only original distribution that even tries to tackle it instead of just working around it.

  • Another aspect I like about Nix compared to what I understand from Ansible (which I used a bit but not much) is that your configuration describes your system without any hidden state. Yes, you only get your dependencies through full evaluation, but what I mean is this: Let's say you install something on a system, i.e. you add it to your list of packages, which you later remove. To my knowledge, Ansible won't remove the package if not explicitly asked. However, if you explicitly tell Ansible to not have it installed, what happens if that package is later introduced as a dependency?

    Ansible will always operate on a stateful system, which is kind of the combination of what others have already mentioned – it's (EDIT: it being Nix) idempotent and there's no hidden state that will break something down the way.

  • It's in the release notes, you add a Wayland driver to your prefix via registry entry and then unset DISPLAY before starting wine.

    https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0

    The Wayland driver is not yet enabled by default. It can be enabled through the HKCU\Software\Wine\Drivers registry key by running:

    wine reg.exe add HKCUSoftwareWineDrivers /v Graphics /d x11,wayland

    and then making sure that the DISPLAY environment variable is unset.

    Note that the registry entry is per prefix.

  • I'm on 9.0 staging and can use wine with Wayland, but not everything works, window bars etc look somewhat off and some games don't start at all, like Stardew Valley. Other games I tried failed to hide the cursor. Others worked just fine.

  • Western society is in no way closer to that point. What you're reading is the counterpoint to "a glass of wine a day is good for your health" when in fact it's not. People ask "how much can I drink without it affecting my health" and the honest answer is nothing. You're obviously right that any substance is more dangerous the higher the amount. You also can't tell beforehand what the exact risk is because this is a statistical question. But just because the outcome is not perfectly predictable doesn't mean there's no risk.