1
00:00:06,519 --> 00:00:09,539
You can also request
information about hardware properties.

2
00:00:10,060 --> 00:00:14,130
These hardware properties are monitored
through the sys sudo file system.

3
00:00:15,009 --> 00:00:20,626
And as an easy interface you can use
udev ADM info because that will read it

4
00:00:20,626 --> 00:00:26,243
for you and it will get the relevant
information. You will notice that this sys file

5
00:00:26,243 --> 00:00:31,859
system can be quite complicated, so better use
commands like udev ADM info on DEV cdrom.

6
00:00:32,770 --> 00:00:35,229
Hardware properties may also
be set on the drivers.

7
00:00:35,759 --> 00:00:39,575
If that is the case,
you can use mod info

8
00:00:39,575 --> 00:00:43,390
that will show you the
driver information that is happening.

9
00:00:44,530 --> 00:00:48,840
If, for instance, you want to
see what is going on on your

10
00:00:48,840 --> 00:00:53,150
CD ROM device, ModInfo on SR0
should do it. Let me show you.

11
00:00:54,329 --> 00:01:00,890
Let's start at the lower level, which is
the driver level where I'm going to use

12
00:01:00,890 --> 00:01:07,450
sudo LSMod, Pipe Grab SR SR is typically
your CD ROM device. And oh, I can

13
00:01:07,449 --> 00:01:14,009
see CD ROM, that's the module that I
need. Okay, so I'm using multinfo to CD

14
00:01:14,009 --> 00:01:20,569
Rom and there we can see the
different parameters that exist for this driver.

15
00:01:21,569 --> 00:01:25,810
So these are parameters that
determine the usage of the driver.

16
00:01:26,349 --> 00:01:32,042
Now, for a CD ROM that
is not very spectacular, but if you

17
00:01:32,042 --> 00:01:37,734
do the same for a network
card like my E1000 there we can

18
00:01:37,734 --> 00:01:43,427
see settings that determine how the
network card is working. Like the duplex

19
00:01:43,427 --> 00:01:49,120
setting. That's kind of old, but
other settings might be available as well.

20
00:01:49,620 --> 00:01:55,120
Sometimes if there's a problem, then it might
be related to the parameters of these drivers.

21
00:01:55,640 --> 00:02:02,269
Now, if you want to know in more detail
what is going on, then UDEV adminfo is useful.

22
00:02:02,930 --> 00:02:08,370
Let me use sudo udev
adminfo on DEV CDROM for instance.

23
00:02:09,270 --> 00:02:14,050
There we can see all the different properties
that I set for this CD ROM device.

24
00:02:14,770 --> 00:02:19,449
Now I'm using the device
interface file to get this information.

25
00:02:20,050 --> 00:02:26,525
As you can see on the top line, it
is actually using a file that is deeply hidden

26
00:02:26,525 --> 00:02:33,000
into the sys devices directory and all the
property of the device device are shown right here.

27
00:02:33,789 --> 00:02:38,599
And I would definitely recommend,
if ever you need to know

28
00:02:38,599 --> 00:02:43,409
more about your devices, check
it out here. UDEV ADM info

29
00:02:43,409 --> 00:02:48,219
is much more accessible than
exploring the sys directory for yourself.