ftp://ftp.redhat.com/pub/redhat/redhat-7.1/powertools/i386/RedHat/RPMS/ xv-3.10a-23.i386.rpm Do you want to download these (Photo web hosting)
ftp://ftp.redhat.com/pub/redhat/redhat-7.1/powertools/i386/RedHat/RPMS/ xv-3.10a-23.i386.rpm Do you want to download these files to /tmp? [Y/n/a/i] ? : Y After you type Y, the software package is downloaded to your current directory (in this case, /tmp). You can then use the rpm -i /tmp/xv* command to install the package. (Replace the /tmp/xv* with the name of the package you are installing.) Note I particularly recommend using the rpmfind command to get software packages that were part of the Red Hat Linux PowerTools that was discontinued for Red Hat Linux 7.2. Those packages are not included with this book, though several previous PowerTools packages (such as xv) are referenced in this book. Understanding package names and formats You just downloaded a massive file from the Internet that contains lots of names, numbers, dots, gzs, and tars. What does all that stuff mean? Well, when you break it down, it s really not that complicated. Most of the names of archive files containing Linux applications follow the GNU-style package-naming conventions. The following example illustrates the package-naming format: mycoolapp-4.2.3.i386.rpm mycoolapp-4.2.3.tar.gz mycoolapp-4.2.3.src.tar.gz mycoolapp-4.2.3.bin.SPARC.tar.gz mycoolapp-4.2.3.bin.ELF.static.tar.gz These examples represent several different packages of the same software application. The name of this package is mycoolapp. Following the package name is a set of numbers that represent the version of the package. In this case, it is version 4.2.3 (the major version number is 4, followed by minor version number and patch level 2.3). After the version number is a dot, followed by some optional parts, which are followed by indications of how the file is archived and compressed. The first line shows a package that is in Red Hat Package Manager (.rpm) format. The .i386 before the .rpm indicates that the package contains binaries that are built to run Intel i386 architecture computers (in other words, PCs). See the sidebar “RPM versus Building from Source” for the pros and cons of using prebuilt RPM binary packages as opposed to compiling the program yourself. RPM versus Building from Source Binaries created in RPM format are easily installed, managed, and uninstalled using Red Hat tools. This is the recommended installation method for Red Hat Linux novices. Sometimes, however, building an application from source code may be preferable. Here are some arguments on both sides: RPM Installing applications from an RPM archive is easy. After the application is installed, there are both shell commands and GUIs for managing, verifying, updating, and removing the RPM application. You don t need to know anything about Makefiles or compilers. When you install an RPM package, RPM tools even check to make sure that other packages that the package depends on are installed. Because Red Hat has released RPM under the GNU, other Linux distributions have begun using it to distribute their software. Thus, most Linux applications are, or will be, available in RPM format.
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.