I take my shitposts very seriously.

  • 14 Posts
  • 658 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle


  • They absolutely are, in terms of gameplay. Ozzy Mandus and The Crank Hog Machine sacrificed most of the gameplay Frictional’s Amnesia became known for. There are no light mechanics. Barely any physics puzzles. The pigmen are braindead, which removes the challenge and the tension. Even if it’s a better story and atmosphere than The Dark Descent, it’s a lesser game. Even Still Wakes The Deep only goes as far as “throw the object to make the thing look away” when you’re not just responding to non-diegetic prompts.

    You can make the argument that walking simulators have a place in the gaming landscape, and you’d be right, but by their nature, they are the exact opposite of what Bloodlines 1 was and what Bloodlines 2 should have been. Why Paradox decided it was a good idea to entrust with it a studio that has only made things that it never should have been is a fucking mystery to me.



  • rtxn@lemmy.worldtoLinux Gaming@lemmy.worlddont do this.
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 day ago

    The option doesn’t have a value. You just need to specify that the option should be present, e.g. defaults,noatime,windows_names,uid=1000,gid=1000 in fstab, or mount.ntfs -o noatime,windows_names,uid=1000,gid=1000 for manual mounts.

    This comment on the UDisks github page elaborates on why the ntfs-3g driver does not automatically restrict the usable characters.

    UDisks itself does mount NTFS volumes with the windows_names option, and the last comment in the same thread explains why enforcing that restriction with no way to opt out is a breaking change for some users.


  • rtxn@lemmy.worldtoLinux Gaming@lemmy.worlddont do this.
    link
    fedilink
    English
    arrow-up
    31
    ·
    2 days ago

    uid=1000,gid=1000,dmask=022,fmask=133

    You can very easily fuck up your NTFS filesystem and make it unmountable in Windows. Would anyone be surprised to learn that not even Windows is fully compliant with the NTFS specifications? Some characters, like :, are valid for NTFS filenames, but illegal in Windows, and if you create such a file (e.g. in a wineprefix’s dosdevices), Windows will refuse to mount it. Ask me how I know.

    The solution is to specify the windows_names option every time you mount the filesystem, both in fstab and when using mount.ntfs.





  • You can host the open-source ID and Relay servers for simple remote access at no cost. The pro subscription is mainly about account and device management.

    compose.yaml
    services:
      hbbs:
        container_name: hbbs
        image: rustdesk/rustdesk-server:latest
        command: hbbs
        volumes:
          - ./data:/root
        network_mode: "host"
        depends_on:
          - hbbr
        restart: always
    
      hbbr:
        container_name: hbbr
        image: rustdesk/rustdesk-server:latest
        command: hbbr
        volumes:
          - ./data:/root
        network_mode: "host"
        restart: always
    





  • You can, technically, but there are some caveats.

    SteamOS is not a general purpose OS. It is optimized to run on the Steam Deck (plus the Frame and Gabecube I guess). Its software components are tested on a limited range of hardware (specifically AMD silicon), and it might not have certain optimizations and compatibility fixes that are required by other consumer hardware. It also probably has some proprietary bits, especially the firmware.

    The best option is Bazzite. It’s not based on SteamOS, but it is built with a robust gaming experience in focus. You can even get it to boot directly into Steam Big Picture. Watch this loud Aussie man do it!

    The other option is HoloISO, which is an independent reimplementation of SteamOS. Their intention is to get as close to the real SteamOS as possible. Hardware support is limited (especially nvidia).



  • Why split physical and data link when they are so closely related?

    You can run Ethernet on any medium that has the capacity to transmit digital signals. It can be copper, optical, over-air laser, radio, on top of an analog carrier wave (ASK, FSK, PSK). The Ethernet traffic can be completely independent from the physical medium by using encapsulation (L2TP or any other protocol that encapsulates Layer-2). It can be pigeons carrying printouts of the Ethernet frames, scanned and reassembled at the destination. The same can be said about most Layer-2 protocols.

    As long as the proper interfaces are present, the physical layer is completely transparent to the data link layer.

    (edit) I should point out that Ethernet, specifically, transmits extra data before and after the frame (the preamble and inter-packet gap) that are used to configure the Rx circuit for reception, but the Layer-2 frame will be identical regardless of the medium.