The OOM killer always, invariably starts off with killing the display server. Any side effects such as "the notification daemon loses its connection and closes" or "every single thing that you were working on loses its connection and closes" is incidental.
"Drivers" are only when you do ring 2 message passing in a hurd microkernel. Everything else is just "late-bound function call steering that happens to satisfy hardware-specific device communication and control".
"Two pointers" makes a lot of sense if you actually have the ability to pay attention to two things simultaneously. Most froods are not hoopy enough for this.
Is anything going down in the system log when you mount a drive, or trigger an access error? If it's (one of the many) security systems clamping down, they tend to log that.
It's fucking crazy how much work goes into shitting out thousands and thousands of slightly different models of android phone and tablet and chromebook. Slap together a board design based on buying two trays of some SOC. Open up the Android source, slap some NDA drivers in, build an image, burn it into a production run. Don't bother saving your changes, these devices will never get an update. Two weeks later, change out the whole design for a different chip, repeat.
rotopenguin @ rotopenguin @infosec.pub Posts 0Comments 614Joined 2 yr. ago
You're lucky she didn't straight up cut ya