4 ms·

One reason is that a big community effort to rewrite the suspend-to-disk layer, which made it more reliable, called TuxOnIce, was kept out of the mainline kerne

One reason is that a big community effort to rewrite the suspend-to-disk layer, which made it more reliable, called TuxOnIce, was kept out of the mainline kernel for a number of reasons, and thus a lot of "community energy" for solving the problem has been sapped out. Also, this is a uniquely "desktop Linux" problem, so exactly the kind of problem that rarely gets commercially sponsored developer hours thrown at it. https://en.wikipedia.org/wiki/TuxOnIce https://en.wikipedia.org/wiki/TuxOnIce

exmadscientist 5y ago
I am surprised that your comment is the only one that seems to engage with the historical reality of suspend and hibernation on Linux. So many people seem to be ignorant of kernel history, and how things came to be the way they are. I followed kernel development closely 10-15 years ago, paying particular attention to hibernation because, well, it was rather more useful back then! And one thing that gradually became clear over the years was that there was one person in the kernel community, with a lot of responsibility, who was completely and utterly incompetent to handle that position. That one person, in my opinion, set Linux hibernation back by more than a decade.
- Shorel 5y ago
  Who?
- Buttons840 5y ago
  Was the choice to have either one incompetent person or no person?
  - exmadscientist 5y ago
    No. From what I saw, this person actively blocked attempts by others to make things better. It seemed to be something of a classic personal fiefdom. (Combined with a bit of genuine technical incompetence.) (And to sibling: I'm not going to name any names, since I prefer not to shame in public. Especially when most all of what I did was read LKML, so who knows what background stuff I'd missed. I'm afraid you'll have to come to your own conclusions.)

4 ms·

One reason is that a big community effort to rewrite the suspend-to-disk layer, which made it more reliable, called TuxOnIce, was kept out of the mainline kerne

by pixelmonkey 5y ago

exmadscientist 5y ago
I am surprised that your comment is the only one that seems to engage with the historical reality of suspend and hibernation on Linux. So many people seem to be ignorant of kernel history, and how things came to be the way they are. I followed kernel development closely 10-15 years ago, paying particular attention to hibernation because, well, it was rather more useful back then! And one thing that gradually became clear over the years was that there was one person in the kernel community, with a lot of responsibility, who was completely and utterly incompetent to handle that position. That one person, in my opinion, set Linux hibernation back by more than a decade.
- Shorel 5y ago
  Who?
- Buttons840 5y ago
  Was the choice to have either one incompetent person or no person?
  - exmadscientist 5y ago
    No. From what I saw, this person actively blocked attempts by others to make things better. It seemed to be something of a classic personal fiefdom. (Combined with a bit of genuine technical incompetence.) (And to sibling: I'm not going to name any names, since I prefer not to shame in public. Especially when most all of what I did was read LKML, so who knows what background stuff I'd missed. I'm afraid you'll have to come to your own conclusions.)