this post was submitted on 26 Mar 2024
638 points (96.4% liked)

linuxmemes

20762 readers
1766 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
638
What is the most difficult problem that you have fixed in linux? (lemmy.world)
submitted 5 months ago by Waffelson@lemmy.world to c/linuxmemes@lemmy.world
164 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Hadriscus@lemm.ee 3 points 5 months ago (2 children)

This is so arcane to me. Like, I more or less understand your high-level explanation, but then you gloss over "including the block offset" but how would one do that ??

[–] DickFiasco@lemm.ee 5 points 5 months ago

Inspecting the file with a hex editor would give you lots of useful info in this case. If you know approximately what the data should look like, you can just see where the garbage (header) ends and the data starts. I've reverse engineered data files from an oscilloscope like this.

[–] T4V0@lemmy.world 2 points 5 months ago* (last edited 5 months ago)

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