<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SupportSages &#187; color codes</title>
	<atom:link href="http://www.supportsages.com/blog/tag/color-codes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supportsages.com/blog</link>
	<description>Technical Support and Server Management : Musings in the fox hole.</description>
	<lastBuildDate>Thu, 05 Jan 2012 03:05:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Chapter 8 File types in Linux.</title>
		<link>http://www.supportsages.com/blog/2009/05/chapter-8-file-types-in-linux/</link>
		<comments>http://www.supportsages.com/blog/2009/05/chapter-8-file-types-in-linux/#comments</comments>
		<pubDate>Fri, 15 May 2009 05:43:46 +0000</pubDate>
		<dc:creator>Fabian</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Howtos]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[characters]]></category>
		<category><![CDATA[color codes]]></category>
		<category><![CDATA[file types]]></category>
		<category><![CDATA[linux file system]]></category>
		<category><![CDATA[paths]]></category>
		<category><![CDATA[permissions]]></category>

		<guid isPermaLink="false">http://www.supportsages.com/blog/?p=241</guid>
		<description><![CDATA[<p style="text-align: left;"><span class="QUOTE">" On a UNIX system, everything is a file, if something is not a file, it is a process. "Most of the files in linux , say regular files have </span>normal data, eg some text files, executable files/programs, input and output to or from a program and so on.</p>
<p style="text-align: left;"><strong>File Types:-</strong></p>

<p style="text-align: left;">Ordinary -&#62; text, ./binary, .images, html and conf files
Directory -&#62; Also known as folders
Special/Device File -&#62;
Hardware Devices --&#62; /dev/lp0 , /dev/hda1, /dev/sda1, /dev/fd0
Logical Devices --&#62; /dev/null , /dev/zero
Links -  Hardlinks and SoftLinks + Difference of Hardlinks &#38; SoftLinks
Sockets - A socket refers to a ...]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;"><span class="QUOTE">&#8221; On a UNIX system, everything is a file, if something is not a file, it is a process. &#8220;Most of the files in linux , say regular files have </span>normal data, eg some text files, executable files/programs, input and output to or from a program and so on.</p>
<p style="text-align: left;"><strong>File Types:-</strong></p>
<p style="text-align: left;">Ordinary -&gt; text, ./binary, .images, html and conf files<br />
Directory -&gt; Also known as folders<br />
Special/Device File -&gt;<br />
Hardware Devices &#8211;&gt; /dev/lp0 , /dev/hda1, /dev/sda1, /dev/fd0<br />
Logical Devices &#8211;&gt; /dev/null , /dev/zero<br />
Links -  Hardlinks and SoftLinks + Difference of Hardlinks &amp; SoftLinks<br />
Sockets &#8211; A socket refers to a special file with which communication between locally running processes happens<br />
FIFOs Or Named Pipes &#8211; act more or less like sockets and form a way for processes to communicate with each other, without using network socket semantics</p>
<p style="text-align: left;">FIFO is a one way communication pipe, while Unix domain sockets (otherwise called as IPC Sockets) are two way communication pipes</p>
<blockquote style="text-align: left;"><p># ls -l  /dev/console<br />
crw&#8212;&#8212;- 1 root root 5, 1 2008-03-30 17:45 /dev/console</p></blockquote>
<p style="text-align: left;">-    Regular file<br />
d    Directory<br />
l    Link<br />
c    Special file<br />
s    Socket<br />
p    Named pipe</p>
<p style="text-align: left;">The maximum number of characters for a file name is 255<br />
Use backslash for special characters<br />
CaseSensiTivty for files : The Files in linux are case sensitive. File a and file A are two different files.</p>
<p style="text-align: left;">Color codes:-</p>
<p style="text-align: left;">blue    directories<br />
red    compressed archives<br />
white    text files<br />
pink    images<br />
cyan    links<br />
yellow    devices<br />
green    executables<br />
flashing red    broken links</p>
<blockquote style="text-align: left;"><p><img class="aligncenter size-full wp-image-242" title="linux-file-permissions-ls-color" src="http://www.supportsages.com/blog/wp-content/uploads/2009/05/linux-file-permissions-ls-color.png" alt="linux-file-permissions-ls-color" width="447" height="263" /></p></blockquote>
<p style="text-align: left;"><strong>Suffix Schemes:-</strong></p>
<p style="text-align: left;">nothing    regular file<br />
/    directory<br />
*    executable file<br />
@    link<br />
=    socket<br />
|    named pipe</p>
<p style="text-align: left;"><strong>PathNames:-</strong></p>
<p style="text-align: left;">Relative Path :- The relative path is the path to the   destination file/directory from the current location (pwd). eg : cd ../var/www</p>
<p style="text-align: left;">Absolute path :- The relative path is the full path to the destination file/directory from the &#8216;/&#8217;. eg : vi /home/indisages/files<br />
The maximum length of PathNames including slashes is  4096</p>
<p style="text-align: left;"><strong>Permissions:- </strong>The behavior of a file/directory to a particular user totally depends on the permission assigned to it.</p>
<p style="text-align: left;">rwx and octal/numerical representations<br />
chmod<br />
chgrp<br />
umask for directories and files</p>
<p style="text-align: left;"><strong>Special Modes in Permission:-</strong></p>
<p style="text-align: left;">Sticky bit &#8211; t, eg &#8211;&gt; ls -ld /tmp<br />
Set UID &#8211; When this mode is set on an executable file, it will run with the user and group permissions on the file instead of with those of the user issuing the command, thus giving access to system resources. eg : /usr/bin/passwd and /etc/passwd<br />
Set GID &#8211; Same as SUID, but applies to group. eg : ls -l /usr/bin/write /usr/bin/bsd-write /dev/pts/1</p>
<div class="tweetthis" style="text-align:left;"><p> <a  class="tt" href="http://twitter.com/home/?status=Chapter+8+File+types+in+Linux.+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F241" title="Post to Twitter"><img class="nothumb" src="http://www.supportsages.com/blog/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter3.png" alt="Post to Twitter" /></a> <a  class="tt" href="http://twitter.com/home/?status=Chapter+8+File+types+in+Linux.+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F241" title="Post to Twitter">Tweet This Post</a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.supportsages.com/blog/2009/05/chapter-8-file-types-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

