I don't run Ubuntu myself, but CONFIG_X86_X32 isn't a new architecture, it's an option for 64 bit kernels. Based on the state of that bug report, it looks like it's an option they've enabled in their recent 64 bit kernels (Quantal+)
You need a completely different userland, compiled for x32 instead of amd64. Just running the default amd64 installation with a x32 kernel doesn't make it x32. EDIT: It would also work for just running x32 apps on an amd64 system, but then you only get the x32 benefits for those applications.
You don't need a whole x32 userland in order to be exploited. Just a single x32 binary executable that happens to not depend on on any external libraries.
I did't mean for an exploit, I just meant that you don't have any use for a x32 kernel on your system if you don't have x32 apps and libraries (unless you build a statically-linked x32 app).
I realized after writing my post that you don't really need an entire system, just the x32 libraries (and not even those if you statically link your x32 application).
That's the same thing I thought, until I got my Air (2012 model with the new charger).
Within my first half hour I had accidentally unplugged it 5 or 6 times, just by moving it around in my lap. Pick up the cord and plug it back in each time, it starts to get a little annoying.
I've gotten better with it now, but I will still do what this video shows, where it doesn't completely unplug. You don't always notice until you get a low battery warning when you thought it was plugged in the whole time :(
Has anyone else noticed you can move most of the design elements around and they interact with the balls. Everything except the Android holding the QR sign, the clock itself and the copyright line can be dragged around. The Google IO logo is the only one that you can move, but doesn't interact with the balls.
