First, load the Aibohack 'burn3' image.

Next, untar this .tgz onto your Zipit's /tmp.

readme.txt         This file
rootfs.gz          Goes onto /dev/mtdblock3 (actual rootfs)
opt.cramfs         Goes onto /dev/mtdblock4 (/opt)
userprefs.cramfs   Goes onto /dev/mtdblock5 (your 64K of r/w preferences)

S10mtd_rwdev       Script to load all the appropriate modules

modules/           Said modules

Basic steps to reflash with my root/opt fs:

#0   verify that /dev/mtdblock* look like the following:

brw-r-----    1 root     root      31,   0 May 19 16:11 /dev/mtdblock0
brw-r-----    1 root     root      31,   1 May 19 16:11 /dev/mtdblock1
brw-r-----    1 root     root      31,   2 May 19 16:11 /dev/mtdblock2
brw-r-----    1 root     root      31,   3 May 19 16:11 /dev/mtdblock3
brw-r-----    1 root     root      31,   4 May 19 16:11 /dev/mtdblock4
brw-r-----    1 root     root      31,   5 May 19 16:11 /dev/mtdblock5


#1   Copy all the above files over to your Zipit's /tmp (don't flash from NFS
:-)
#2   cd /tmp; ./S10mtd_rwdev
#3   rmmod physmap
#4   insmod modules/maps/readwrite_rescue/danger_physmap.o
#5   dd if=rootfs.gz of=/dev/mtdblock3
     dd if=opt.cramfs of=/dev/mtdblock4
     dd if=userprefs.cramfs of=/dev/mtdblock5

#6   sync
#7   reboot, pray


To minimize use of the /dev/mtdblock5 flash circuitry, I've used
cramfs for the preferences stuff.  To modify, just mount, copy over
to a writeable area, "mkcramfs", and dd back onto /dev/mtdblock5.
You can mount that FS to make sure you got it right before the next reboot.

You'll probably need to edit the /etc/init.d scripts so that
your wireless settings are appropriate for your house....

If you screw something up, hold down the lid-closed switch during bootup,
which halts the process prior to mounting /opt (/dev/mtdblock4), and
drops you into a shell where you can repair things.