[Motorola Atrix 2] ShotSkydiver:
Okay, here's my entire experience with this.

As of now, I have my 16GB sdcard partitioned with a 6GB ext3 partition (done with Linux + gparted). After starting from a fresh stock 2.3.6 system, I ran the webtop_unlock script per the original post (it basically just looks for your ext3 partition, mounts it to a temp folder, copies the /osh folder to that ext3 partition, unmounts it, copies over scripts to mount the ext3 partition at boot, removes Motorola's folder that prevents custom commands, and finally mounts the ext3 as /osh).

For me personally, the mountosh scripts have never worked. So, what I did was check which block it was mounted on.

fdisk -l /dev/block/mmcblk0 | grep Linux | awk '{print $1}' | head -1

Mine was mounted at /dev/block/mmcblk0p2, so I mounted that to the /osh folder.

mount -t ext3 /dev/block/mmcblk0p2 /osh

To verify it was actually mounted correctly, I ran the command 'busybox df -h' to get a listing of each folder in my root and where it was mounted.

This shows that my /osh folder has 6GB of space, so I know it's mounted correctly. At every reboot, the command to mount the ext3 partition has to be run. To make my life easier, I just used ROM Toolbox to create a custom script with that command, set to run automatically at boot (In addition to that, I also have two other scripts set to run at boot, one to mount system read/write and one to overclock to 1.2Ghz).

Now I'm going to plug it into my lapdock and press the key combination to open the gnome-terminal (Ctrl+Alt+T). Then, you could either use the command-line apt-get or the GUI synaptic to install and update the necessary packages. If you're at all familiar with Ubuntu, this should be fairly simple. Run an apt-get update or just open synaptic with 'gksu synaptic'. I'd recommend using synaptic in this case, as it lets you visually browse available packages. From there, it's as simple as installing a desktop environment and its necessary dependencies. I'm using xfce4 as my desktop; alternatively you could use GNOME or KDE. I personally recommend using xfce4, as GNOME is significantly more resource-intensive.

I'll assume you've got xfce4. Once you've installed xfce4, I'd run 'sudo apt-get upgrade' to let the system automatically upgrade all of your packages to their latest. And... here's where I started running into errors.

Dbus errors:

Because webtop's ubuntu.sh script (/usr/local/bin) dictates that a specific dbus, udev, and hald be run, upgrading (and simply starting) these processes are a pain. This matters because a lot of errors get thrown if dbus isn't seen as running. To force dbus to run in a way that allows you to proceed, run

sudo rm /var/run/dbus/pid
sudo dbus-daemon --system --nofork

and leave that terminal window open. This should work.

perl locale errors:

Oh god, this one was a nightmare. You'll know if this happens to you. You'll get a bunch of errors about missing locale files, and LC_ALL not being set properly. What I ended up doing was downloading this .deb, manually extracting its contents by running 'dpkg-deb -x name-of-package.deb tmpdir', and dragging/dropping the extracted files into their respective folders (/usr/share/locales). Only drag in the locale folders en_GB and en_US. Then, run a 'sudo dpkg-reconfigure locales' and it should get the locales working properly. You might need to reboot webtop first. Run the command 'locales' to verify that all the fields are filled.

The problem here is that the system's locale is set to the UK (en_GB), so it looks for the en_GB locale when trying to set the en_US locale. I had to set my locale file to en_GB to get it to work.

"No space left on device" errors:

Honestly, I'm not too sure what I did to fix this. It happened to me when running a full upgrade on all of my packages. If you look in the file manager, it reports the root / folder as having 0B of free space, but /osh has plenty of room. I think this happens because in order to emulate a full Linux install, folder links are created in / for all of the folders inside /osh. The package manager sees this and for whatever reason, sometimes reads the / folder as the system, causing it to think there are 0B left on the whole disk. I 'fixed' this by removing a few packages, then attempting to reinstall what I was previously.

Modifying the startup scripts

Now that you've got everything set up (somewhat) properly, you can modify what happens when webtop first starts with the start-oshwt-1.sh and -2 files. The original guide in the first post was written before the latest motorola update, which changed the layouts and contents of both files. Most of the changes you'll want to make are in the oshwt-1 file. (If you use ES File Explorer to edit these files, like I did, make sure to change the file permissions after you save it back to rwx r-x r-x.)

So, here's what's inside my modified oshwt-1.sh, along with my notes explaining what each line does:

#! /bin/sh
### BEGIN INIT INFO
# Provides: start_lxde2.sh
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: started by adas user at login
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=/usr/lib:/usr/local/lib

. /lib/lsb/init-functions
export `fbcp_dsba`

log_action_msg "Will now start OSHWT 1 scripts"

# Start WM
xrandr --auto [B]This tells webtop to auto-detect the display resolution and set it.[/B]
gnome-terminal [B]Here I have the terminal window set to open at boot.[/B]
# update-font.sh [B]This is a motorola script that checks to see if webtop is running with the font Droid Sans at point 10, and if not, set the font to that. Comment this script out if you set a custom font.[/B]
# sfalv -i "metacity -c" [B]This automatically launches the metacity window manager. [I]sfalv[/I] is a custom motorola executable that, when specified with a program, will launch that program and automatically re-launch it every time it is killed.[/B]
# sfalv -i "xfwm4 -c" [B]Here I have the xfce4 window manager set to auto-launch.[/B]

# sfalv -i "awn-autostart" [B]This auto-launches the mobile view.[/B]
# sfalv -i "webtop-panel" [B]This auto-launches the default webtop panel (stock bottom dock and status bar)[/B]

# GNOME Startup
# sfalv -i "gdm" [B]This auto-launches the GNOME window manager.[/B]
# sfalv -i "gnome-panel" [B]This auto-launches the GNOME panel.[/B]
# sfalv -i "gnome-settings-daemon" [B]This auto-launches the GNOME settings daemon, to set user themes.[/B]
# sfalv -i "dbus-daemon --system --nofork" [B]This auto-launches dbus, as detailed in my fix above.[/B]

# XFCE4 Startup
# sfalv -i "xfwm4 -c" [B]Auto-launches xfce4 window manager, as seen above. [/B]
# sfalv -i "xfdesktop" [B]Auto-launches the xfce4 destkop.[/B]
# sfalv -i "xfce4-panel" [B]Auto-launches the xfce4 panel.[/B]
# sfalv -i "xfce4-session" [B]Auto-launches the entire xfce4 session, with negates the use of launching each xfce4 component separately.[/B]

# Cache Firefox files to improve startup times
# [ -x /usr/bin/firefox-readahead ] && /usr/bin/firefox-readahead & [B]As the comment says, this is what auto-launches Firefox with the user's last-opened tabs. I disabled this so it wouldn't open every time.[/B]

# start OSHWT 1 scripts
sfalv -w "webdaemon -d -n" [B]Launches important webtop files.[/B]

sfalv -i "xscreensaver" [B]Launches the webtop screensaver; not sure if this is safe to disable.[/B]

# webtop-wallpaper & [B]Launches the webtop background. Disable this to be able to run xfce4's desktop.[/B]

As of now, I just have my launch script open a terminal window at boot and nothing else, so I can have manual control over what launches. It's pretty self-explanatory to edit. If you want to launch something once, give it it's own line. If you want to keep something running throughout your entire session, run it through sfalv -i.

Here's start-oshwt-2.sh:

#! /bin/sh
### BEGIN INIT INFO
# Provides: start_lxde2.sh
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: started by adas user at login
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=/usr/lib:/usr/local/lib

. /lib/lsb/init-functions
export `fbcp_dsba`

log_action_msg "Will now start OSHWT 2 scripts"

# start OSHWT 2 scripts
# sfalv -i "aiw -d" [B]Launches the actual mobile view process.[/B]
aiw -d
sfalv -i evbridge [B]Launches motorola's bridge for interfacing a connected keyboard/mouse with linux.[/B]

# sfalv -i "docking_manager" [B]I'm pretty sure this launches the picker to choose what to do when connected.[/B]

#sfalv -i "window_switcher"
# window_switcher & [B]Launches motorola's custom alt+tab window switcher.[/B]

sfalv -i "/usr/lib/gvfs/gvfs-gdu-volume-monitor"
print-daemon.sh --start & [B]This is important to keep, as it launches and mounts the phone's filesystem in linux.[/B]

# IKXWEBTOP-5690
setxkbmap 'us(android)' [B]Allows the phone's keystrokes to be detected in linux.[/B]

So, that's how you edit the startup scripts to launch what you want. And that's most of what I've discovered in trying to get this whole thing set up. Right now, I'm trying to figure out how to get webtop launched at the phone's boot as opposed to the phone booting to android first, to dedicate all available processing power to webtop.

More information about webtop and what it does at boot: https://sites.google.com/site/androidnothize/nebtop/webtop