• 0 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: December 14th, 2023

help-circle


  • Steam could build for 64bit

    Steam is doing that, though rather piecemeal. Both their client and runtime are moving towards 64-bit.

    but it won’t help the gigantic amount of games that are 32bit also.

    Doesn’t WINE’s WOW64 implementation solve this? Albeit with a non perfect compatibility.

    because macos bo longer ships with the 32bit libraries needed.

    I have no idea what the MacOS software landscape looks like, but if it uses WINE it might just be its silver bullet? If Steam does move towards 64-bit only, they would want to keep it compatible with Linux, due to their SteamOS ecosystem, and in turn MacOS users could also reap the benefits.




  • [Fun fact to lighten things up: people often call volts “velas” candles here. So e.g. “127V” and “220V” are often called “cem velas” (100 candles) and “duzentas velas” (200 candles) respectively. Confusingly enough some also do it with watts.]

    Never heard this before, brazilian here btw.

    All regular sockets in my city are 220V 60Hz. I think only places like hotels have different voltages.

    Or people who have old houses, 2 pins sockets, and rip apart the ground pin from their 3 pins plugs.

    Yep, my dad can’t stand the ground pin in almost every plug. I had to convince him not to destroy them all.










  • It’s not wrong per se, it’s just different. I don’t particularly like Discovery and Picard, but they’re ok. They don’t have the same monster of the week approach as the others, and a lot of the other stuff has already been discussed here; lack of development of the crew and their relationship, the main character is constantly on focus while everyone else in the bridge is in rear view, no breathing room for proper character development, the orcs/klingons, etc.

    I would rather watch Lower Decks, Prodigy or even The Orville. They’re closer to what I like about Star Trek (though The Orville takes a bit to get there).





  • Well, in this scenario the image file had 512 bytes sections, each one is called a block. If you have a KiB (a kibibyte = 1024 bytes) it will occupy 2 blocks and so on…

    Since this image file had a header with 512 bytes (i.e. a block) I could, in any of the relevant Linux mounting software (e.g. mount, losetup), choose an offset adding to the starting block of a partition. The command would look like this:

    sudo mount -o loop,offset=$((header+partition)) img_file /mnt
    

  • Not a Linux problem per se, but I had a 128GB image disk in a unknown .bin format which belongs to a proprietary application. The application only ran on Windows.

    I tried a few things but nothing except Windows based programs seemed able to identify the partitions, while I could run it in Wine, it dealt with unimplementend functions. So after a bit of googling and probing the file, it turns out the format had just a 512 bytes as header which some Windows based software ignored. After including the single block offset, all the tools used in Linux started working flawlessly.