I'm surprised I didn't hear about this via email direct marketing!

"Glass cubicle walls will cut down on noise like a cubicle would, but does not give as much of the feeling of being in a box as standard cubicles. They allow unobstructed view of the video-wall and you can write on them with grease pens."

They also allow an unobstructed view of things you really don't want to stare at such as bright lights.

My experience is from the dev cubicle floor, not a NOC, but it applies at least as much to monitoring a screen or screens as to staring through the screen into the code-realm. Bad placement plus a low ceiling meant that I had a bright fluorescent fixture showing just above the cubicle corner. I tried sunglasses, moving the monitor, etc. and ended up roofing that corner of the cube with cardboard, just so I didn't have that light stabbing my eye while I was trying to dive into my code. Glass cubes will exacerbate this into a no-escape situation. Nobody's going to want to keep staring at a view which is actually painful.

Even if you don't go with glass, before you sign off on that build, have a short person and a tall person test out every station for glare within scope of view. Be prepared to hood some of those lights to keep them out of people's eyes.

Someone with a schematic of the car should have a look to see how those signals are generated and routed. If they go through the same microcontroller...

In my Chrysler-made minivan, I've learned that headlights have to be turned off BEFORE the engine is stopped. If I switch the lights off first (two steps on a rotary knob), things work fine no matter how fast I twist that knob; both switch-events are caught.

If I turn the key first, though, turning off the engine before shutting off the headlights, both headlight-switch events will be missed by whatever MCU drives the headlight relays. The lights are on, the door is open, the engine is off, but I get no chimed 'lights left on' alert unless I put that switch through another full-on-full-off cycle to resync the micro with the physical state of things.
My guess is that the same MCU is responsible for a number of tightly timed engine-shutdown sequence events during which it has to mask off switch interrupts, which is lousy embedded design on Chrysler's part.

Nothing says that the same crappiness of design isn't evident in Toyota's machines, in which case the timing of those brake lights coming on means exactly nothing: that pedal might have been pressed for some seconds before the MCU got around to noticing.

*poof*

You're a sandwich.

The reason for the Idle category is so crap like this can be put there, and I can block it.

That's a genuinely good point, I wonder if Sony would help them out on this or if they are getting the old one or what?
I don't have much of a use for linux on mine TBH, it was far too goddamn slow (and I'm no linux guru) it really does need 1gb or more of ram, then she'd be fine.
That being said, sucks for researchers who wanted this.

All the time I spent vacuuming out dead roaches from my computer cases... wasted. If I'd mashed them flat instead, obviously I'd have had a lot fewer live bugs to eliminate from my code as a result.

There's nothing like a screen that even remotely appears to respond to viewer interaction to get children involved. They won't tell you this, of course, but you'll know immediately by the trails of peanut butter, jelly, ketchup and various bodily emissions left as bookmarks in their favorite places on your console. Trust me on this.

Not exactly my preferred mind-picture of "open source", thank you.

As straight technology, this is great: easy familiarizing exposure to Linux for the Windows users who fear the unfamiliar, and a blowout end-run around MS's restrictive agreements with OEMs on what OSes are allowed where. That said, the BIOS vendors are typically biased towards proprietary exclusivity, so I'll be inclined to be wary. How open-source will that HyperSpace environment (the apps and applets running on Linux) be? Or, more likely, how hard will it be to jailbreak it so one's choice of apps can be loaded in from an USB drive instead? This looks like a nice subtle screw-you to Windows, as long as it's not just as much a screw-you to FOSS.