this post was submitted on 24 Jul 2024
537 points (98.7% liked)

Technology

35125 readers
166 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] kristoff@infosec.pub 1 points 5 months ago (1 children)

Just watched some videos on btrfs. I start to understand the conceps. Perhaps I should also look into how exactly

On windows and the "recovery partion". I guess what you say is that it should always be possiblity to boot in some kind of system, but it will not happen automatically as there is no way for a system to detect that the system completely hangs.

Thinking about it. It kind of strange. Embedded systems have watchdog interrupts that get fired if the system hangs (i.e. if it does not provide a "yes, I still live" signal every "x" milliseconds). Does a PC not have something similar?

[โ€“] tetris11@lemmy.ml 1 points 4 months ago

embedded systems have the advantage of all using a single bootloader: Uboot, so the error path is always known and the software knows how to fallback.

With x86_64 systems it's a mixed bag, and maybe the windows and linux bootloader knows what to do, but in most cases it will just signal an error and stop