LabVIEW
Linx on Raspi uses UTC
Solved!
@billko wrote:
I meant "time zone settings".
That's in true Linux manner unfortunately a very flakey way to try to do. Where and how theses settings are stored can depend on many variables, such as Linux version, distribution and other such things. And it is stored in a configuration file that can change based on user configuration values. chroot isolates the guest OS as much as possible from the host OS and only allows very specific access to the host OS. That's the whole idea of chroot, to create a jail-root in which you can run a guest OS and that guest OS has only very restricted access to specific guest OS resources.
You can configure the chroot setup to grant access to specific files and subdirectories but for that you need to know where these resources are and considering that the way these settings are stored can be reconfigured by a user, this is a very flaky path to follow.
@rolfk wrote:
@billko wrote:
I meant "time zone settings".
That's in true Linux manner unfortunately a very flakey way to try to do. Where and how theses settings are stored can depend on many variables, such as Linux version, distribution and other such things. And it is stored in a configuration file that can change based on user configuration values. chroot isolates the guest OS as much as possible from the host OS and only allows very specific access to the host OS. That's the whole idea of chroot, to create a jail-root in which you can run a guest OS and that guest OS has only very restricted access to specific guest OS resources.
You can configure the chroot setup to grant access to specific files and subdirectories but for that you need to know where these resources are and considering that the way these settings are stored can be reconfigured by a user, this is a very flaky path to follow.
Thank you for the explanation. I appreciate your patience.
I believe that for Community Edition, it is the Hobbyist Toolkit, and for any other flavor of LabVIEW it is LINX (which really are exactly the same thing, one is just rebranded (and updated)).
I know that doesn't anwer your question but it was important to get that straightened out right away before you installed the wrong one and maybe completely hose your LabVIEW installation. (Hobbyist Toolkit should automatically install with Community Edition since it is a part of the package.)
Also, start your own topic. This one isn't related to your question and it has already been answered.
Unfortunately that is bad advice. For the Community Edition you do NOT need to install anything as it comes preinstalled with the Hobbyist Toolkit. For LabVIEW Development you need the Linx Toolkit from the VIPM only if is LabVIEW 2019 or earlier. Otherwise you need to install the Hobbyist Toolkit or it will not work!
