1
00:00:00,000 --> 00:00:12,120
In this video, you'll learn about the system V init legacy boot procedure. So what is this

2
00:00:12,120 --> 00:00:18,200
about? Well, this is about how we booted before system D. System D has been the standard for

3
00:00:18,200 --> 00:00:25,040
over a decade. So you won't find many systems anymore that use system V, also known as system

4
00:00:25,040 --> 00:00:31,920
V, which is named after the system V Unix distribution that already used this way of

5
00:00:31,920 --> 00:00:40,000
booting. System D booting replaces the system V legacy boot, where slash sbin slash init

6
00:00:40,000 --> 00:00:46,639
was the PID1 loaded by the kernel and responsible for booting everything else. Now in system

7
00:00:46,639 --> 00:00:52,200
V boot, the run level was used to define the state that the system should start in. And

8
00:00:52,200 --> 00:00:57,480
the etc init tab file was used to set the default run level in which the system would

9
00:00:57,480 --> 00:01:04,000
enter. So in system V boot, we had etc init tab to set the default run level. And you

10
00:01:04,000 --> 00:01:10,040
could use init or tell init commands to manage the current run level temporarily. Where run

11
00:01:10,040 --> 00:01:14,680
level five was for graphical, run level three was for multi-user. So if you would be in

12
00:01:14,680 --> 00:01:20,199
graphical, and you wanted to go to multi-user, you would use init three. And to start a

13
00:01:20,199 --> 00:01:26,120
different run level while booting, the number of the run level could be added at the end of

14
00:01:26,120 --> 00:01:34,720
the line that boots the kernel in grub. System V services were managed with service

15
00:01:34,720 --> 00:01:40,040
commands. So you would have service followed by the name of the service, followed by start,

16
00:01:40,040 --> 00:01:46,160
stop, status, or restart to perform one of the respective operations on them. And every

17
00:01:46,160 --> 00:01:51,760
now and then you still might have to do that if system D is not available. Now the service

18
00:01:51,760 --> 00:01:56,760
commands are for managing services individually. If you wanted to make sure that the service

19
00:01:56,760 --> 00:02:03,279
was toggled to be automatically enabled or disabled, you would use check config. So check

20
00:02:03,279 --> 00:02:09,639
config, httpd on would make sure that on Red Hat the httpd service would be started

21
00:02:09,639 --> 00:02:15,559
automatically. System V booting is legacy. It's old. And for that reason, you should not

22
00:02:15,559 --> 00:02:22,800
search for system V compatibility while using system D, but use system D solutions. So nobody

23
00:02:22,800 --> 00:02:28,320
is using these options anymore unless you encounter a distribution where you get a system

24
00:02:28,320 --> 00:02:35,119
CTL command not found. If that is the case, use the service command instead. But fortunately,

25
00:02:35,199 --> 00:02:36,839
that's going to be pretty rare.