WEBVTT

00:00.810 --> 00:07.200
Uh, some drugs can split into partitions in order to manage and uh and separate information.

00:07.800 --> 00:14.130
So, for instance, you may want to separate your hard drives so that your swept file home directory

00:14.130 --> 00:17.880
and root directory are all on separate partitions.

00:18.360 --> 00:24.780
So you may want to do this for a number of reasons uh, including to share resources and to reflect

00:24.790 --> 00:25.930
the different permissions.

00:25.980 --> 00:32.430
So the new labels each partition with a minor number that comes after the Z designation.

00:32.880 --> 00:41.460
So this way, uh, then first partition on the certain, uh, wold be SD, a one I won't forget here

00:42.020 --> 00:43.370
is here.

00:44.010 --> 00:46.440
So let's find a CTA here.

00:46.950 --> 00:49.950
This is, uh, my hard drive.

00:51.060 --> 01:03.690
If you had a second device, attach it to your computer, you will still be SDC esteem or SDF like that.

01:04.110 --> 01:09.030
How many files that many SD and Alphabet you will have?

01:10.800 --> 01:11.130
So.

01:14.660 --> 01:21.170
Uh, this way, uh, mine, the miner, as you can see here, that this way, uh uh, the first position

01:21.170 --> 01:25.480
on the setup will, uh, drive Baldwin SD a one.

01:26.570 --> 01:33.490
So the second position will do it and stick a tool towards the tree and so on.

01:33.500 --> 01:33.860
Yeah.

01:34.970 --> 01:42.920
And here so at times, you may want to view the politicians on your Linux system to see which one,

01:43.310 --> 01:47.000
which ones you have and how much capacity is available in each.

01:47.450 --> 01:51.170
You can do this by using if disk utility utility.

01:52.230 --> 02:03.360
And um, if this utility, you can do this by if this utility and using L Switch with fdisk lifts all

02:03.360 --> 02:10.580
the partitions here because we need to, uh, give of permissions to this pseudo and Typekit of kind

02:10.590 --> 02:11.400
of passport here.

02:11.400 --> 02:16.470
As you can see here, we have, uh, we printed all of our disks here.

02:17.040 --> 02:27.150
So as you can see here, the device's SD, A1, SD, A2 and A5 are listed in the first stanza.

02:28.110 --> 02:34.290
So these three devices make up the virtual disks from my virtual machine, which is, um.

02:35.660 --> 02:44.360
Eighteen eighty gigabyte drive with three partitions here, including the server partitions, um, including

02:44.360 --> 02:51.950
the smart partitions and which acts like a virtual lame ram, similar to page files and windows.

02:52.990 --> 02:56.080
So sweat partitions and it's like a virtual ram.

02:56.920 --> 03:03.020
It's similar to windows like windows using patch partition for virtual ram.

03:03.040 --> 03:03.370
Right?

03:04.150 --> 03:08.500
So this partition is using when a RAM capacity is accepted.

03:08.650 --> 03:18.100
So if you scan down here now to the third Cesar, if you have it external drive, you will see a second

03:18.100 --> 03:22.480
device output designed by SD, B or STC here.

03:22.870 --> 03:29.890
So, uh, this can be your flash are flash drive or, um, anything here.

03:29.950 --> 03:40.570
So actually, we can, uh, see our drives here with Partition Gparted application here and you can

03:40.570 --> 03:41.620
run Gparted.

03:41.800 --> 03:46.240
You parked it like that and enter your password here.

03:46.240 --> 03:47.480
In my case is Kala.

03:47.650 --> 03:54.250
By default, as you can see, we can see our device's actual partition as well.

03:54.830 --> 03:57.520
It this is the one device here attached to it.

03:58.180 --> 04:01.960
And as you can see here, we have a two gigabyte.

04:03.290 --> 04:05.360
Actual seventy nine gigabyte.

04:06.680 --> 04:14.300
Main system, a root system, the second is extended and the second the third is Linux smart and one

