1
00:00:00,000 --> 00:00:14,720
Hey everyone and welcome back.

2
00:00:14,720 --> 00:00:19,339
So now what we're doing is we are back on our client machine.

3
00:00:19,339 --> 00:00:24,339
Now what I've actually done here is I have rebooted that machine.

4
00:00:24,339 --> 00:00:32,340
So if I happen to issue a DF-H, you will notice that we have no longer mounted the

5
00:00:32,340 --> 00:00:37,100
network file share that we are getting from the NFS server.

6
00:00:37,100 --> 00:00:43,579
Now think about this, what if we wanted to boot up our machine and have immediate access

7
00:00:43,579 --> 00:00:45,340
to that particular share?

8
00:00:45,340 --> 00:00:49,039
Well the reality lies in being able to configure persistence.

9
00:00:49,039 --> 00:00:55,740
Now if I had to pop quiz you and ask you what file do you think we should modify to invoke

10
00:00:55,740 --> 00:00:59,759
some type of persistent mounting of a file system?

11
00:00:59,759 --> 00:01:04,480
Well hopefully you will remember that we have a configuration file called FSTab within the

12
00:01:04,480 --> 00:01:05,840
Etsy directory.

13
00:01:05,840 --> 00:01:10,920
That is absolutely where we are going to make this configuration so that we can have such

14
00:01:10,920 --> 00:01:12,759
a persistent connection.

15
00:01:12,759 --> 00:01:17,359
So before I do anything like I say I will show you my mount directory.

16
00:01:17,359 --> 00:01:23,079
We still have the my share directory we created where we were actually mounting our network

17
00:01:23,079 --> 00:01:24,079
file system.

18
00:01:24,079 --> 00:01:29,120
But if I do an LS notice that those particular files that we created, file 1 and file 2 are

19
00:01:29,120 --> 00:01:32,879
not accessible, that is because we have not got the mount in action.

20
00:01:32,879 --> 00:01:37,879
Now again of course we do realise we can just manually mount the file system with the mount

21
00:01:37,879 --> 00:01:42,359
command as we did before and I could help if I could spell mount correctly.

22
00:01:42,359 --> 00:01:43,359
There we go.

23
00:01:43,359 --> 00:01:49,439
And obviously that can be a little bit inefficient if we want to be using this very very regularly.

24
00:01:49,439 --> 00:01:53,000
So what we will do here is we will go in and do sudo nano.

25
00:01:53,000 --> 00:01:55,780
I am going to Etsy and then I will go into FSTab.

26
00:01:55,780 --> 00:01:57,840
So let me type in the password here.

27
00:01:57,840 --> 00:02:01,359
Cool so let me actually just full screen this so it looks a little bit neater.

28
00:02:01,359 --> 00:02:02,359
There we go.

29
00:02:02,359 --> 00:02:06,239
So what I am going to do here is I am going to follow the same format.

30
00:02:06,239 --> 00:02:12,000
What I will do is I will give the IP address of the server that I am trying to reach to

31
00:02:12,000 --> 00:02:19,520
remember that will be the NFS server which has the IP address 192.1680.44.

32
00:02:19,520 --> 00:02:20,520
Let me just confirm that.

33
00:02:20,520 --> 00:02:21,520
Let's do an IP adder.

34
00:02:21,520 --> 00:02:26,639
Yep we can see right here 192.1680.44 that is correct.

35
00:02:26,639 --> 00:02:31,000
So back onto the client right here and then we will do a colon then a forward slash and

36
00:02:31,000 --> 00:02:32,560
then the name of the share.

37
00:02:32,560 --> 00:02:35,879
Now the share we created was simply called my share.

38
00:02:35,879 --> 00:02:40,520
And now what I want to do is I want to specify where it is I am going to mount this.

39
00:02:40,520 --> 00:02:45,680
I am going to mount it in the MNT directory on my system within the directory I created

40
00:02:45,680 --> 00:02:47,120
called my share.

41
00:02:47,120 --> 00:02:50,600
And then I want to specify the file system type which will be NFS.

42
00:02:50,600 --> 00:02:55,480
And now I can specify the different options that I want to invoke here.

43
00:02:55,480 --> 00:03:01,200
Now I am just going to use the defaults and then I will have my values 0 and 0.

44
00:03:01,200 --> 00:03:04,120
If you do recall these values relate to things such as FISC.

45
00:03:04,120 --> 00:03:06,120
We don't need to worry about that so much right now.

46
00:03:06,319 --> 00:03:11,120
Within these defaults here we can actually specify different options if we so wish.

47
00:03:11,120 --> 00:03:16,719
We can specify something called say for example a soft mount meaning that if the server isn't

48
00:03:16,719 --> 00:03:22,520
actually reachable for whatever reason that may be soft mount will stop attempting to mount

49
00:03:22,520 --> 00:03:24,480
that network file system.

50
00:03:24,480 --> 00:03:30,400
Whereas if we specify a hard mount even if the server is not reachable hard mount is

51
00:03:30,400 --> 00:03:35,000
going to specify that we keep trying and trying and trying until we have reached a

52
00:03:35,000 --> 00:03:37,000
certain given timeout.

53
00:03:37,000 --> 00:03:40,120
A timeout by the way that we can control and specify.

54
00:03:40,120 --> 00:03:44,560
But for now we are not going to worry too much about those particular configurations.

55
00:03:44,560 --> 00:03:46,800
Understand they do exist be aware of them.

56
00:03:46,800 --> 00:03:48,759
But for now we will just leave the defaults.

57
00:03:48,759 --> 00:03:54,719
So now what we have here is we have specified the server plus its share name.

58
00:03:54,719 --> 00:03:57,360
We specify whereabouts we want to mount it.

59
00:03:57,360 --> 00:04:00,240
The file system with some default values.

60
00:04:00,240 --> 00:04:07,159
But if I happen to just save this right now and I escape out again I do a DFH nothing

61
00:04:07,159 --> 00:04:09,600
has actually changed quite just yet.

62
00:04:09,600 --> 00:04:17,040
What I can do though is I can run the mount-a command or I could reboot my system either

63
00:04:17,040 --> 00:04:19,840
or as fine so I will just use mount a.

64
00:04:19,840 --> 00:04:23,720
That is going to pull in the configurations that we get from fstab.

65
00:04:23,720 --> 00:04:30,480
If I try running this command once again notice now that we have indeed actually got access

66
00:04:30,480 --> 00:04:36,280
to that share mounted over the network and if I go into my mount directory and into my

67
00:04:36,280 --> 00:04:41,960
share we do an ls suddenly those files are once again accessible.

68
00:04:41,960 --> 00:04:47,440
And if I happen to just reboot my system do a telnet 6 for a reboot give it a little minutes

69
00:04:47,440 --> 00:04:50,360
so we will go and open up a terminal.

70
00:04:50,360 --> 00:04:58,000
What I will do is immediately do a DF-H and we can see here indeed the share has been

71
00:04:58,000 --> 00:05:04,520
automatically mounted and we do have persistence if I go in to my MNT directory and into my

72
00:05:04,520 --> 00:05:12,199
share clearly we have access to our files from our file system across the network via the

73
00:05:12,199 --> 00:05:14,040
NFS server.

74
00:05:14,040 --> 00:05:18,480
So that's how we can configure our clients to have persistent mounting and access to

75
00:05:18,480 --> 00:05:22,060
those shares over the network I hope this has been informative for you and I would like

76
00:05:22,060 --> 00:05:23,360
to thank you for viewing.

