TFTP CLIENT RPM INSTALL
It is recommended that you run this script from the /mnt/fastpath directory.įor example, to install Puppet from the HTTP server at 10.27.9.99 where the RPMs are installed in /var/www/html/repo/brl/3.8: The script also takes parameters for the TFTP/HTTP path and TFTP/HTTP server IP address. For example, you could install all RPMs required for Python, or all RPMS required for the Chef client, or just all available RPMs. Use the -h option to display the commands available. It is automatically installed as part of the bootstrap RPM tar ball. Once extracted, see the rpms.-/output/RPMS directory for binaries and rpms.-/output/SRPMS for source code.įor installing further RPMs you can use the rpm-install.sh utility script that is shipped with the RPMs.
A number of RPMs are provided in the rpms.-.tgz file. Once the RPM system has been installed onto the switch, rpm can then be used as normal to install additional packages.
Installing RPM bootstrap files (this can take 10-15 minutes): mnt/ # wget or tftp -g -r bootstrap-rpm.brl_3.6a.iproc.1.0.1.7.sh It is recommended that wget is used to fetch the bootstrap-rpm file since the file is large and tftp may time out. This is the file that needs to be copied and installed on the switch, as shown below. Step into that folder and step into the output directory. Uncompress and extract this file on your host Linux machine. The RPMs are delivered as a compressed tar ball in the rpms.-.tar.bz2 file. This is the process of installing RPM and its dependencies without actually using RPM, but doing so in a way that creates the initial RPM database. The ".1" portion of "4.2.1-7.1" indicates the Broadcom package revision, "brl_3.6a" indicates the Broadcom tool chain version and "iproc" indicates the processor family. For example, sed-4.2. from CentOS is cross compiled and repackaged as sed-4.2.1-7.1.el6.brl_3.6a.iproc.rpm. These source RPMs have been cross compiled and then repackaged.
The Broadcom Linux RPMs are based on the source RPMs from the CentOS 6.2 release. Note that /mnt/fastpath/usr/bin is on the default search path for binaries. This location is persistent across reboots and across upgrades of the OF-DPA switch. The RPM system and subsequent packages are installed into /mnt/fastpath/usr. You must then install the other RPMs using the rpm command. In order to use RPM you must first bootstrap the RPM framework so that the rpm binary is available.
TFTP CLIENT RPM SOFTWARE
Customer applications and other open source software can be installed and maintained on an OF-DPA switch using the RPM Package Management System.
0 kommentar(er)
