<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Use /proc File System to Monitor Linux System	</title>
	<atom:link href="https://www.tecmint.com/exploring-proc-file-system-in-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Thu, 25 Jan 2024 04:57:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ravi Saive		</title>
		<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-2048668</link>

		<dc:creator><![CDATA[Ravi Saive]]></dc:creator>
		<pubDate>Fri, 25 Aug 2023 07:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=4561#comment-2048668</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-1040467&quot;&gt;situn&lt;/a&gt;.

@Situn,

In the Linux /proc directory, you&#039;ll encounter a mix of files with different sizes including files with 0KB size. However, this doesn&#039;t mean they are empty or lack content, but they are often used as interfaces to kernel data structures, configurations, or real-time information.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-1040467">situn</a>.</p>
<p>@Situn,</p>
<p>In the Linux /proc directory, you&#8217;ll encounter a mix of files with different sizes including files with 0KB size. However, this doesn&#8217;t mean they are empty or lack content, but they are often used as interfaces to kernel data structures, configurations, or real-time information.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: situn		</title>
		<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-1040467</link>

		<dc:creator><![CDATA[situn]]></dc:creator>
		<pubDate>Thu, 27 Sep 2018 06:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=4561#comment-1040467</guid>

					<description><![CDATA[The &lt;code&gt;/proc&lt;/code&gt; directory has &lt;strong&gt;0kb&lt;/strong&gt; files but there are some files that have some size what are those files?]]></description>
			<content:encoded><![CDATA[<p>The <code>/proc</code> directory has <strong>0kb</strong> files but there are some files that have some size what are those files?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Paul R		</title>
		<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-216012</link>

		<dc:creator><![CDATA[Paul R]]></dc:creator>
		<pubDate>Wed, 16 Jul 2014 19:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=4561#comment-216012</guid>

					<description><![CDATA[Minor issue - it&#039;s &lt;code&gt;/proc/consoles&lt;/code&gt; (with an &lt;strong&gt;s&lt;/strong&gt; at the end).

Also you might want to add mention of &lt;code&gt;/proc/self&lt;/code&gt; and why this happens:
&lt;pre&gt;
$ cd /proc/self
$ readlink -e .
/proc/7803
$ readlink -e /proc/self
/proc/11257
&lt;/pre&gt;]]></description>
			<content:encoded><![CDATA[<p>Minor issue &#8211; it&#8217;s <code>/proc/consoles</code> (with an <strong>s</strong> at the end).</p>
<p>Also you might want to add mention of <code>/proc/self</code> and why this happens:</p>
<pre>
$ cd /proc/self
$ readlink -e .
/proc/7803
$ readlink -e /proc/self
/proc/11257
</pre>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ricky Tan		</title>
		<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-62902</link>

		<dc:creator><![CDATA[Ricky Tan]]></dc:creator>
		<pubDate>Tue, 29 Oct 2013 08:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=4561#comment-62902</guid>

					<description><![CDATA[Thanks for the info sir.. very much appreciated]]></description>
			<content:encoded><![CDATA[<p>Thanks for the info sir.. very much appreciated</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rob Krul		</title>
		<link>https://www.tecmint.com/exploring-proc-file-system-in-linux/comment-page-1/#comment-61806</link>

		<dc:creator><![CDATA[Rob Krul]]></dc:creator>
		<pubDate>Sat, 26 Oct 2013 09:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=4561#comment-61806</guid>

					<description><![CDATA[Depending on what type of hardware you have, you can get a lot of information in some of the &lt;code&gt;/proc&lt;/code&gt; files. Since you were asking specifically about your video card, you can run:
&lt;pre&gt;
$ cat /proc/pci
&lt;/pre&gt;
If it is using an ISA slot, you can run the following:
&lt;pre&gt;
$ cat /proc/isapnp
&lt;/pre&gt;
If you are looking for your hard drive info:
&lt;pre&gt;
$ cat /proc/scsi/scsi
&lt;/pre&gt;
The man page of &lt;code&gt;/proc/&lt;/code&gt; will give you plenty of info about any file in the &lt;code&gt;/proc&lt;/code&gt; directory.

Of course, there are easier ways to obtain this information, and utilities that are much more script-friendly. lshw is the first:
&lt;pre&gt;
$ lshw -class disk
&lt;/pre&gt;
There is also hwinfo:
&lt;pre&gt;
$ hwinfo --disk
&lt;/pre&gt;
And the very script-friendly lsblk:
&lt;pre&gt;
$ lsblk -io KNAME,TYPE,SIZE,MODEL
&lt;/pre&gt;
All three of those utilities are available through &lt;strong&gt;apt&lt;/strong&gt; or &lt;strong&gt;yum&lt;/strong&gt;.]]></description>
			<content:encoded><![CDATA[<p>Depending on what type of hardware you have, you can get a lot of information in some of the <code>/proc</code> files. Since you were asking specifically about your video card, you can run:</p>
<pre>
$ cat /proc/pci
</pre>
<p>If it is using an ISA slot, you can run the following:</p>
<pre>
$ cat /proc/isapnp
</pre>
<p>If you are looking for your hard drive info:</p>
<pre>
$ cat /proc/scsi/scsi
</pre>
<p>The man page of <code>/proc/</code> will give you plenty of info about any file in the <code>/proc</code> directory.</p>
<p>Of course, there are easier ways to obtain this information, and utilities that are much more script-friendly. lshw is the first:</p>
<pre>
$ lshw -class disk
</pre>
<p>There is also hwinfo:</p>
<pre>
$ hwinfo --disk
</pre>
<p>And the very script-friendly lsblk:</p>
<pre>
$ lsblk -io KNAME,TYPE,SIZE,MODEL
</pre>
<p>All three of those utilities are available through <strong>apt</strong> or <strong>yum</strong>.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