04:14.300 --> 04:18.130
megabyte is unallocated near, as you can see the SDR.

04:18.230 --> 04:22.070
I have one hard disk and another X and I have discussed attached to it.

04:22.730 --> 04:31.310
So something else to note about the naming of the files in the directory is that the first positions

04:31.310 --> 04:34.820
contains either C or B.

04:35.810 --> 04:43.580
So you can see here, for example, uh, as L here as you can see or C.

04:44.910 --> 04:50.040
Or be here, we will have, as you can see there, a bee here.

04:51.390 --> 04:58.710
So what this means, so these letter represents the two ways that devices transfer data in and out.

04:59.160 --> 05:05.760
So this C stands for character on this device are known as you might expect as a character devices.

05:06.840 --> 05:13.230
So external devices that interact with the system by sending and receiving data collected by characters

05:13.230 --> 05:13.800
such as.

05:14.980 --> 05:23.980
Mice or keyboards are connected devices, the B stands for the second type look devices, they communicate

05:23.980 --> 05:31.660
in blocks of data, multiple bytes at a time and include devices like hard drives and DVD, DVD drives

05:32.290 --> 05:33.650
and et cetera.

05:33.910 --> 05:41.020
These drives require high speed data transport and therefore send and receive data in blocks, many

05:41.020 --> 05:43.090
connectors or bytes at a time.

05:44.260 --> 05:49.750
So once you know whether a device is character or a bloke's device, you can easily get more information

05:49.750 --> 05:51.430
about it, as you will see next.

05:52.360 --> 05:59.890
So less blook devices and interfere in information with LSV Alki at least be OK.

06:00.130 --> 06:07.120
So Linux and the Linux common lisp health care for least block here, least block here.

06:07.780 --> 06:16.960
So this common list some basic information about each block device now listed in the Div Directory directory.

06:17.620 --> 06:21.700
So the result is similar to the output from the FTC IL here.

06:22.270 --> 06:27.250
So but it will also display the devices with multiple partitions in a kind of tree.

06:27.700 --> 06:35.260
So showing each device, which is partition as bridges here, uh, like that and does not require root

06:35.710 --> 06:37.300
privileges to a room run.

06:37.420 --> 06:41.380
So as you can see, we have SD and Xerox here.

06:42.430 --> 06:49.900
So the output includes the floppy, uh, if you have a little drive here, if T zero and DVD drive s

06:50.250 --> 06:51.990
s s are zero.

06:52.000 --> 06:54.040
So this isn't my DVD drive here.

06:54.850 --> 07:02.560
Uh, so this is simply a holdover for legacy systems for we can also see information on the mount point

07:02.560 --> 07:03.700
of the drive here.

07:04.180 --> 07:08.500
As you can see, there's multiple multipoint swap and this is the root directory, which is seven to

07:08.500 --> 07:11.380
nine hours, 18 and gigabytes here.

07:12.610 --> 07:13.330
Um, and.

07:14.880 --> 07:23.510
Not at them, Hard Drive is a one month old here, um, the road and the flash drive, if you have it,

07:23.510 --> 07:30.670
will amount to media here, so you will see more the significant of this in next pictures, actually

07:30.710 --> 07:32.900
next nine minutes here.

07:33.650 --> 07:35.690
So mounting and mounting.

07:37.960 --> 07:44.680
Most modern operating systems, including most new versions of Linux, Ottoman storage devices when

07:44.680 --> 07:50.290
they are attached, so meaning the new flash drive or hardware is automatically attached to the file

07:50.290 --> 07:58.300
system for those new to Linux, the mounting might be a subject, so a storage device must be first

07:58.300 --> 08:02.230
physically connected to the file system and then logically attached to the file system.

08:02.620 --> 08:05.710
In order for the data to be made available to the operating system.

08:06.130 --> 08:12.730
In other words, if the device is physically or physically attached to the system, it's a that's necessarily

