Linux boot mode: systemd upstart sysV

Today, I saw a microblog saying that the biggest change in the RHEL7 beta system may be replacing upstart with systemd, so I have to say goodbye to the chkconfig command.

Suddenly we were confused about systemV, upstart, and systemd. Previously, I always thought that upstart was in the Ubuntu system. Didn't RH systems use sysV? Should RHEL6 start to use upstart to replace init?

Check the notes of the previous class:

"Early use of devices under/dev/requires # mknod Loading

More than 2.4 files exist in the directory before kernel 20 thousand

Udev: Create device files as needed"

"This method is quite inefficient: traditional. Because the boot process was completed by the script, it was very slow.

Although the idea of Red Hat 6 is the same, it is:/sbin/init --> changed to upstart: event-driven init, which does not depend on the configuration file. However, the service life is not long.

Later I developed this: systemd, imitating MAC, and making services parallel and independent from each other.

Fedora15, followed by systemd, extremely fast startup"

###################################

Update:

The Debian community is arguing about the default init system used in the next version. The focus is on the more advanced systemd technology and cross-platform upstart. Bdale Garbee, chairman of the Debian Technical Committee, expressed his support for systemd in the mail list, which allowed the Committee to support more than upstart. Debian GNU/Linux Project Leader Lucas nussbum asked the Technical Committee to decide the default init system for the next version in last November. There are three candidate init systems: Red Hat's systemd, Canonical upstart, and OpenRC. Four members of the previously stated technical committee supported upstart, including Ian Jackson, former Canonical employees, Colin Watson, Steve Langasek, and Don Armstrong; the number of people supporting systemd is also four.