this post was submitted on 26 Sep 2024
1007 points (98.3% liked)

Technology

60047 readers
2829 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
1007
Paralyzed Jockey Loses Ability to Walk After Manufacturer Refuses to Fix Battery For His $100,000 Exoskeleton (www.404media.co)
submitted 2 months ago by [email protected] to c/[email protected]
105 comments fedilink hide all child comments
 

Apologies for posting a pay walled article. Consider subscribing to 404. They’re a journalist-founded org, so you could do worse for supporting quality journalism.

Trained repair professionals at hospitals are regularly unable to fix medical devices because of manufacturer lockout codes or the inability to obtain repair parts. During the early days of the COVID-19 pandemic, broken ventilators sat unrepaired for weeks or months as manufacturers were overwhelmed with repair requests and independent repair professionals were locked out of them. At the time, I reported that independent repair techs had resorted to creating DIY dongles loaded with jailbroken Ukrainian firmware to fix ventilators without manufacturer permission. Medical device manufacturers also threatened iFixit because it posted ventilator repair manuals on its website. I have also written about people with sleep apnea who have hacked their CPAP machines to improve their basic functionality and to repair them.

PS: he got it repaired.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 125 points 2 months ago (2 children)

They call it jailbreak because this is an issue of freedom

I support your position and the right to repair, but that’s not the origin of the term jailbreak in the context of computing.

The term jailbreaking predates its modern understanding relating to smartphones, and dates back to the introduction of “protected modes” in early 80s CPU designs such as the intel 80286.

With the introduction of protected mode it became possible for programs to run in isolated memory spaces where they are unable to impact other programs running on the same CPU. These programs were said to be running “in a jail” that limited their access to the rest of the computer. A software exploit that allowed a program running inside the “jail” to gain root access / run code outside of protected mode was a “jailbreak”.

The first “jailbreak” for iOS allowed users to run software applications outside of protected modes and instead run in the kernel.

But as is common for the English language, jailbreak became to be synonymous with freedom from manufacture imposed limits and now has this additional definition.

[–] [email protected] 47 points 2 months ago* (last edited 2 months ago) (1 children)

Thanks for the history and technical explanation. I didn't mean to imply that was the origin (for computing) and was only talking about a specific usage of the word.

I think most people say it to refer to manufacture imposed limits but I wanted to promote a broader usage. That using proprietary software is like being in a jail because your software freedoms are denied.

[–] [email protected] 22 points 2 months ago (1 children)

Oooo healthy online discourse. Where's my popcorn...

[–] AmbientChaos 7 points 2 months ago

Lemmy is such a rad place, I love it here

[–] [email protected] 1 points 2 months ago

With the introduction of protected mode it became possible for programs to run in isolated memory spaces where they are unable to impact other programs running on the same CPU. These programs were said to be running “in a jail” that limited their access to the rest of the computer. A software exploit that allowed a program running inside the “jail” to gain root access / run code outside of protected mode was a “jailbreak”.

I still miss the narrow window in which you could make use of paging without technically being in protected mode. Basically there was like one revision of the 386 where you could set the paging bit but not protected mode and remain in real mode but with access to paging meaning you got access to paging without the additional processor overhead of protected mode. Not terribly useful since it was removed in short order, but neat to know about. Kinda like how there were a few instructions that had multiple opcodes and there was one commercially distributed assembler that used the alternative opcodes as a way to identify code assembled by it. Or POP CS - easily the most useless 80086 instruction, so useless that the opcode for it got repurposed in the next x86 processor.