These activities for the OLPC XO-1 are currently under development.
OLPC4Mac: Script to download OLPC software image and convert it into a virtual machine for use with VMware Fusion on the Mac. This is currently broken due to to bug #7770. Please leave a comment in that bug ticket if you'd like to run the OLPC OS image on your Mac using VMware.
Random OLPC and Sugar notes
- How do I run activities from within the terminal activity? sugar-launch hello should work (sometimes it just crashes, then a X restart is in place). But it needs the activity to be either installed or at least symlinked (setup.py dev does that). Attention: When run from the terminal, sugar-launch starts the activity without rainbow activity isolation! This is because the terminal activity runs without rainbow. But one can copy the terminal activity, change its names in the info file and then it has rainbow enabled (thanks m_stone).
- Who agrees with me that strings like [u'sugar-activity', u'webactivity.WebActivity', u'-s', '-b', dbus.String(u'org.laptop.WebActivity', variant_level=1), '-a', '1f1aa8b72736c0c0cfb921ded8296c2e0852677f'] are not precisely "human"... Why can't we just have something like "sugar-run /home/olpc/Activities/hello.activity"? Would do the job just as well, plus mere mortals could actually understand what was going on.
- There is no apparent way to run a bundle's main python file directly. Due to sugar "architecture", it needs to be run through sugar-activity
- To see the environment variables, run: cat /proc/XXX/environ | sed 's|\x00|\n|g'
- Activity isolation (rainbow) needs more documentation. Since the same activity runs under different user IDs, it is especially picky about permissions. chmod -R 0755 appears to work.
- "Documentation" says that $HOME points to something writeable by default. That seems not to be accurate, since only ./data (persistent) and ./tmp (non-persistent) seem to be writeable.
Simon Peter (probono myrealbox com)