Calling opkg from the System Exec VI?

[ASLindeman]

This relates to my previous question:https://decibel.ni.com/content/thread/43548?tstart=0. I'm working with a large number of remote systems, and the logic behind building an ipk containing a source distribution was so that I could set the systems up to do updates on their own, most likely by adding a repository, and then checking for updates through a scheduled "opkg update" command sent from the System Exec VI. However, at this point in time, I can't get the System Exec VI to even install the ipk. Whenever I try to make the call, I get the response "Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: Permission denied." from the standard output. I've tried prefixing it with su, but then I get the standard error "su: must be run from a terminal". After that, I tried changing the access permissions on var/lib/opkg, and got the response "chmod: opkg: Operation not permitted". Is there any way to access these admin-level programs and permissions from LabVIEW code on the RT target?

[BradM]

For the move to NI Linux RT, NI tried to make sure that LabVIEW code would not have undue supreme power over the controller as it's far too easy to foul up the software when such power is wielded. Most folks who need this sort of ability will install sudo and configure it to have limited command support (e.g. only allow lvuser to run opkg) and configure sudo to work without password. You will need to configure sudo to allow lvuser to use it, preferably through visudo. See: http://linux.die.net/man/8/sudo