Add env var for GPU process sandbox.

content/gpu/gpu_main.cc

Index: content/gpu/gpu_main.cc
diff --git a/content/gpu/gpu_main.cc b/content/gpu/gpu_main.cc
index 92afb3b12ab3b37d201d4cfdcd3bb30eb2bda6b2..6ab3247551288917d5d739fec2dd57e001ded929 100644
--- a/content/gpu/gpu_main.cc
+++ b/content/gpu/gpu_main.cc
@@ -96,6 +96,13 @@ int GpuMain(const content::MainFunctionParams& parameters) {
       command_line.GetSwitchValueASCII(switches::kGpuDriverVersion);
   content::GetContentClient()->SetGpuInfo(gpu_info);
 
+#if defined(OS_CHROMEOS)
+  // On Chrome OS, we can now sandbox the GPU process using seccomp filter.
+  // This restricts calls to open(), so set the config line in /etc/drirc as
+  // an environment variable.
+  base::Environment::Create()->SetVar("force_s3tc_enable", "true");

[piman, 2012/07/10 23:53:05]

Sigh... that file may be used to do per-platform configuration. Is it going to
leak all over the place here instead of in Chrome OS per-board overlay?

Can't we change the driver to make sure that it reads that file early (before we
turn on the sandbox) instead?

+#endif
+
   // Load and initialize the GL implementation and locate the GL entry points.
   if (gfx::GLSurface::InitializeOneOff()) {
 #if defined(OS_LINUX)