Changes

===Comments===

===Comments===

I haven't been able to get this to work in Update.1 --[[leetcharmer]]

I haven't been able to get this to work in Update.1 --leetcharmer

Rob - I modified the script to work in Update 1 for SeaMonkey, but it requires an effective disabling of security.  The crux of the problem is that Rainbow 1) runs your application as a totally new user each time (never as "olpc"), 2) these "on-the-fly" users don't have write access to their home directories, and 3) these "on-the-fly" users are destroyed on reboot.    All of these users are created in the same persistent group, and all share write access to a common "data" directory for the group.  (The preceding is just a paraphrase of the Rainbow docs - should likely be a link).  In the case of non-Sugar apps, the application has no idea that the usual role of a user has been migrated to a group, and so the application is unlikely to create it's data files with the correct permissions.  Further, since the "on-the-fly" users are destroyed on each reboot, if the username appears in persistent data (e.g., absolute pathnames), the application will fail after a reboot.  All of these issues are addressed in the following for the SeaMonkey application.

Rob - I modified the script to work in Update 1 for SeaMonkey, but it requires an effective disabling of security.  The crux of the problem is that Rainbow 1) runs your application as a totally new user each time (never as "olpc"), 2) these "on-the-fly" users don't have write access to their home directories, and 3) these "on-the-fly" users are destroyed on reboot.    All of these users are created in the same persistent group, and all share write access to a common "data" directory for the group.  (The preceding is just a paraphrase of the Rainbow docs - should likely be a link).  In the case of non-Sugar apps, the application has no idea that the usual role of a user has been migrated to a group, and so the application is unlikely to create it's data files with the correct permissions.  Further, since the "on-the-fly" users are destroyed on each reboot, if the username appears in persistent data (e.g., absolute pathnames), the application will fail after a reboot.  All of these issues are addressed in the following for the SeaMonkey application.