C/sclient, server yum repository the Yum Warehouse file service, can be the following types Ftpwebfileyum have their own client clients, the configuration file must specify the location of the Yum Warehouse, the name, Called Yum access path  -RPM packet storage location-metadata file ctreaterepo mount system disk Mount-r/dev/cdrom/media/cdrom/media/cdrom/ The Repodata directory exists under server in the configuration file of the Yum repository Html:hypertext Mark languagexml:extended Mark Language xml,json: Semi-structured data (Transfer data between different systems, Interface!!) ) primary.xml.gz list dependencies for all RPM packages each RPM installation generates a list of files filelists.xml.gz all RPM packages in the current warehouse other.xml.gz additional information, the RPM change log repomd.xml recorded when the above three files Inter-rubbing and checksum yum install ZSH COMPS*.XML:RPM packet grouping information ftp://172.16.0.1/pub/{Server,VT,Cluster} configuration file in/ etc/yum.conf How to define the name of the repo file format [repo_id] container name=description explain the meaning of the container baseurl= the actual address of the container three formats ftp://http://file:/// enabled=0|1gpgcheck= {1|0} verifies the integrity and source of the Yum package gpgkey= yum [option] [command] [packages] list: list Allavailbale:clean; Clear Cache Repolist Display repo list and brief information allenabledisable------------------------------------------------------------install: Installing yum installed Package_nameupdate: Update update_to upgrade to specified version remove | Erase: Uninstalling info; provides| Whatprovides: View the specified file yum provides yum grouplist View the installed package group Groupinfogroupinstallgroupremovegroupdate 1. Creating a yum REPOCREATEREPO/PATH/TO/2.CP comps-rhe15-vt.xml creating a group repo createrepo-g/root/comps-rhe15-vt.xml/yum/xxx
RPM Installation: Binary format: Source program--"compile--" binary format RPM package version will lag behind with the source package, and even many, bind-9.8.7,bind-9.7.2 customization: Manually Compile and install the compilation environment, development environment Development Library, development tools linux:c,gnu:cg+ +: Make: Project management tools C and C + + Mkefile; Defines the order in which GCC compiles source program C environment in source program file, C++,perl,java,python automake,--"makefile.inautoconf,-- > Configure optional features are combined with makefile.in through scripting. Build makefile and then use make install for the three-step premise of installing a compiled installation: preparing the Development Environment (compilation environment) development tools and development libraries installing development tools and development libraries
- #tar
- #cd
- #./configure
- --help
- --perfixr=/path/to/somewhere Software Installation path
- --sysconfdir=/path/to/conffile_path specifying the configuration file path
- Features: 1. Let the user select the compilation features: 2. Check the compilation environment
- #make
- #make Install
Tar XF tengine-1.4.2.tar.gzcd tengine-1.4.2./configure--prefix=/usr/local/tengine--conf--path=/etc/tengine/ Tengine.conf #--without-http_rewrrrite ignore the module make manual installation cannot be quickly uninstalled, all must have a specific path made Install#user/local/tengine/sbin/nginx
Linux Package Management front end tool Yum
