1
00:00:00,002 --> 00:00:05,002
(upbeat music)

2
00:00:05,002 --> 00:00:07,001
- [Instructor] Let's look at a couple of challenges

3
00:00:07,001 --> 00:00:09,009
related to messages from the kernel

4
00:00:09,009 --> 00:00:11,007
and the proc file system.

5
00:00:11,007 --> 00:00:13,005
Real simple.

6
00:00:13,005 --> 00:00:17,005
First of all, go to /proc, do an ls.

7
00:00:17,005 --> 00:00:20,003
Look to see if you can figure out if there's a file

8
00:00:20,003 --> 00:00:22,006
for the kernel command line.

9
00:00:22,006 --> 00:00:25,003
The name of the file is pretty good.

10
00:00:25,003 --> 00:00:27,006
I think if you look a little bit, you'll find it.

11
00:00:27,006 --> 00:00:28,008
Cat that out.

12
00:00:28,008 --> 00:00:30,002
See what it is.

13
00:00:30,002 --> 00:00:32,002
Now you know what the kernel command line is,

14
00:00:32,002 --> 00:00:34,006
use dmesg piped into grep,

15
00:00:34,006 --> 00:00:39,003
and see if dmesg reported the kernel command line.

16
00:00:39,003 --> 00:00:44,000
If not, maybe the messages have rolled over.

17
00:00:44,000 --> 00:00:45,007
If your system's been up for a while,

18
00:00:45,007 --> 00:00:47,002
the RAM buffer's only so big.

19
00:00:47,002 --> 00:00:50,001
It'll have lost some of the messages.

20
00:00:50,001 --> 00:00:55,008
You can look under /var/log for kernel messages,

21
00:00:55,008 --> 00:00:57,004
if they're there, or if not,

22
00:00:57,004 --> 00:01:01,001
you could try the journal control -k command

23
00:01:01,001 --> 00:01:03,009
and then look at the proc file meminfo

24
00:01:03,009 --> 00:01:05,004
and see if you could determine

25
00:01:05,004 --> 00:01:10,002
what's the total amount of RAM available in your system.

26
00:01:10,002 --> 00:01:12,000
Alright, give those a try.