mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
translated
This commit is contained in:
geekpi
parent
5921fdb705
commit
3d2c41fdfb
@ -1,90 +0,0 @@
|
||||
[#]: subject: "The systemd Controversy: A Beginner's Guide to Understanding the Debate"
|
||||
[#]: via: "https://itsfoss.com/systemd-init/"
|
||||
[#]: author: "Bill Dyer https://itsfoss.com/author/bill/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
|
||||
The systemd Controversy: A Beginner's Guide to Understanding the Debate
|
||||
======
|
||||
|
||||
In the world of Linux, few debates have stirred as much controversy as the battle between the traditional System V [init][1] system, often known as SysVinit, and the newer [`systemd`][2].
|
||||
|
||||
In this article, I'll briefly discuss what systemd is, what advantages and disadvantages it has over the traditional init systems and why it is controversial.
|
||||
|
||||
### What is systemd?
|
||||
|
||||
systemd is a system and service manager, first introduced in 2010 to replace the traditional System V init system. It was designed to improve boot-up speeds and manage system services more efficiently. Today, `systemd` is the default `init` system for many popular Linux distributions, including Ubuntu, Fedora, and Red Hat Enterprise Linux.
|
||||
|
||||
### Is systemd a Daemon?
|
||||
|
||||
Despite the name, `systemd` is not a daemon. Instead, it's a software suite that provides a number of system components for Linux. Its goal: to standardize service configuration and behavior across Linux distributions.
|
||||
|
||||
The main component of `systemd` is a "system and service manager", which serves as an `init` system to bootstrap user space and manage user processes. It also offers replacements for various daemons and utilities, from device and login management to network connection management and event logging.
|
||||
|
||||
### Key Features of systemd
|
||||
|
||||
`systemd` has many features, such as its ability to aggressively parallelize operations, facilitate the on-demand launching of daemons, monitor processes using Linux control groups, manage mount and automount points, and implement a sophisticated transactional dependency-based service control logic.
|
||||
|
||||
Additionally, `systemd` supports SysV and LSB init scripts, serving as a substitute for SysVinit. It also offers a logging daemon and utilities for managing essential system configurations.
|
||||
|
||||
![systemd on fedora - Courtesy of Wikimedia][3]
|
||||
|
||||
### systemd Vs SysVinit: The Controversy
|
||||
|
||||
The heart of the init vs systemd debate revolves around how best to manage Linux-based systems. Concerns range from complexity and compatibility to the optimal way to manage system services, touching on foundational questions facing system administrators and Linux enthusiasts.
|
||||
|
||||
Critics argue that `systemd` is too complex and monolithic, making it harder to troubleshoot. They worry about a single point of failure, as all services are managed by one daemon, and voice concerns about tight integration with the Linux kernel, which could limit portability to other systems.
|
||||
|
||||
That's the reason why some people created [distributions free from systemd][4].
|
||||
|
||||
Proponents, however, praise `systemd` for providing a more efficient and modern approach to system management, with its parallelization of service startup and on-demand starting of daemons reducing boot times and improving system responsiveness. They also commend its advanced logging capabilities.
|
||||
|
||||
Despite the controversy, `systemd` has become the default `init` system for many Linux distributions, and system administrators and developers have come to appreciate its advanced features and capabilities.
|
||||
|
||||
### Positives and Negatives of systemd Vs SysVinit
|
||||
|
||||
**Positives**
|
||||
|
||||
| Positives of SysVinit | Positives of systemd |
|
||||
| :- | :- |
|
||||
| Simplicity and familiarity | Improved boot-up speed |
|
||||
| Respect for Unix philosophy | Standardized logging system |[#]: url: " "
|
||||
|
||||
| More direct control over system services | Consistent approach to service management |
|
||||
| Mature and stable system | Compatibility with modern Linux systems and applications |
|
||||
| Compatibility with legacy systems and applications | Active development and support from a large community of developers and contributors |
|
||||
|
||||
**Negatives**
|
||||
|
||||
| Negatives of SysVinit | Negatives of systemd |
|
||||
| :- | :- |
|
||||
| Limited functionality compared to newer `init` systems | Complexity and steep learning curve |
|
||||
| Lack of built-in support for parallel startup of services | Invasive nature and potential for breaking compatibility with traditional Unix tools and utilities |
|
||||
| Can be less efficient than newer `init` systems, especially on large systems | Potential for instability and crashes on some systems |
|
||||
| Limited support for modern Linux systems and applications | Limited compatibility with legacy systems and applications that have not been updated to work with `systemd` |
|
||||
|
||||
### Conclusion: A Personal Perspective
|
||||
|
||||
As a Linux user hailing from the older days of UNIX, my preference leans toward the traditional `init` system. However, I've come to accept `systemd`, seeing some of its benefits despite my initial resistance. Each system has its own place in the Linux world, and it's important to understand both.
|
||||
|
||||
The `systemd` debate continues. What is your take on it?
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/systemd-init/
|
||||
|
||||
作者：[Bill Dyer][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/bill/
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://en.wikipedia.org:443/wiki/Init
|
||||
[2]: https://systemd.io:443/
|
||||
[3]: https://itsfoss.com/content/images/2023/07/Systemd-on-fedora.png
|
||||
[4]: https://itsfoss.com/systemd-free-distros/
|
||||
@ -0,0 +1,90 @@
|
||||
[#]: subject: "The systemd Controversy: A Beginner's Guide to Understanding the Debate"
|
||||
[#]: via: "https://itsfoss.com/systemd-init/"
|
||||
[#]: author: "Bill Dyer https://itsfoss.com/author/bill/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
systemd 争议：理解争议的初学者指南
|
||||
======
|
||||
|
||||
在 Linux 世界中，很少有争议能像传统的 System V [init][1] 系统（通常称为 SysVinit）和较新的 [`systemd`][2] 之间的斗争那样引起如此大的争议。
|
||||
|
||||
在这篇文章中，我将简要讨论什么是 systemd、它相对于传统 init 系统有哪些优点和缺点以及为什么它会引起争议。
|
||||
|
||||
### 什么是 systemd？
|
||||
|
||||
systemd 是一个系统和服务管理器，于 2010 年首次推出，用于取代传统的 System V init 系统。它旨在提高启动速度并更有效地管理系统服务。如今，`systemd` 是许多流行 Linux 发行版的默认`init` 系统，包括 Ubuntu、Fedora 和 Red Hat Enterprise Linux。
|
||||
|
||||
### systemd 是守护进程吗？
|
||||
|
||||
尽管有这个名字，“systemd” 并不是一个守护进程。相反，它是一个为 Linux 提供许多系统组件的软件套件。其目标：标准化 Linux 发行版的服务配置和行为。
|
||||
|
||||
`systemd` 的主要组件是一个“系统和服务管理器”，它充当 `init` 系统来引导用户空间并管理用户进程。它还提供各种守护程序和实用程序的替代品，从设备和登录管理到网络连接管理和事件记录。
|
||||
|
||||
### systemd 的主要特性
|
||||
|
||||
`systemd` 具有许多功能，例如它能够积极并行化操作、方便按需启动守护进程、使用 Linux 控制组监视进程、管理挂载点和自动挂载点，以及实现复杂的基于事务依赖的服务控制逻辑。
|
||||
|
||||
此外，`systemd` 支持 SysV 和 LSB 初始化脚本，作为 SysVinit 的替代品。它还提供了一个日志守护进程和用于管理基本系统配置的程序。
|
||||
|
||||
![systemd on fedora - Courtesy of Wikimedia][3]
|
||||
|
||||
### systemd 与 SysVinit：争议
|
||||
|
||||
init 与 systemd 争论的核心围绕如何最好地管理基于 Linux 的系统。关注的范围从复杂性和兼容性到管理系统服务的最佳方式，涉及系统管理员和 Linux 爱好者面临的基本问题。
|
||||
|
||||
批评者认为 `systemd` 过于复杂和单一，使得故障排除变得更加困难。他们担心单点故障，因为所有服务都由一个守护进程管理，并且担心与 Linux 内核的紧密集成，这可能会限制向其他系统的可移植性。
|
||||
|
||||
这就是为什么有些人创建[脱离 systemd 的发行版][4]的原因。
|
||||
|
||||
然而，支持者称赞 `systemd` 提供了一种更高效、更现代的系统管理方法，其服务启动的并行性和守护进程的按需启动减少了启动时间并提高了系统响应能力。他们还赞扬其先进的日志记录功能。
|
||||
|
||||
尽管存在争议，`systemd` 已成为许多 Linux 发行版的默认 `init` 系统，系统管理员和开发人员已经开始欣赏它的高级特性和功能。
|
||||
|
||||
### systemd 与 SysVinit 的优点和缺点
|
||||
|
||||
**优点**
|
||||
|
||||
| SysVinit 的优点 | systemd 的优点 |
|
||||
| :- | :- |
|
||||
| 简单且熟悉 | 提高启动速度 |
|
||||
| 尊重 Unix 哲学 | 标准化日志系统 |
|
||||
| 更直接地控制系统服务 | 一致的服务管理方法 |
|
||||
| 系统成熟稳定 | 与现代 Linux 系统和应用程序的兼容性 |
|
||||
| 与遗留系统和应用的兼容性 | 来自大型开发者和贡献者社区的积极开发和支持 |
|
||||
|
||||
**缺点**
|
||||
|
||||
| SysVinit 的缺点 | systemd 的缺点 |
|
||||
| :- | :- |
|
||||
| 与较新的 `init` 系统相比功能有限 | 复杂性和陡峭的学习曲线 |
|
||||
| 缺乏对服务并行启动的内置支持 | 有侵入性，可能会破坏与传统 Unix 工具和程序的兼容性 |
|
||||
| 可能比新的 `init` 系统效率低，尤其是在大型系统上 | 某些系统可能会出现不稳定和崩溃的情况 |
|
||||
| 对现代 Linux 系统和应用的有限支持 | 与尚未更新以与 `systemd` 配合使用的遗留系统和应用的兼容性有限 |
|
||||
|
||||
### 总结：个人观点
|
||||
|
||||
作为一名来自 UNIX 早期的 Linux 用户，我更倾向于传统的 `init` 系统。然而，尽管我最初有所抵制，但我已经开始接受 `systemd`，并看到了它的一些好处。每个系统在 Linux 世界中都有自己的位置，了解这两个系统非常重要。
|
||||
|
||||
关于 `systemd` 的争论仍在继续。你对此有何看法？
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/systemd-init/
|
||||
|
||||
作者：[Bill Dyer][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/bill/
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://en.wikipedia.org:443/wiki/Init
|
||||
[2]: https://systemd.io:443/
|
||||
[3]: https://itsfoss.com/content/images/2023/07/Systemd-on-fedora.png
|
||||
[4]: https://itsfoss.com/systemd-free-distros/
|
||||
Loading…
Reference in New Issue
Block a user