How do I find install files in http://download.ni.com/ for cRIO-9033?

[tpc1095]

I have a cRIO-9033 which is not connected to the Internet.  I need to "opkg install openssl" on it.

I can scp files onto it after which Ishould be able to "opkg install /path/to/file" . I am guessing that the installable files (.ipk ?) can be found somewhere in "http://download.ni.com/".

How do I identify which file to download? Is there a command that tells you where a related package was downloaded from?

Tim

[BradM]

Do you need the development files (headers, .so symlink for linking purposes) for openssl, or do you need some of the tools that come in the openssl package? I ask since the openssl library is already on the controller (for other programs like ssh)

But, to answer your actual question, the software package feeds are at http://download.ni.com/ni-linux-rt/feeds/. I just want to check to make sure that you're not doing extra work for something that's already there...

[tpc1095]

I want to handle the case where someone might enter "opkg remove openssl" expecting to be able to immediately "opgk install openssl" but didn't anticipate that the Internet connection that was supposedly working was not.

In general, our team  needs to be able to "opkg install" but there is no Internet connection where the 9033s are mounted.

I see there is a 2014/x64 and also a 2015/x64 directory, and going down both there is core2-64 and also x64. I don't see openssl in either of these four possible locations. (2014/2015 and core2-64/x64).

How would one identify the specific file opkg wants so as to scp it over and install it?

[BradM]

For 2014: http://download.ni.com/ni-linux-rt/feeds/2014/x64/x86_64/openssl_1.0.1e-r15.1_x86_64.ipk

For 2015: http://download.ni.com/ni-linux-rt/feeds/2015/x64/ipk/core2-64/openssl_1.0.1m-r0.48_core2-64.ipk

Once you get the appropriate .ipk, scp/filezilla/webdav the .ipk over to the target and, from a console logged in as admin, opkg install /path/to/openssl...ipk.

[tpc1095]

OK, I can see a pattern.

For a recent cRIO-9033 would it be reasonable to assume I'd only look in 2015? Or would I also look in 2014 if I couldn't find something?

[BradM · Accepted solution]

It is advisable to install from the feed from your particular software stack (e.g. check the configuration of /etc/opkg/*.conf files to see where they point).

If you cannot find something in the matching feed, report it so we are aware that there is interest in a particular package and, in the meantime, you can try to install the package (if it exists) from another feed.

Be sure to back up the state of the controller if you need to install from a feed other than the configured feed as this has not been thoroughly tested and it is possible you will need to format your target. You may need to work around bogus package version dependencies (e.g. package A claims that it depends on package libB >= 1.2, you have libB 1.1.0, there's a reasonable chance that A will be perfectly happy with libB 1.1.0)

[tpc1095]

I am seeing some errors that makes me think that opkg is still depending on an Internet connection.

opkg install /home/admin/downloads/openssh_6.6p1-r0.5.125_core2-64.ipk

Installing openssh (6.1p1-r0) to root...

Downloading http://download.ni.com/ni-linux-rt/feeds/2014/x64/x86_64/openssh_6.1p1-r0_x86_64.ipk.

wget: bad address 'download.ni.com'

Collected errors:

* opkg_download: Failed to download http://download.ni.com/ni-linux-rt/feeds/2014/x64/x86_64/openssh_6.1p1-r0_x86_64.ipk, wget returned 1.

* opkg_install_pkg: Failed to download openssh. Perhaps you need to run 'opkg update'?

* opkg_install_cmd: Cannot install package openssh.

Instead of a file name, should I be using " --offline-root /home/admin/downloads" ?

[BradM]

Something odd is going on with your installation: you're attempting to install the 2015 openssh, it's attempting to download the 2014 openssh on installation. I have a feeling that you're working with a 2014 image. Not that this should be causing an issue, but I'm just trying to figure out how the cross-over is happening...

[tpc1095]

Sorry, I changed the example to openssh. This is a long story.

I thought that if I gave opkg a leading / (slash) it would understand to use the file it was given and stay off the network. I suppose not.

Perhaps I should try the 2014 file first?

[BradM]

No, in my experiences, your expectations (/some/path/to/package.ipk does not require a network connection, use the file presented) are sane, and I've seen it behave the way that you would expect it to. I would be likewise bewildered to see the behavior that you're seeing, but right now I just don't have the time to look into it further...