I take my shitposts very seriously.

  • 4 Posts
  • 345 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle

  • I never watch TV anymore, but commercials still find a way to get at me. If I want to watch an older series, I have to consciously avoid certain regional releases because they might have scenes removed to cram in an extra five minutes of ads. The fade-outs and immediate recaps that would’ve surrounded the commercial blocks are also annoying.


  • (edit) I assume you’re mounting the NTFS volume using fstab, which is how you should mount internal drives. If you’re trying to use the file manager to mount it dynamically, you really should look into how to use the fstab file.

    I’d like to see your mount options.

    As others have said, it’s best to explicitly mount it with the rw option.

    Second, because NTFS doesn’t understand the Unix-like file ownership of users and groups, you have to specify the UID and GID of the mounted filesystem using the uid= and gid= mount options. If you don’t specify these, all files within the NTFS volume will appear as being owned by root. Use the uid=1000,gid=1000 options to mount the volume as owned by your user.

    Third, use the windows_names option as well. Otherwise the filesystem will allow you to create files with illegal names, and that will completely fuck up the volume when mounted on Windows. For example, the : character is permitted by NTFS, but not by Windows.

    Although, in general, just avoid using NTFS on Linux if you can. The driver is good, but there are too many basic conceptual differences between NTFS and most Linux filesystems.


  • Rapidly reusable orbital launch vehicles were unheard-of until Falcon 9. The Space Shuttle was supposed to fill that role, but NASA, ULA, and government elements have made it a horrid overbuilt pile of feature creep that was, at the same time, the crowning achievement of American aeronautical engineering, which was impossible to refurbish quickly. The same thing that is currently happening to SLS.

    Propulsive landing of a first stage booster was an insane idea. Even massive space nerds like Everyday Astronaut were skeptical, and I watched him cream his jeans live when the first booster landed. That alone, the ability to reuse both the structure and the engines of the booster, as opposed to ditching them in the ocean (or in China’s case, on top of villages), has made access to low Earth orbit significantly cheaper, and affordable to underfunded scientific organizations.

    That being said, competition is closing in. Rocket Lab (New Zealand) is targetin the same industry with the Neutron rocket (CEO Peter Beck literally ate his hat when the announcement was made) and is experimenting with recovering its smaller Electron rocket using mid-air capture by a helicopter. Astra (USA) is developing a rapidly deployable small orbital launch rocket that can fit inside a standard shipping container. There’s also Jeff Bezos and his massive overcompensation of a dick rocket that can also land propulsively, but not worth discussing.














  •   <form method="GET" action="https://duckduckgo.com/">
        <input name="q" type="text"/>
        <button type="submit">Go</button>
      </form>
    

    This is a fully functional search bar. This is all it needs to be. It doesn’t need Javascript, only if you want suggestions.

    The last time I checked, Google still works if you simply pass your query in the URL using the q variable. Google has no need to enforce Javascript.


  • I’ve done my tests, and it looks like I may have been incorrect.

    Point 1. While I was right to suspect the : character, I discovered that it is permitted in NTFS and only reserved in Windows. When an NTFS volume is mounted in Linux, it only becomes a problem if the windows_names option is used. Sometimes it is used, sometimes it isn’t, and I don’t know when.

    Point 2. The other thing I found is that Wine only works if the wineprefix is owned by the user. NTFS doesn’t understand Unix-style file ownership and permissions, so it must determine the uid, gid, and umask when the volume is mounted. When mounted with OP’s fstab entry, it will default to root, so every file (including the wineprefixes) within the volume will appear as being owned by root, which prevents Wine from starting.

    This might also explain why mounting the drive dynamically worked, as it probably used udisks2 to mount it as the user.

    The solution may be as simple as specifying the uid and gid mount options. In a system with a single user, they should both be 1000, but you can check them by running echo $UID $GID.

    The modified fstab entry should be:

    UUID=E01A2CEC1A2CC180 /mnt/games ntfs nofail,uid=1000,gid=1000 0 3
    

    This will present all files as being owned by the user, and should allow wine to run.

    Point 3. That being said, mixing Windows and Linux is still not a good idea. I don’t know what will happen if you create wineprefixes on NTFS. Windows might see the invalid filenames and shit itself. I tried doing it on a new NTFS volume and Windows wouldn’t even mount it.

    If you really want to keep the game files on the NTFS volume, you might have better luck trying your own symlink fuckery. If you have the Steam library on the NTFS device, you could try moving the .../SteamLibrary/steamapps/compatdata directory to a Linux filesystem, then creating a symlink in compatdata’s place that points to the moved directory. This method moves the problematic files outside the volume.

    The second method involves bringing the game files on the NTFS volume into the default Steam library on the Linux filesystem using a bind mount – a way to mount a directory at a different mount point. In essence, this replaces the .../steamapps/common directory with that on the NTFS volume, and avoids creating wineprefixes inside the NTFS filesystem in the first place.

    • Mount the NTFS volume using the fstab entry above.
    • Assuming that you have the Steam stuff in their default locations, execute sudo mount --bind /mnt/games/SteamLibrary/steamapps/common ~/.local/share/Steam/steamapps/common to create the bind mount manually.
    • Or use the equivalent fstab entry:
    /mnt/games/SteamLibrary/steamapps/common /home/salty/.local/share/Steam/steamapps/common none defaults,bind 0 0
    

  • Not really, because some files in the wineprefix will have invalid names.

    When an NTFS volume is mounted, it implicitly uses the windows_names option, which restricts the character set that can be used in filenames, in order to preserve compatibility with Windows. The specific character in question is the colon – it is permitted by NTFS, but it’s a reserved character in Windows, which means it is also restricted by the windows_names mount option. This prevents Wine from creating its c: and z: symlinks, which are required for Wine to operate.

    You could try some symlink fuckery, like linking .../steamapps/common to the NTFS drive, since all of the problematic files are located outside of that, in .../steamapps/compatdata. Or you could mount the NTFS volume directly to the common directory. If you do, I’d love to hear the results.

    Relevant issue: https://github.com/storaged-project/udisks/issues/713