08:13.000 --> 08:16.580
logically attached and available to the operating system.

08:16.900 --> 08:23.950
So the term mount is a legacy from the early days of competing, when storage tapes before hard drives

08:23.950 --> 08:27.970
had had to be physically mounted to the computer system.

08:28.510 --> 08:32.110
Think of these big computers with spinning tape drives.

08:32.110 --> 08:39.790
You might have seen old science fiction movies here, and I mentioned the point in the Directory three

08:40.210 --> 08:44.710
directory where the drives are attached is known as the Mount Point.

08:44.890 --> 08:50.130
So the two main ones in Linux are entire year.

08:50.680 --> 08:53.470
Actually, that's what happened.

08:54.890 --> 08:55.220
Most.

08:56.790 --> 08:57.390
I'm sorry.

08:57.630 --> 08:58.290
Display.

09:07.070 --> 09:07.430
Here.

09:16.250 --> 09:17.630
I'm sorry, one minute, please.

09:23.280 --> 09:23.580
OK.

09:29.080 --> 09:29.980
OK, we fixed it.

09:30.850 --> 09:32.800
So let's see the.

09:33.820 --> 09:34.150
Near.

09:37.010 --> 09:38.180
It's modest.

09:38.520 --> 09:44.490
So when as much as I mentioned the point in the directory three where the device are attached is known

09:44.490 --> 09:45.690
as the mind point.

09:46.140 --> 09:55.120
So the two main mount, no points in Linux are A. and media here media.

09:55.140 --> 10:02.340
As a general rule, internal hard drives are mandated to monitor that MMT and external use drives such

10:02.340 --> 10:10.290
as flash drives and external USB drives are mounted at media through a specially taken and taken strategically.

10:10.290 --> 10:11.700
Command directory can be used.

10:12.880 --> 10:15.910
So here I am using visual books.

10:16.010 --> 10:21.760
I actually am not using VMware here, so I will create a new USB flash drive.

10:21.760 --> 10:23.980
Here is the controller.

10:26.960 --> 10:28.160
Hard disk drive.

10:29.490 --> 10:33.090
This will be OK, great visual.

10:33.410 --> 10:38.010
It will be by 0.5 gigabyte.

10:39.700 --> 10:42.310
Store desk has a single file.

10:42.640 --> 10:42.990
OK.

10:46.830 --> 10:54.270
So in some versions of Linux, you amounted to a dry manual in in order in order to access its content.

10:54.660 --> 11:03.270
So this is a skill worth learning to your man to drive on the pipeline system, use the Mount Command.

11:03.660 --> 11:07.740
So demand point for the device will be an empty directory.

11:08.160 --> 11:16.890
If you want a device on a directory that has UM directory to subdirectories and files, the smart device

11:16.890 --> 11:21.810
will cover the contents of the directory, so making them invisible and unavailable.

11:22.140 --> 11:29.680
So the mount the new hard drive, for example, SDP amount is to be one at the M.A. Directory.

11:29.680 --> 11:41.820
You will enter here and Mount Dev SDB, SD or step one and month M.A. him into directory.

11:42.210 --> 11:50.340
So you have four in mounting the you will enter um, this following into a command M.A. you will have

11:50.340 --> 11:51.870
to use sudo here.

11:52.230 --> 11:55.860
And step one is not existed because it's either.

11:55.930 --> 12:01.190
I have no intel then instead be to my seer or external drive or drive.

12:01.200 --> 12:04.080
You know, the hard drive should be available for access.

12:04.260 --> 12:10.560
So if you want to monitor, um, flash drive STC one, is this one.

12:11.600 --> 12:14.270
Is this given to Media Directory?

12:14.750 --> 12:18.410
Uh, you know, you, uh, do enter this month here.

12:18.890 --> 12:19.310
So.

12:21.420 --> 12:27.280
We can amongst our devices as well, so if you are coming from a Mac or Windows window background,

