OLPC XO Opera browser as Sugar activity

[John Gilmore]

> The activity start script should configure Opera to put its  
> configuration file in $SUGAR_ACTIVITY_ROOT/data instead of  
> $HOME/.opera. Also it should set umask to 0002 so the config file is  
> group-writable (otherwise the next activity instance cannot overwrite).
> 
> See http://wiki.laptop.org/go/Low-level_Activity_API#File_Access

> > QSettings: error creating /home/olpc/isolation/1/uid_to_home_dir/ 
> > 10000/.qt
> > opera: Can not use personal directory: /home/olpc/isolation/1/ 
> > uid_to_home_dir/10000/.opera

This looks more like a bug in Rainbow than in Opera.

Why would Sugar or Rainbow be setting $HOME to a rainbow-created
directory that the activity can't make subdirectories in?

(The universe of Unix programs isn't going to rewrite itself because
OLPC decided that $SUGAR_ACTIVITY_ROOT is the right place to keep your
files on Unix.  $HOME has been that place for decades.  Rainbow is
already setting $HOME.  It's just apparently setting it to something
that doesn't work.)

> Also it should set umask to 0002 so the config file is  
> group-writable (otherwise the next activity instance cannot overwrite).

If Rainbow runs the same activity as many different UIDs that share a
single group ID, then yes, Rainbow should be setting the umask so that
files are created group-writeable by default.  There should be no need
to modify ordinary Unix programs for this.

	John