Hi zaoqi,
that's a nice tool! And I certainly recognize some things

I found a small problem, in line seven of the script to start XFCE
https://github.com/zaoqi/kual-linuxd...ce4.user.sh#L7
In this command to find the window size:
Code:
SIZE=$(xwininfo -root -display :0 | egrep "geometry" | cut -d " " -f4)
I run this from within the chroot, as the Kindle OS doesn't have egrep (at least mine, "chroot.xfce4.user.sh: line 7: egrep: not found"). Xephyr then gets confused with its arguments and chokes on the color depth:
Code:
Fatal server error:
(EE) Unrecognized option: 4
Also I found out that the loop devices don't get disassociated automatically when umounting, you can check like this:
Code:
[root@kindle kual-linuxdeploy-armhf]# cat /sys/block/loop*/loop/backing_file
/dev/mmcblk0p4
/mnt/us/extensions/kual-linuxdeploy-armhf/rootfs.img (deleted)
/mnt/us/extensions/kual-linuxdeploy-armhf/rootfs.img
/usr/share/X11/xkb.sqsh
/usr/java/lib/fonts.sqsh
/etc/kdb.src.sqsh
/usr/lib/locale.sqsh
/usr/share/keyboard.sqsh
/opt/var/local.sqsh
/mnt/us/extensions/kual-linuxdeploy-armhf/rootfs.img (deleted)
/mnt/us/extensions/kual-linuxdeploy-armhf/rootfs.img (deleted)
That for me leads to a) running out of loop devices at one point (max 16) b) storage doesn't get freed when deleting the umounted image (df -h). Thus I disassociate it manually:
Code:
LOOPDEV="$(mount | grep loop | grep /tmp/alpine | cut -d" " -f1)"
... umounts ...
losetup -d $LOOPDEV
And a small thing: In my dotfiles I archive dconf dumps now as well. These have to be read in upon initialization as well though, e.g. like this
Code:
dconf load /org/onboard/ < ~/.config/org_onboard.dconf.dump
Just because I saw you install onboard too.. I switchted to Mate now, but currently the XFCE config is also still in the repo, so you can update the version you clone if you want.
Nice work! And your scripts look way more elegant than mine