12:27.490 --> 12:33.640
so you're probably on the drive without knowing so before your removal flash drive from your system,

12:33.940 --> 12:39.610
your as you remember, they mean right click on to erect it to keep causing damage to the files stored

12:39.610 --> 12:40.510
in the device.

12:40.840 --> 12:43.780
So Eject is just another word for unwanted.

12:44.260 --> 12:51.510
So similar to Mount Command, you can on want a second hard drive by entering on Mont or you're actually

12:51.520 --> 12:53.180
not amount you want.

12:53.800 --> 12:54.650
You want?

12:55.180 --> 13:04.930
Uh, here uh was followed by the entry of the device in the directory here, our dev sdb1, for example.

13:06.130 --> 13:06.580
And.

13:07.940 --> 13:08.410
Um.

13:09.570 --> 13:14.860
A similar demand comment you can on want a second hard drive by entering command here?

13:15.870 --> 13:18.930
Well, for example, I entered SDP one year.

13:24.350 --> 13:29.460
And then click Enter and this you can see it, I have no such file or directory because I know that

13:29.960 --> 13:36.440
I entered in this um stibbe one here so we can monitor files here.

13:36.670 --> 13:37.110
Yeah.

13:37.520 --> 13:39.860
You be in this lecture as well.

13:40.340 --> 13:40.880
We will.

13:41.330 --> 13:45.230
We will also look at some comments for monitoring this state of the fire system.

13:45.650 --> 13:48.770
So esco necessary for any hacker or system administrator.

13:48.890 --> 13:56.360
So we will get some information about the amount of disks and then checked for and fix errors here.

13:56.840 --> 14:01.040
So storage devices are virtually error front, so it's not learning the skill.

14:01.550 --> 14:04.490
So getting information on mounted disks, actually, it's me.

14:04.670 --> 14:05.050
Sure.

14:05.090 --> 14:05.420
OK.

14:05.750 --> 14:11.810
So getting information on mounted disk to the command, the f the f.

14:13.770 --> 14:21.000
Um, means this hopefully will provide us with basic information on any hard disks or smart devices

14:21.000 --> 14:27.590
such as CDs or DVDs and flash drives, including how much space is being used and how much is available

14:28.500 --> 14:29.430
with alternate options.

14:29.850 --> 14:38.010
DD if Dev holds the first drive on your system, in this case, it is, uh, it's a and.

14:41.420 --> 14:46.810
If you want to check a different drive simply full of DMF, comment here.

14:47.120 --> 14:50.300
Uh, buy your driving him.

14:52.740 --> 14:54.870
So we can check errors as well here.

14:55.240 --> 15:03.610
Know if it's if it's, uh, see command shortfall fi system check checks to file system for errors and

15:03.610 --> 15:04.680
the repairs the damage.

15:05.660 --> 15:13.490
If possible or else, plus the bed area in to a bad bloke's table to market as a bed so near to turn

15:13.940 --> 15:19.340
to run, if it's seeking common, you need to specify the filesystem type here.

15:21.850 --> 15:23.090
Actual, uh.

15:25.090 --> 15:29.470
And I will not continue here, so you can.

15:29.740 --> 15:41.200
So in order to run it first, you hold one moment there is to be one or your, um, your file system,

15:41.800 --> 15:43.920
I it storage devices.

15:44.800 --> 15:45.160
So.

15:47.020 --> 15:53.080
Um, and then you can run if it's seeking comment here, which I will not run.

15:53.320 --> 16:01.000
So understanding how Linux designers and manage its devices is circular for any Linux user and hacker

16:01.450 --> 16:07.180
hackers will need to know what devices are attached to a system and how much space is available.

16:07.480 --> 16:13.300
Because storage devices are often develop errors here so we can check and report these errors with f

16:13.300 --> 16:20.680
s c key and D, the command is capable of making the physical copy of a device, including any deleted

16:20.680 --> 16:21.430
files, of course.
