Is this functional?

[JesseCake]

I'm not sure if this is functional on a Chumby Classic? Has it been tested and confirmed?

On boot up I get an error about the file system being read only, and after I type in my wifi details it says it cannot connect to chumby.com

I guess I'm a little confused about the process also - does this modify the onboard chumby firmware or do I leave the USB stick in it and it'll run of it?

I've scanned and checked the USB drive multiple times to make sure it's not needing repair to the FAT32 filesystem onboard, and have reformatted also. Are there problems with the system not mounting the USB drive as readable? Or is there an error in the script?

[francistheodorecatte]

Sorry I missed this, Github has become awful selective about sending me notifications... Feel free to open PR's.

As for the firmware, it's somewhat functional on the Chumby Classic, at least it works enough to boot on mine IIRC. I'll have to dust it off and try out your fork, it's obviously been a while if you look at my commit history...

Also, try using as small of a USB drive as possible; I had the best luck with <2GB ones.

[francistheodorecatte]

Also, the newer versions of Zurk's Offline Firmware made heavy use of symbolic linking, which FAT32 very obviously does not support. I'm fairly sure that's the stumbling block I hit. For everything to work properly, it'd probably be best to rebase on the unmodified latest version of Zurk's Offline Firmware, cherry pick fixes from this repo (and yours), and create an EXT3 filesystem image to flash with Etcher or similar.