The difference between centos6 and 7
1. Evolution of system initialization technology - boot process
CentOS 6: Adopting INIT technology, the entire boot process is self-checking BIOS - MBR boot - GRUB loads - loads the kernel - starts the INIT process - reads the INITTAB configuration file and starts the process services in order according to the mode specified in the configuration file. INIT technology makes the startup process very clear and relies on SHELL scripts. Because the processes are started one by one in sequence, the speed is slow and the system startup may be affected because a certain service is stuck.
CentOS 7: Using systemd technology. This is a new technology that replaces INIT. It uses a parallel method to start the process, so the startup speed is faster, and it is compatible with INIT commands to reduce migration costs.
PS: You can know the technology used by the current system by viewing the process with PID 1 through the ps command.
(Recommended tutorial: centos usage tutorial)
2. Changes in network setting methods
The familiar ipconfig in CentOS 6 is used in CentOS 7 was replaced by the ip command; the graphical network configuration tool nmtui replaced setup
3. Host name and character set
In CentOS 6, you can modify the host name by editing /etc/ sysconfig/network file, but this method has been abandoned in CentOS 7, and the /etc/hostname file is used. The method of temporarily modifying the host name remains unchanged, and the hostname command is still used. And a new hostname management tool hostnamectl has been added to CentOS 7 (the file name modifications made by this tool are permanent).
For the modification of the character set, CentOS 7 uses the new configuration file /etc/locale.conf to replace /etc/sysconfig/i18n. If you want to temporarily modify the character set, the method remains the same, modify the LANG variable, such as LANG=zh_CN.UTF-8. A new character set management tool, localectl, has the same effect as hostnamectl.
4. Compatible with /etc/rc.local
The /etc/rc.local file records commands that need to be automatically executed after booting. Although this file has been abandoned in CentOS 7, However, it can also be used with compatibility. You only need to give the file executable permissions:
chmod +x /etc/rc.d/rc.local
5. The difference between runlevels
The /etc/inittab file in CentOS 6 is based on init technology. , so naturally it cannot be used in CentOS 7, but the file is still retained, but the content has been replaced with boot content to let users know how to switch run levels now. Since this is not commonly used, I will not continue to describe it.
6. Service Management
This is the most unpleasant modification for users. It adds the systemctl tool and integrates the functions of service and chkconfig commands. See the figure for specific usage:
Related video tutorial sharing: linux video tutorial
The above is the detailed content of The difference between centos6 and 7. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Backup and Recovery Policy of GitLab under CentOS System In order to ensure data security and recoverability, GitLab on CentOS provides a variety of backup methods. This article will introduce several common backup methods, configuration parameters and recovery processes in detail to help you establish a complete GitLab backup and recovery strategy. 1. Manual backup Use the gitlab-rakegitlab:backup:create command to execute manual backup. This command backs up key information such as GitLab repository, database, users, user groups, keys, and permissions. The default backup file is stored in the /var/opt/gitlab/backups directory. You can modify /etc/gitlab

Improve HDFS performance on CentOS: A comprehensive optimization guide to optimize HDFS (Hadoop distributed file system) on CentOS requires comprehensive consideration of hardware, system configuration and network settings. This article provides a series of optimization strategies to help you improve HDFS performance. 1. Hardware upgrade and selection resource expansion: Increase the CPU, memory and storage capacity of the server as much as possible. High-performance hardware: adopts high-performance network cards and switches to improve network throughput. 2. System configuration fine-tuning kernel parameter adjustment: Modify /etc/sysctl.conf file to optimize kernel parameters such as TCP connection number, file handle number and memory management. For example, adjust TCP connection status and buffer size

The CentOS shutdown command is shutdown, and the syntax is shutdown [Options] Time [Information]. Options include: -h Stop the system immediately; -P Turn off the power after shutdown; -r restart; -t Waiting time. Times can be specified as immediate (now), minutes ( minutes), or a specific time (hh:mm). Added information can be displayed in system messages.

CentOS will be shut down in 2024 because its upstream distribution, RHEL 8, has been shut down. This shutdown will affect the CentOS 8 system, preventing it from continuing to receive updates. Users should plan for migration, and recommended options include CentOS Stream, AlmaLinux, and Rocky Linux to keep the system safe and stable.

The key to installing MySQL elegantly is to add the official MySQL repository. The specific steps are as follows: Download the MySQL official GPG key to prevent phishing attacks. Add MySQL repository file: rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm Update yum repository cache: yum update installation MySQL: yum install mysql-server startup MySQL service: systemctl start mysqld set up booting

Complete Guide to Checking HDFS Configuration in CentOS Systems This article will guide you how to effectively check the configuration and running status of HDFS on CentOS systems. The following steps will help you fully understand the setup and operation of HDFS. Verify Hadoop environment variable: First, make sure the Hadoop environment variable is set correctly. In the terminal, execute the following command to verify that Hadoop is installed and configured correctly: hadoopversion Check HDFS configuration file: The core configuration file of HDFS is located in the /etc/hadoop/conf/ directory, where core-site.xml and hdfs-site.xml are crucial. use

Building a Hadoop Distributed File System (HDFS) on a CentOS system requires multiple steps. This article provides a brief configuration guide. 1. Prepare to install JDK in the early stage: Install JavaDevelopmentKit (JDK) on all nodes, and the version must be compatible with Hadoop. The installation package can be downloaded from the Oracle official website. Environment variable configuration: Edit /etc/profile file, set Java and Hadoop environment variables, so that the system can find the installation path of JDK and Hadoop. 2. Security configuration: SSH password-free login to generate SSH key: Use the ssh-keygen command on each node

Common problems and solutions for Hadoop Distributed File System (HDFS) configuration under CentOS When building a HadoopHDFS cluster on CentOS, some common misconfigurations may lead to performance degradation, data loss and even the cluster cannot start. This article summarizes these common problems and their solutions to help you avoid these pitfalls and ensure the stability and efficient operation of your HDFS cluster. Rack-aware configuration error: Problem: Rack-aware information is not configured correctly, resulting in uneven distribution of data block replicas and increasing network load. Solution: Double check the rack-aware configuration in the hdfs-site.xml file and use hdfsdfsadmin-printTopo
