> You won't see anything from preinit with set -x because when preinit is > first called there is no stdin/stdout.
Ah, I didn't think of that! > >> >> I didn't think about running wireshark to capture the script output >> ... I'll have to look into that. I'm well versed in wireshark. >> >> What is this 'pure' /jffs envrionment? Is it possible to setup the >> union so that 'any' file can be modified? That is kind of what I was >> expecting to have but I realize some of the preinit stuff has to run >> from squashfs because the union isn't established that early in the >> startup. >> > > No not pure /jffs - that's just the mountpoint when using a jffs2 > overlay over the squashfs. It is possible to build/flash images that > don't have a squashfs at all, and which store everything on a jffs2 > filesystem (no overlay). This images are larger than the squashfs > images so you may not have enough flash memory for one of them. Ah, yes. I started off with a all JFFS2 partition but switched to squashfs for speed/performance issues. I still need persistence so I back ported mini_fo to my kernel and am trying to learn the preinit scripts to understand how the squashfs & jffs2 filesystems are manipulated and then combined. I had hoped that it was possible to create the union in such a way that the startup scrips in squashfs rootfs could be modified and the version in /jffs used but that might not be possible. I'm not real experienced on the finer points of using a union fs in a embedded environment yet. I thought that it might be possible to set the union up so that any file in the squashfs could be edited. That may be true but in the case of the startup scripts ... the /jffs version might not be used as the union isn't setup yet. These limits are the kind of things I'm trying to figure out. Regards, Brian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
