Originally Posted by
sonatine
Bluetooth. Linux distributions generally ship with bluetooth support. And even when you remove the drivers or tools to manipulate bluetooth, often various frameworks will retain vestigal folders, libraries on occasion, so on. They are not in use and have no operational impact probably but they are there due to anything from sloppy programming to license weirdness.
They're in /var/run for a system that has never had Bluetooth support. They're loaded as modules. They have open sockets.
Even if you could delete the socket files, delete the /var/run files, and rmmod -fv the modules the thing about write protected base system loop images is they'll just put them all back.
Second comment; never forget that with any contemporary linux distro, 80% of the code is just sloppy workarounds to mitigate other peoples errors that have become architectural canon. So often, things appear not to make sense simply because we are exposed to compromises, not solutions.
You're preaching to the choir re: the creepy incompetence used by creepy 'freedom' hackers who love their redundant sloppiness but then if you caught them with their dicks in your prepubescent daughter, for a year - you'd be less likely to mitigate their inexplicable.
And this is chromeOS, and I've been in this newly write-protected clusterfuck before. It had no Bluetooth then, it was read-write and Google cleaned up a lot of that creepy bullshit.
This is not leftovers or vestiges. This is Unix sockets to pipe into my sub-system.
http://www.chromium.org/chromium-os/...he-source-code
When you see a message like "TMP not OWNED", consider strongly doing a recursive grep through source code looking for that error. The effort may or may not be useful or productive but its certainly immsersive and the answer is literally always in there.
Pretty sure the Answer is in the obvious but if I knew how to grep I'd probably look into it. I could learn, I suppose but..
I just woke up at midnight from a 3 hour nap and I have to pick my father up at the airport in like 23 hours so Im a bit of a mess.
..I can wait. 55
I certainly consider it possible that you have a legitimately corrupted Chromebook but Occams Razor says you misinterpreted a benign error and flipped the wrong bit and made it worse, of course. Which is something computer people are rather known for.
Pretty hard to do on a read-only filesystem; which one imagines, is the point of the loop devices being used to load my OS.
Also, there are only so many Occam Razors one can negotiate before the stack of razors becomes telling, in their own blunt ways.
Linear Mode
