The XEN hypervisor can potentially cause all guest systems (even dom0 is a guest under XEN) to get into a problem. Redhat ships a number of products directly under XEN so that may be why they report it.

Actually eating might corrolate decently. It's rare to find a chef that doesn't like to eat.

It mostly became impracticle to keep around after distros started taking measures to kill HAL after the HAL team had deprecated itself and was trying to move everything away from it. No idea what version was around then of kde4 though I had switched to it a bit before that since the bugs that existed didn't affect me too much and i didn't like gnome then either.

I've actually got an interestingly broken one. It isn't "off" or "on" but only has about 4 states in between instead of the 2^6 that the others have. Certain colors it's overbright, others its overdark. It's very weird to see and play with.

I always think of Betteridge's Law of Headlines

http://en.wikipedia.org/wiki/Betteridge's_Law_of_Headlines

I don't know. Getting a bunch of prepaid cards and then using them to get cash back at places doesn't sound like a half bad idea if you can pull it off fast enough to get some money.

The problem isn't necessarily the LEDs themselves but how they're hooked up. I'd be surprised if they aren't hooked up with a full wave rectifier or some other support circuitry to get them to output a more stable light, otherwise it'd be like cheap LED christmas lights all over your house.

IPV6 would get you that, IPV6 NAT would get you where you're at today with ipv4, one ip to the isp and outside world and then everything inside has a private address. NAT would make this impossible to do well.

That's because you can accesorize them into pink!

http://compare.ebay.com/like/170541070215?var=lv&ltyp=AllFixedPriceItemTypes&var=sbar
http://www.otterbox.com/strength/strength,default,pg.html

those are just the two i found off the top of google. I'm not sure about laptops, but for phones there's a huge market out there of customizations to make it "you" just like the thousands of others of people who buy the same cover.

I'm likely to consider diesel myself, though in my area it's actually the other way around price wise, about 20-30 cents higher than gas but it's been far more stable and if you really do get that much better milage it'll still pay for itself given how long the engines usually last.

Why hope it flops? There's currently projects to do network transparent wayland. In fact it should likely end up working much better than doing X over the network since it will be able to do things that and actually compress the data properly to get better transfer times and won't need so many round trips just to draw something (last i looked X needs about 4 round trips for putting something on the screen, minimum, all synchronous). Along with that you've got the rather annoying problems where X11 doesn't provide any good ways to render things in any decent way that actually works among all the drivers: Xrender [held up by nvidia still for their fencing code], XAA [being dropped since most other drivers have moved on], EXA [i think this is the latest one], UXA [done by intel that's very similar to EXA but uses GEM instead of TTM for memory on the graphics card], and then a number of others that are in embedded graphics DDXs that are only supported by the manufacturer because they don't want to give out code.

The situation with X11 is not as full of rainbows as people seem to think. Because of all the stuff above, most toolkits and libraries have stopped using X11 for doing anything other than pushing bitmaps, they're doing all font rendering in application, all widget drawing in application, all scrolling in application, the only thing the X server gets used for by the applications anymore is to display images and get input. That's what wayland is being written for, to replace the rather horrific design issues of the X11 server for handling the hardware.

Wayland aims to fix all this by instead using the kernel interfaces KMS and indirectly DRI2 (through Mesa). This leaves one interface to talk to hardware to maintain, far less code for bugs to be found in, and makes it possible to support things that X11 can't do right now like supporting hot plugging graphics cards, NVIDIA Optimus (the "support" in linux right now isn't really support. It's running two X servers and copying one of them to the other to make it look like there's only one).

This is pretty typical of CMOS sensors, you can see it happen on a digital camera if you try hard enough (usually need a laser).