I have a question about the Zaurus Developer Image version 1.6 package published by Anton Maslovsky on the Embedded Linux Software Index (www.elsix.org) back in 2005.

The setup scripts call for both a mount point for the image squashfs file and a symbolic link to the mount point at /home/zaurus/develop. Then additional symbolic links are created in the standard file hierarchy (/usr/bin, /usr/lib, /usr/local/include, etc.) to the various compilers, libraries, and tools in the image, all referencing the link /home/zaurus/develop. Why is the link /home/zaurus/develop necessary? Couldn't all the compiler, library, and tool links reference the squashfs mount point directly?

Thanks! Space on SD-card or CF-card is a lot cheaper than in former times. I'll try to extract the dev-image on a desktop linux with squashfs-support (e.g. with Slax or Puppy LiveCD) and transfer the files on a SD card for the Zaurus.

Thanks! Space on SD-card or CF-card is a lot cheaper than in former times. I'll try to extract the dev-image on a desktop linux with squashfs-support (e.g. with Slax or Puppy LiveCD) and transfer the files on a SD card for the Zaurus.

That is a great idea, & here's one better: Repack the uncompressed image files in cramfs format, which is supported by default at least in Sharp's C860 ROM. Developer Image version 1.5 was provided in cramfs format, though that package has long since disappeared from the Internet.