"Symbian was a mass-market OS; Harmattan won't be.

The provision of a secure DRM system makes sense when the platform is your future, with content providers lining up to provide movies-on-demand and for purchase.

Maemo managed fine for years without platsec, and Android's recent malware problems show that having one doesn't prevent users granting permissions to apps which don't need them."

12 0

• I have improved the chrootmeego script to use variables, so you can customize how you run Meego.
• I have added a new syncmeego script that copies over the necessary files from Maemo to Meego. I got most of this script from this Meego wiki page, and I honestly don't know what effect the copied files actually have on the chroot (except the resolv.conf file, which we already knew about).
• I have enhanced the startmeegoui script, now called startmeegoui3. This script now starts the Xephyr nested X-Server inside Meego, gives it keyboard focus, and then starts the Meego UI. 
• I have added a new script, gomee (clever name, eh?), that opens the Meego chroot, syncs it, and then starts the Meego UI.

export M_USE_SOFTWARE_RENDERING=1

/usr/bin/mdecorator -software -remote-theme 2>/dev/null &
echo "sleeping..."
sleep 10
echo "...ok now"
/usr/bin/duihome --desktop -software -remote-theme 2>/dev/null &

10 0

• You have a working install of Easy Debian on your N900, and you can start the LXDE desktop in a window.
• You have made the image from the last post, and you have put it in your /home/user/MyDocs folder.

debbie /home/user/meego/meegoxeph
/home/user/meego/chrootmeego /home/user/meego/startmeegoui

if [ ! -d "/.meego" ] ; then
  sudo mkdir /.meego
fi
IMG="`ls -1 /home/user/MyDocs/meego*.img* | head -1`"
sudo qchroot $IMG /.meego "$@"

export DISPLAY=:1
/usr/bin/mthemedaemon 1>/dev/null 2>&1 &
/usr/bin/sysuid -software -remote-theme 1>/dev/null 2>&1 &
/usr/bin/meego-im-uiserver -software -remote-theme 2>/dev/null &
/usr/bin/mdecorator -software -remote-theme 2>/dev/null &
/usr/bin/duihome --desktop -software -remote-theme 2>/dev/null &

9 0

1. Unix/Linux commands and computer acronyms are commonly pronounced as words. "grep", which is a contraction of the g/re/p command, is pronounced as a word, as are many even less plausible acronyms. Try saying "s-c-s-i" instead of "scuzzy" in a computer lab and be prepared for the derisive laughter.
2. I think the chroot command was intended to reference the cheroot, a kind of inexpensive cigar also known as a stogie.
3. It is much easier to say. Why would you make work for yourself by saying a one-syllable word as two or three syllables?

• Binding: After a partition or image file is mounted, it isn't very useful for the kind of chroot we want here. A basic chroot is sometimes referred to as a "jail", because applications run in the chroot filesystem can't "see" anything outside of this filesystem. This means none of the devices, media, temp directories, nor even the user's home directory can be accessed while "inside" the chroot. That's why a careful use of the "mount -o bind" command is required. It mounts directories from the parent OS in the chroot, too, so applications in the "chroot" can "see" them. Mounting the /dev directory makes most of the devices connected to the system visible, and mounting everything under /media allows the chroot access to SD cards and attached external media such as USB drives. This also allows chroot apps to share the X display and desktop manager, so they appear to be running on the Maemo desktop. The qchroot script also mounts the various temporary directories, so that applications can communicate with applications in the parent OS. This means GTK apps inside the chroot can invoke Maemo's stylus keyboard when a text field is tapped. It also means a chroot app can open an e-mail attachment from Modest.
• Chroot: This is the primary purpose of all of these scripts, and in the end, it is one of the most simple and straightforward parts. The qchroot script makes sure that exiting the chroot, however that happens, resets things gracefully as possible, but the actual chroot is a simple one line command. It really is the mounting and the binding that make the chroot a workable virtual environment.
  

userchroot /media/mmc1/ubuntu-ooo.img.ext2 /opt oowriter "/home/user/MyDocs/resume.doc"

• /etc/hosts
  
• /etc/resolv.conf
• /etc/group
• /etc/passwd
• /etc/localtime
• /usr/share/X11/xkb

8 0

• Mer is based on Ubuntu Jaunty, which is my current distro of choice, mainly because it has the newest Open Java6 JDK.
• The Mer developers have clearly been working to slim down the big Ubuntu footprint; consequently, the image is much smaller than a comparable Jaunty image.
  
• The Hildon Input Method works automatically with GTK apps; this means the stylus keyboard pops up when I tap an input field in a GTK app.
• Midori, a great little GTK WebKit-based browser, comes bundled. Not only that, but they've managed to get some Hildonization done by the developer!

Prism running a simple demo Java applet

• Fennec doesn't do Flash (even though it sees the plugin, it doesn't actually show the Flash) and it is somewhat unstable. I can't select text; if I drag, it just drags the page. If I double click, it zooms.
  
• Abiword works, and it uses Hildon Input Method. It seems to have problems loading files, however, often opening an empty "Untitled" file instead of the chosen document. It also is a bit wobbly; it crashed once on me.
• I can make the stylus keyboard pop up in most Mer apps (where it doesn't pop up by itself) by pressing the centre d-pad key.

• Edit /home/user/.gtkrc-2.0 and comment out any theme-related lines. Add the following line:

include "/usr/share/themes/liberty/gtk-2.0/gtkrc"

• Start the sapwood theme server inside the chroot (as user, not root). I have no idea why it doesn't share the running sapwood server in Maemo; probably Nokia's version is proprietary somehow.

/usr/lib/sapwood/sapwood-server &

12 0