android-root/system and android-root/data have no problem as symbolic links from / to android-root. In /etc, only hosts file could be an issue, so keep Angstrom's hosts file. Other than it just spill them over.
$ ssh root@zaurusNow I might be able to boot Android up with just two commands.
# cd /
# ln -s /home/root/android-root/system system
# ln -s /home/root/android-root/data data
# cd /home/root/android-root/etc
# cp /etc/hosts .
# tar cvf /tmp/etc.tar .
# cd /etc
# tar xvf /tmp/etc.tar
# chmod 666 /dev/binderGee. I ended up looking at famous red cylon forever. From PC's another shell, I logged in to Zaurus to see the binder's permission.
# android-root/init
$ ssh root@zaurusIt seems to me that android-root/init re-constructs /dev with udev stuff.
# ls -l /dev/binder
crw-rw---- 1 root root 252, 0 Jan 18 02:58 /dev/binder
After I rebooted my Zaurus, I brought two ssh consoles connected to my Zaurus, so that I could check the binder's permission while booting Android up.
# chmod 666 /dev/binderThe permission had changed.
# android-root/init
--- from the second console ---
# ls -l /dev/binder
crw-rw---- 1 root root 252, 0 Jan 18 02:58 /dev/binder
After a couple of try-and-errors, I found Android can be booted up by chmod the binder before Android switches to grapfical mode.
I revised start-android.sh.
#!/system/bin/shOK. I get Android up without chroot.
chmod 666 /dev/binder
android-root/init &
sleep 1
chmod 666 /dev/binder
/system/bin/sh
By the way, Angstrom mounts 30MB tmpfs on /media/ram. Now I can move /tmp from HDD to RAM.
Reboot again, then symlink /var/tmp to /media/ram.
$ ssh root@zaurusAfter I boot Android up, I see less HDD LED brinking than /tmp on HDD.
# cd /var
# rm tmp
# ln -s /media/ram tmp
I expected more performance improvement by moving /tmp out to RAM, but it doesn't change much.
I'll play with this Android Zaurus for a while.
Cheers,
android-root/systemとandroid/dataをルートに持っていって、chrootなしでブートできますた。initしてから1秒寝て再度chmod 666 binderするのがキモ。
ついでに/tmpをRAMに追い出しました。HDDのLED点滅は減ったけど、あまりパフォーマンスは変わらないかも。