<?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: Solution: How to Create a man page?</title>
	<atom:link href="https://www.emblogic.com/blog/12/solution-how-to-create-a-man-page/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.emblogic.com/blog/12/solution-how-to-create-a-man-page/</link>
	<description>Embedded System and ARM Training</description>
	<lastBuildDate>Mon, 07 Oct 2013 04:00:03 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>By: swapnil kamble</title>
		<link>https://www.emblogic.com/blog/12/solution-how-to-create-a-man-page/#comment-3077</link>
		<dc:creator><![CDATA[swapnil kamble]]></dc:creator>
		<pubDate>Sat, 24 Nov 2012 09:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://emblogic.org/blog/?p=1436#comment-3077</guid>
		<description><![CDATA[i have writing the manual pages.]]></description>
		<content:encoded><![CDATA[<p>i have writing the manual pages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Praveen Joshi</title>
		<link>https://www.emblogic.com/blog/12/solution-how-to-create-a-man-page/#comment-3045</link>
		<dc:creator><![CDATA[Praveen Joshi]]></dc:creator>
		<pubDate>Wed, 21 Nov 2012 09:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://emblogic.org/blog/?p=1436#comment-3045</guid>
		<description><![CDATA[1---&gt;&gt;&gt; It replaces your original file with a compressed version unlike tar which shows both compress and original file and hence memory occupied is very less.

2----&gt;&gt;&gt;  You can tell gzip to use different levels of compression with the flag to use compression fast and efficient.

3---&gt;&gt;&gt;  In  case of damage to one member of a .gz file, other members can still be recovered.]]></description>
		<content:encoded><![CDATA[<p>1&#8212;&gt;&gt;&gt; It replaces your original file with a compressed version unlike tar which shows both compress and original file and hence memory occupied is very less.</p>
<p>2&#8212;-&gt;&gt;&gt;  You can tell gzip to use different levels of compression with the flag to use compression fast and efficient.</p>
<p>3&#8212;&gt;&gt;&gt;  In  case of damage to one member of a .gz file, other members can still be recovered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamran Ali</title>
		<link>https://www.emblogic.com/blog/12/solution-how-to-create-a-man-page/#comment-517</link>
		<dc:creator><![CDATA[Kamran Ali]]></dc:creator>
		<pubDate>Fri, 13 Jan 2012 06:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://emblogic.org/blog/?p=1436#comment-517</guid>
		<description><![CDATA[When we consider manual pages in Linux, if one goes to the /usr/share/man directory, he/she would find that there exists a few directories. We consider the directories named man1 to man9, which contain man pages in Linux. What are these directories and why are they named man1 to man9? Each directory consist of manual pages, but the directory section number, that is the numerical after the word &quot;man&quot; decides what the directory contains, and who can access the man pages inside it and can invoke it accordingly. In other words the &quot;section numbers&quot; define the accessibility of manual pages in Linux. The most common sections under Linux, and their human readable names, are:
Section 	The human readable name
1 	User commands that may be started by everyone.
2 	System calls, that is, functions provided by the kernel.
3 	Subroutines, that is, library functions.
4 	Devices, that is, special files in the /dev directory.
5 	File format descriptions, e.g. /etc/passwd.
6 	Games, self-explanatory.
7 	Miscellaneous, e.g. macro packages, conventions.
8 	System administration tools that only root can execute.
9 	Another (Linux specific) place for kernel routine documentation.

Thus, when we created our custom manual page for our application catapp, and when installing it in the proper location we muct make sure it installed in the directory man1. The reason being we want the manual page for catapp to be accessible by all.]]></description>
		<content:encoded><![CDATA[<p>When we consider manual pages in Linux, if one goes to the /usr/share/man directory, he/she would find that there exists a few directories. We consider the directories named man1 to man9, which contain man pages in Linux. What are these directories and why are they named man1 to man9? Each directory consist of manual pages, but the directory section number, that is the numerical after the word &#8220;man&#8221; decides what the directory contains, and who can access the man pages inside it and can invoke it accordingly. In other words the &#8220;section numbers&#8221; define the accessibility of manual pages in Linux. The most common sections under Linux, and their human readable names, are:<br />
Section 	The human readable name<br />
1 	User commands that may be started by everyone.<br />
2 	System calls, that is, functions provided by the kernel.<br />
3 	Subroutines, that is, library functions.<br />
4 	Devices, that is, special files in the /dev directory.<br />
5 	File format descriptions, e.g. /etc/passwd.<br />
6 	Games, self-explanatory.<br />
7 	Miscellaneous, e.g. macro packages, conventions.<br />
8 	System administration tools that only root can execute.<br />
9 	Another (Linux specific) place for kernel routine documentation.</p>
<p>Thus, when we created our custom manual page for our application catapp, and when installing it in the proper location we muct make sure it installed in the directory man1. The reason being we want the manual page for catapp to be accessible by all.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
