Unix/linux System Management Technical manual Read (ix)

2016.8.31 10:00-10:30

1.12 WAYS to FIND and INSTALL software

Chapter, software Installation and Management, addresses software provisioning in detail. But for the impatient, here's a quick primer on how to find out what's installed on your system and how to obtain and inst All new software.

1.12 Ways to find and install software

The 12th chapter describes the knowledge of software in detail. But for impatient readers, this section is a beginner-level textbook that teaches readers how to know what software has been installed on their systems and how to get and install new software.

Modern operating systems divide their contents into packages the can be installed independently of one another. The default installation includes a range of starter packages that's can expand according to your needs.

The modern operating system divides itself into multiple software packages, which can be installed individually. The default installation includes only a range of starter packages that users can expand as needed.

Add-on software is often provided in the form of precompiled packages as well, although the degree to which this is a main Stream approach varies widely among systems. Most software are developed by independent groups that release the software in the form of source code. Package repositories then pick up the source code, compile it appropriately for the conventions in use on the systems they Serve, and package the resulting binaries. It ' s usually easier to install a systemspecific binary package than to fetch and compile the original source code. However, Packagers is sometimes a release or both behind the current version.

add-ons are often provided in pre-compiled packages, which is a mainstream approach, where the difference between systems is simply the difference between programs. Most of the software is developed by a separate team and published in the form of source code. Next, the software library collects the source code, compiles it according to the usage habits of the system it serves, and then compiles the results into a package. It is often easier to install binary packages for a particular system than to obtain and compile the original source code. However, packaging software is sometimes one or two version numbers behind the current version.

The fact that both systems use the same package format doesn ' t necessarily mean this packages for the both systems are inter Changeable. Red Hat and SUSE both use RPM, for example, but their filesystem layouts is somewhat different. It's best to use packages designed for your particular system if they is available.

two systems using the same software packaging system does not necessarily mean that the packages of the two systems can be used interchangeably. For example, both Red hat and SuSE use RPM, but their file system layouts are slightly different. It's best to use them if you can find packages that are designed for your system.

Major Linux distributions provide excellent package management systems this include tools for accessing and searching Inte Rnet software repositories. Distributors aggressively maintain these repositories on behalf of the community, so there are rarely a need for Linux Admi Nistrators to step outside the bounds of their systems ' default Package Manager. Life is good.

Mainstream Linux distributions provide an excellent package management system that includes tools to access and search the software library on the Internet. Publishers actively maintain these repositories for the community, so Linux system administrators rarely need to jump out of the default Package manager on their systems. Life is so beautiful.

UNIX Systems show more ambivalence about the package management. Solaris, HPUX, and AIX all provide packaging software this works at the level of individual machines. However, the vendors of these systems don ' t maintain repositories of open source software, so the user communities is MOS Tly left-to-fend for themselves.9 Unfortunately, one of the main pieces of glue that holds a packaging universe together I S A-on-packages to reliably refer-to-packages in order to express dependency or compatibility information. Without some central coordination, the whole ecosystem can quickly fall apart.

UNIX systems look daunting in terms of package management. Both Solaris, HP-UX, and AIX provide packaged software that is used on a single machine level. However, the vendors of these systems do not maintain open-source repositories, and most of the user base is self-sustaining. Unfortunately, one of the links that sustains a packaged software environment is a way for software packages to reliably retrieve additional packages to gain information on dependencies and compatibility. Without some sort of center as a coordination, the whole system will soon fall apart.

This article is from the "Zhao Dongwei blog" blog, make sure to keep this source http://zhaodongwei.blog.51cto.com/4233742/1844628

Unix/linux System Management Technical manual Read (ix)