1
00:00:00,000 --> 00:00:09,880
So, to work with file systems, they need to be mounted.

2
00:00:09,880 --> 00:00:14,960
And even if nowadays there are system demounts, ETCFSSTEP is still the standard.

3
00:00:14,960 --> 00:00:19,440
So let's discuss what is going on in this important configuration file.

4
00:00:19,440 --> 00:00:22,660
So ETCFSSTEP is used to automate mounts.

5
00:00:22,660 --> 00:00:26,780
In current Linux, it's used as an input file for the FSSTEP generator.

6
00:00:26,780 --> 00:00:30,500
And that is a systemd component that generates the system demounts.

7
00:00:30,500 --> 00:00:32,860
We talked about it in an earlier lesson.

8
00:00:32,860 --> 00:00:36,980
In ETCFSSTEP, six columns are used to automate mounts.

9
00:00:36,980 --> 00:00:41,740
The first column has the name of the device, or the UUID or label, if you want to mount

10
00:00:41,740 --> 00:00:44,040
by UUID or label.

11
00:00:44,040 --> 00:00:47,860
Then there is the mount point, followed by the file system type.

12
00:00:47,860 --> 00:00:49,580
Next there are the mount options.

13
00:00:49,580 --> 00:00:54,380
And column five and six are for the dump option and the FSCHEC option.

14
00:00:54,380 --> 00:00:59,820
The dump option enables or disables support for the legacy dump utility.

15
00:00:59,820 --> 00:01:04,739
As it is a legacy utility, not many people are using it anymore, and in many cases you

16
00:01:04,739 --> 00:01:06,540
will find zero.

17
00:01:06,540 --> 00:01:11,779
FSCHEC is determining the order for a file system check.

18
00:01:11,779 --> 00:01:15,940
File system check is also something that belongs to older file systems.

19
00:01:15,940 --> 00:01:19,660
Basically, EXE2, EXE3 were using it.

20
00:01:19,660 --> 00:01:20,660
Now what was the idea?

21
00:01:20,940 --> 00:01:25,860
Well, if your server crashed and it came up again, then file systems were checked.

22
00:01:25,860 --> 00:01:29,779
And the FSCHEC option would be used to determine the order of checking.

23
00:01:29,779 --> 00:01:31,300
Zero means no checking.

24
00:01:31,300 --> 00:01:33,339
One means check this first.

25
00:01:33,339 --> 00:01:38,820
Two means check this after the file system that has been marked with a one.

26
00:01:38,820 --> 00:01:43,739
In current FSSTEP configurations, you will find zero, zero in most cases for dump and

27
00:01:43,739 --> 00:01:44,739
FSCHEC.

28
00:01:44,739 --> 00:01:48,820
Let's explore the contents of this configuration file.

29
00:01:48,820 --> 00:01:54,739
So here we have the ETCFS app, and we already worked with it, so it can be quite fast.

30
00:01:54,739 --> 00:01:56,300
Maybe this one is interesting.

31
00:01:56,300 --> 00:01:58,419
So we are mounting a UUID.

32
00:01:58,419 --> 00:02:04,300
I'll tell you later more about UUIDs and labels, but UUIDs and labels will never change, even

33
00:02:04,300 --> 00:02:06,739
if your device name may change.

34
00:02:06,739 --> 00:02:12,500
And for that reason, mounting by UUID or by label is standard.

35
00:02:12,500 --> 00:02:16,539
Now we have the directory on which you want to mount the file system.

36
00:02:16,539 --> 00:02:19,899
And here we have a couple of mount options.

37
00:02:19,899 --> 00:02:22,820
Many options can be provided while mounting.

38
00:02:22,820 --> 00:02:27,580
Here we can see a UMASK and a short name, but other popular options, for instance, are

39
00:02:27,580 --> 00:02:33,940
no exec, which means that you cannot run any executable files, or no fill, which means

40
00:02:33,940 --> 00:02:38,940
that if the file system cannot be mounted while booting, your boot procedure won't fill

41
00:02:38,940 --> 00:02:40,660
because of that.

42
00:02:40,660 --> 00:02:46,179
You put all of these options in the fourth column and feel free to replace defaults with

43
00:02:46,300 --> 00:02:49,660
any option that you would like to use.

44
00:02:49,660 --> 00:02:56,100
After tweaking your ETCFS step, I would always advise to use mount minus A. Mount minus A

45
00:02:56,100 --> 00:02:59,740
is going to mount everything that hasn't been mounted yet.

46
00:02:59,740 --> 00:03:04,339
And even stronger, if you reboot, you can immediately verify if everything works out

47
00:03:04,339 --> 00:03:05,339
all right.

48
00:03:05,339 --> 00:03:10,500
In real life, I would always advise you to reboot after making changes to ETCFS step

49
00:03:10,500 --> 00:03:15,380
just to make sure that you didn't make any critical errors, which make that your system

50
00:03:15,380 --> 00:03:17,580
may not be able to boot anymore.