I have duplicated the contents of /etc/system/enum in an image filesystem.  I created these directories in systembuilder
...

/etc 
/etc/system
/etc/system/enum 
/etc/system/enum/devices
/etc/system/enum/devices/usb 
/etc/system/enum/include 

and populated them with files exactly as the distribution.

/etc/system/trap is linked to /dev/shmem (so its writeable)

Yet starting enum-devices always fails to mount the usbstick.

BUT if I link /etc/system/enum to a copy of the files on a mounted harddrive, using

ln -sP /fs/etc/system/enum /etc/system/enum

NOW enum-devices works perfectly...  with only this one change. 


The difference appears to be the underlying filesystem.  Looking at "snoopy" output shows that enum processing (on the 
proc filesystem) fails to traverse the directories it opens... unlike when located on the real filesystem.

Is this a known issue (limitation) that /etc/system/enum must be located on a r/w filesystem?  I notice that qnx-car 
always locates /etc on a filesystem other than the image...