I am sure there is a good explanation for this, but I
can’t quite envision what it might be 
Why do the executable files in /proc/boot disappear
after they are executed the first time ?
I have gotten around the problem right now by placing
devb-ram in my image, and “cp’ing” the contents of
/proc/boot to /ram and then executing the programs
from there (this works perfectly).
This on 6.2.1 with a custom BSP on an arm720t core.
Everything else appears to work fabulously…
Rennie
Brian Stecher wrote:
Read the mkifs documentation sections on the code=? and data=? attributes
and “Notes on XIP versus copy”.
I had read that section but “prevents running” just didn’t jump out at me
as unlink, but it makes perfect sense.
Short answer: the default data=uip attribute doesn’t allow executables
to be run more than once since the only copy of the R/W data is damaged
by the first execution.
I suspected there was a good reason.
Thanks, Rennie
Rennie Allen <rallen@csical.com> wrote:
I am sure there is a good explanation for this, but I
can’t quite envision what it might be >Why do the executable files in /proc/boot disappear
after they are executed the first time ?
Read the mkifs documentation sections on the code=? and data=? attributes
and “Notes on XIP versus copy”.
Short answer: the default data=uip attribute doesn’t allow executables
to be run more than once since the only copy of the R/W data is damaged
by the first execution.
–
Brian Stecher (bstecher@qnx.com) QNX Software Systems, Ltd.
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8