There have been unofficial statements that certain parts of the kernel and userspace, driving certain pieces of the SoC like the 3D rasterizer, will not have any corresponding source code available and will only be made available as licensed binary blobs.

Can we get an official statement on the matter? What's your stance on open drivers, and why are you for/opposed to them?

~ C.

https://github.com/MostAwesomeDude
https://www.ohloh.net/accounts/MostAwesomeDude
http://cgit.freedesktop.org/~csimpson/
http://git.kernel.org/?p=linux/kernel/git/csimpson/linux-2.6.git;a=summary

Your turn. Put up or shut up. >:3

We employ roughly as many programmers as sysadmins, and write plenty of code. http://code.osuosl.org/

I am not a full-timer, and I am not speaking on behalf of OSL.

The "legal reasons" alluded to are mostly problems with other signers on the contract for our upstream bandwidth provider. *coughDuckscough* At our bandwidth scale, tunneling is not feasible.

We don't run Puppet at the moment, we run CFEngine. Everybody's receiving Puppet training and there's a slow-yet-steady migration to Puppet, but these things take time. There are quite a few people depending on us to not fuck up, so we don't change our stacks without deliberation and testing.

I see what you did there. :3

Disclosure: I work for the Oregon State University Open Source Lab, which recently received donations from Facebook.

I've been out to this datacenter. They employed quite a number of locals to build the place, and although the skeleton crew is only 35, they plan to keep a bigger crew of hundreds out there most of the time. In the medium term, they plan to build *two* more buildings the size of their current one, extending their current need for construction for another two years or so, and requiring a reasonably-sized group of engineers to live in the Prineville area for a while. So Facebook's put money, jobs, and consumers into Prineville, and apparently, according to the locals, this was a real lifesaver for many of the construction workers who were otherwise broke and unemployed.

I'm not a fan of Facebook, but this doesn't really seem like a horrible corporate exploitation.

http://www.youtube.com/watch?v=WgbK0ztUkDM&feature=player_detailpage#t=3195s is the video. In short, I asked the NaCl guy whether they knew what they were doing by letting NaCl clients access GPUs directly. His response was that they were doing everything WebGL does to protect the system from malicious code. That's unfortunately not sufficient.

I asked the Chrome team (see http://www.youtube.com/watch?v=cQZu6azNlA0&feature=player_detailpage#t=514s ) and yes, it runs Gentoo Linux just like the Cr48. The marketing team at Google apparently has a Linux allergy.

Chrome OS is Gentoo Linux. One of the things that Google's marketing team isn't wanting to admit.

Did you know that Haskell, Ruby, and Python exist? They have many of C#'s features, while not being C#. Consider it sometime.

IOCP or WMFO are both options on Windows which are worth investigating. Thankfully, a bit ago (sometime last decade) somebody wrote a Java library called NIO (http://en.wikipedia.org/wiki/New_I/O) which provides platform-independent networking services, and somebody else included it into the Java standard library. Then, some people wrote a thing called MINA (http://mina.apache.org/) which provides even better networking services on top of NIO, and somebody else got the Apache guys to maintain it.

So yeah, there's no excuse for thead-per-connection these days. Using NIO or MINA in Java is the right way to build asynchronous servers.

Also, is that whole thread-per-connection thing gonna be fixed before then? (Signs point to no, of course.)

Specifically, my X.org student last year did some great work in the r300g Gallium driver for Mesa, and is still a developer in the project to this day. There's a single success story. I'm sure the other several thousand success stories will be along shortly.

I wonder if this iteration will be less prone to overheating. I have an original GuruPlug which still gets too hot to use for long periods of time.

OR? Oregon's not exactly a bomb-proof place, unfortunately. Portland, OR is one of the three good West Coast spots to drop a nuke. Intel's here, Linux is here (technically, Linux is in Corvallis, but still), and we're in range of ICBMs from the other side of the Rim.