Works on Voyager at least.
Works on Voyager at least.
Or PipePipe (at the time it was basically Newpipe with comments to me)
Could you explain what these bugs are? I’m curious.
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.
You should edit that to say Gnome Software (aka Gnome App Store) instead of just Gnome. People are going to think you’re talking about the whole DE.
For sure! At one point in winter I had to wear a second pair of pants to get through the day, and it was only in the 10°C range…
Yes, that was my first thought!
I mean, you can use decimals, but I understand your point.
To be honest, a 10°C range is way too much variation for me to consider it as the same ‘category’ (at least in the 0°C ~ 40°C range). I say that as a Brazilian.
That’s because it is!