<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Tue, Jun 18, 2013 at 9:38 AM, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On 18/06/13 14:05, Daryl McDonald wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I'm not understanding how to view /var/log/messages.<br>
<br>
</blockquote></div>
As root, "cat /var/log/messages"; although that could give you thousands of lines if your host has been up long, or "tail -<n> /var/log/messages" where <n> is a number (that's /just/ a number after the hyphen). That will display the last n lines of the log.<br>
<br>
I would also have a look at dmesg. You don't need to be root to do that and if you try "dmesg | more" you'll see how the system boots up and what it thinks it finds.<br>
<br>
The first few pages can be skipped over as that's the software finding out what CPU and memory you have. Later on you'll see what peripherals it finds.<div class="im"><br></div></blockquote><div><br></div><div>Instead of trying to find the needle in a haystack, do this:</div>
<div><br></div><div>grep -i -E "kworld|dvb" /var/log/messages</div><div><br></div><div>and</div><div><br></div><div>dmesg | grep -i -E "kworld|dvb"</div><div><br></div><div>The '-i' modifier says to ignore case, and -E is extended regexp, so it will look for lines with kworld OR dvb.</div>
<div><br></div><div>If you want to view the whole file, by all means do the above, but trying to find a single line amongst thousands by eye is going to be difficult.</div><div><br></div><div>Tom</div><div> </div></div></div>
</div>