<?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>The Linux Daily &#187; Tips and Tricks</title>
	<atom:link href="http://www.thelinuxdaily.com/category/tips-and-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thelinuxdaily.com</link>
	<description>Tutorials, Guides, Tips, and Tricks from Everyday Experiences</description>
	<lastBuildDate>Thu, 02 Sep 2010 21:38:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Using &#8216;aspell&#8217; to Spellcheck a File via Terminal</title>
		<link>http://www.thelinuxdaily.com/2010/08/using-aspell-to-spellcheck-a-file-via-terminal/</link>
		<comments>http://www.thelinuxdaily.com/2010/08/using-aspell-to-spellcheck-a-file-via-terminal/#comments</comments>
		<pubDate>Fri, 13 Aug 2010 14:00:58 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[aspell]]></category>
		<category><![CDATA[CLI]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[spellcheck]]></category>
		<category><![CDATA[terminal]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=2053</guid>
		<description><![CDATA[The utility aspell (along with others such as spell and hunspell), can be used to spellcheck a file from the terminal. You can also specify a file &#8220;mode&#8221; for which to scan. Modes include plain text, HTML, sgml, LaTeX, and others. Usage Example To list all of the spelling mistakes of the file &#8220;testfile.txt&#8221;, use: [...]]]></description>
			<content:encoded><![CDATA[<p>The utility <a href="http://linux.die.net/man/1/aspell"><code>aspell</code></a> (along with others such as <code>spell</code> and <code>hunspell</code>), can be used to spellcheck a file from the terminal.  You can also specify a file &#8220;mode&#8221; for which to scan.  Modes include plain text, HTML, sgml, LaTeX, and others.</p>
<p><b>Usage Example</b><br />
To list all of the spelling mistakes of the file &#8220;testfile.txt&#8221;, use:</p>
<pre class="brush: bash;">
aspell list &lt; textfile.txt
</pre>
<p>To list all of the spelling mistakes of the HTML document &#8220;testpage.html&#8221;, use:</p>
<pre class="brush: bash;">
aspell --mode=html list &lt; testpage.html
</pre>
<p>As always, be sure to take a look at the <a href="http://linux.die.net/man/1/aspell">man pages</a> for more information.  Keep in mind that certain distributions may not come with <code>aspell</code> pre-installed, so you may need to use the package manager to install it (ie. <code>apt-get install aspell</code> or <code>yum install aspell</code>).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/08/using-aspell-to-spellcheck-a-file-via-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setup a Universal User Profile with &#8216;/etc/profile.d/custom.sh&#8217;</title>
		<link>http://www.thelinuxdaily.com/2010/08/setup-a-universal-user-profile-with-etcprofile-dcustom-sh/</link>
		<comments>http://www.thelinuxdaily.com/2010/08/setup-a-universal-user-profile-with-etcprofile-dcustom-sh/#comments</comments>
		<pubDate>Thu, 12 Aug 2010 14:00:01 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[alias]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[profile]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=2012</guid>
		<description><![CDATA[It&#8217;s fairly common to edit the /home/user/.bash_profile file to setup a custom environment, such as alias and startup applications, for user, but what if you wanted that profile to be the same for all users (including root). The best way is to use a custom script that resides in the /etc/profile.d/ directory. This process is [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s fairly common to edit the <em>/home/user/.bash_profile</em> file to setup a custom environment, such as alias and startup applications, for <code>user</code>, but what if you wanted that profile to be the same for all users (including root).  The best way is to use a custom script that resides in the <em>/etc/profile.d/</em> directory.  This process is described briefly in <em>/etc/bashrc</em>:</p>
<pre class="brush: plain;">
# /etc/bashrc

# System wide functions and aliases
# Environment stuff goes in /etc/profile

# It's NOT good idea to change this file unless you know what you
# are doing. Much better way is to create custom.sh shell script in
# /etc/profile.d/ to make custom changes to environment. This will
# prevent need for merging in future updates.
</pre>
<p>Here is a quick example for taking advantage of this hook which assigns a simple alias.  First, you must setup <em>/etc/profile.d/custom.sh</em>:</p>
<pre class="brush: bash;">
/etc/profile.d/custom.sh
chmod +x /etc/profile.d/custom.sh
</pre>
<p>Second, you must created the contents of <em>/etc/profile.d/custom.sh</em>:</p>
<pre class="brush: bash;">
#!/bin/sh

alias ls='ls -lah'
</pre>
<p>Third, simply log out and then back in again.  You&#8217;ll notice the changes.  You can verify this particular example by using the <code>alias</code> command:</p>
<pre class="brush: bash;">
$ alias | tail -n1
alias ls='ls -lah'
$
</pre>
<p>Of course, you&#8217;ll want to take what you&#8217;ve learned above and run with your own script suited to your needs.  I hope this has helped you achieve your goal of creating a universal profile for all users on the system.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/08/setup-a-universal-user-profile-with-etcprofile-dcustom-sh/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To:  Get .rar Support in Fedora 13 [Two-Liner Command]</title>
		<link>http://www.thelinuxdaily.com/2010/08/how-to-get-rar-support-in-fedora-13-two-liner-command/</link>
		<comments>http://www.thelinuxdaily.com/2010/08/how-to-get-rar-support-in-fedora-13-two-liner-command/#comments</comments>
		<pubDate>Tue, 10 Aug 2010 14:00:41 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[guide]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[rar]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=2034</guid>
		<description><![CDATA[Let&#8217;s get right to the point. Here&#8217;s how to install .rar support in Fedora 13: 1.) Open the terminal 2.) Copy/Paste the following into terminal su -c 'rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm' su -c 'yum install -y rar unrar' 3.) Refer to the following pages for usage Create/Compress/Archive Almost Any File in Linux (tar, tar.gz, tar.bz2, [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s get right to the point.  Here&#8217;s how to install .rar support in Fedora 13:</p>
<p><b>1.) Open the terminal</b><br />
<b>2.) Copy/Paste the following into terminal</b></p>
<pre class="brush: bash;">
su -c 'rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'
su -c 'yum install -y rar unrar'
</pre>
<p><b>3.) Refer to the following pages for usage</b><br />
<a href="http://www.thelinuxdaily.com/2010/02/createcompressarchive-almost-any-file-in-linux-tar-tar-gz-tar-bz2-gz-bz-zip-7z-rar-etc/">Create/Compress/Archive Almost Any File in Linux (tar, tar.gz, tar.bz2, gz, bz, zip, 7z, rar, etc…)</a><br />
<a href="http://www.thelinuxdaily.com/2010/01/extractunarchive-almost-any-file-in-linux-tar-tar-gz-tar-bz2-gz-bz-zip-7z-rar-etc/">Extract/Uncompress/Unarchive Almost Any File in Linux (tar, tar.gz, tar.bz2, gz, bz, zip, 7z, rar, etc…)</a></p>
<p><b>P.S.</b><br />
For those die-hard one-liner fans out there, you can use the following instead:</p>
<pre class="brush: bash;">
su -c 'rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm &amp;&amp;  yum install -y rar unrar'
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/08/how-to-get-rar-support-in-fedora-13-two-liner-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use &#8216;sync&#8217; Tool to Commit Changes in Embedded Linux</title>
		<link>http://www.thelinuxdaily.com/2010/07/use-sync-tool-to-commit-changes-in-embedded-linux/</link>
		<comments>http://www.thelinuxdaily.com/2010/07/use-sync-tool-to-commit-changes-in-embedded-linux/#comments</comments>
		<pubDate>Fri, 30 Jul 2010 14:00:07 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[commit]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[flash]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[sync]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=2006</guid>
		<description><![CDATA[When you&#8217;re working in an embedded Linux environment, liberal use of the sync command can be a headache saver. Here&#8217;s the thing: in most embedded systems, your OS will be running from something like an SD card or flash and you may be subject to unexpected power loss. When you&#8217;re editing files or making changes [...]]]></description>
			<content:encoded><![CDATA[<p>When you&#8217;re working in an embedded Linux environment, liberal use of the <a href="http://linux.die.net/man/2/sync"><code>sync</code></a> command can be a headache saver.  Here&#8217;s the thing:  in most embedded systems, your OS will be running from something like an SD card or flash and you may be subject to unexpected power loss.  When you&#8217;re editing files or making changes in the filesystem, some of these edits and/or changes are only written to buffer cache, not the flash disk (not yet anyways).  <code>sync</code> will force the system to commit the buffer cache to the disk.</p>
<p>As always, be sure to check out the <a href="http://linux.die.net/man/2/sync">man page</a> for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/07/use-sync-tool-to-commit-changes-in-embedded-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use perldoc to View Perl Manual/Documentation</title>
		<link>http://www.thelinuxdaily.com/2010/07/use-perldoc-to-view-perl-manualdocumentation/</link>
		<comments>http://www.thelinuxdaily.com/2010/07/use-perldoc-to-view-perl-manualdocumentation/#comments</comments>
		<pubDate>Thu, 29 Jul 2010 14:00:47 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[doc]]></category>
		<category><![CDATA[man]]></category>
		<category><![CDATA[perl]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1978</guid>
		<description><![CDATA[Simply put, perldoc is the man page of perl applications. Use it and use it often when dealing with perl utilities. For example: perldoc open Reveals&#8230; System::Library::Perl:User.Contributed PeSystem::Library::Perl::5.8.8::open(3) NAME open − perl pragma to set default PerlIO layers for input and output SYNOPSIS use open IN =&#62; &#34;:crlf&#34;, OUT =&#62; &#34;:bytes&#34;; use open OUT =&#62; [...]]]></description>
			<content:encoded><![CDATA[<p>Simply put, <code>perldoc</code> is the <code>man</code> page of perl applications.  Use it and use it often when dealing with perl utilities.  For example:</p>
<pre class="brush: bash;">perldoc open</pre>
<p>Reveals&#8230;</p>
<pre class="brush: plain;">
System::Library::Perl:User.Contributed PeSystem::Library::Perl::5.8.8::open(3)

NAME
       open − perl pragma to set default PerlIO layers for input and output

SYNOPSIS
           use open IN  =&gt; &quot;:crlf&quot;, OUT =&gt; &quot;:bytes&quot;;
           use open OUT =&gt; ’:utf8’;
           use open IO  =&gt; &quot;:encoding(iso−8859−7)&quot;;

           use open IO  =&gt; ’:locale’;

           use open ’:utf8’;
           use open ’:locale’;
           use open ’:encoding(iso−8859−7)’;

           use open ’:std’;

DESCRIPTION
       Full‐fledged support for I/O layers is now implemented provided Perl is
       configured to use PerlIO as its IO system (which is now the default).
       ...
       ...
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/07/use-perldoc-to-view-perl-manualdocumentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Get Weather Report from Terminal</title>
		<link>http://www.thelinuxdaily.com/2010/07/get-weather-report-from-terminal/</link>
		<comments>http://www.thelinuxdaily.com/2010/07/get-weather-report-from-terminal/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 14:00:12 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[CLI]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[terminal]]></category>
		<category><![CDATA[weather]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1971</guid>
		<description><![CDATA[I&#8217;ve been on a kick recently about doing everything in the terminal and I became excited about the possibility of doing it through the terminal. I was excited until my little research on the subject revealed that this horse has been beaten left and right and up and down and diagonally. There were so many [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been on a kick recently about doing everything in the terminal and I became excited about the possibility of doing it through the terminal.  I was excited until my little research on the subject revealed that this horse has been beaten left and right and up and down and diagonally.  There were so many different ways of doing it, I sorta lost the urge to create a post about it.  Well, here I am anyways listing the ones I found to be the most interesting.  Check &#8216;em out if you&#8217;re interested&#8230;</p>
<p><a href="http://fungi.yuggoth.org/weather/">http://fungi.yuggoth.org/weather/</a><br />
<a href="http://linuxshellaccount.blogspot.com/2008/09/bash-script-to-get-weather-forecasts.html">http://linuxshellaccount.blogspot.com/2008/09/bash-script-to-get-weather-forecasts.html</a></p>
<pre class="brush: bash;">telnet rainmaker.wunderground.com</pre>
<pre class="brush: bash;">curl http://weather.noaa.gov/pub/data/forecasts/city/state/city.txt</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/07/get-weather-report-from-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Network Connection with &#8216;tcpdump&#8217; and &#8216;arp&#8217;</title>
		<link>http://www.thelinuxdaily.com/2010/07/troubleshooting-network-connection-with-tcpdump-and-arp/</link>
		<comments>http://www.thelinuxdaily.com/2010/07/troubleshooting-network-connection-with-tcpdump-and-arp/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 14:00:13 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[arp]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ping]]></category>
		<category><![CDATA[tcpdump]]></category>
		<category><![CDATA[troubleshoot]]></category>
		<category><![CDATA[usage]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1982</guid>
		<description><![CDATA[A quick and easy way to troubleshoot network connections in an embedded Linux environment is to use the ping, tcpdump, and arp commands. This will allow you to see what might be happening with the traffic on your network at the packet level. Once scenario would be that you&#8217;re not getting a successful ping between [...]]]></description>
			<content:encoded><![CDATA[<p>A quick and easy way to troubleshoot network connections in an embedded Linux environment is to use the <code>ping</code>, <code><a href="http://linux.die.net/man/8/tcpdump">tcpdump</a></code>, and <code><a href="http://linux.die.net/man/8/arp">arp</a></code> commands.  This will allow you to see what might be happening with the traffic on your network at the packet level.  Once scenario would be that you&#8217;re not getting a successful ping between two computers on the network.  All reason tells you that it should be working, but maybe there&#8217;s something wrong at the driver level?  To start troubleshooting, fire up <code>tcpdump</code> on the box being pinged (ip: 192.168.1.100) and specify the network interface and IP address of the machine doing the pinging (ip: 192.168.1.101):</p>
<pre class="brush: bash;">tcpdump -i eth0 host 192.168.1.101</pre>
<p>Now, run the ping test:</p>
<pre class="brush: bash;">ping 192.168.1.100</pre>
<p>At this point, if you get an output from <code>tcpdump</code>, you&#8217;ll know that the packet has made its way to the target machine (192.168.1.100).  The next step would be to see if you ever received an acknowledgment from the target machine.  Run <code>arp</code> on the machine doing the pinging (192.168.1.101): </p>
<pre class="brush: bash;">arp -an</pre>
<p>If you see something like <code>? (192.168.1.112) at (incomplete) on en1 [ethernet]</code>, that means you never got an acknowledgment back from the target machine (192.168.1.100).</p>
<p>At this point in this scenario, we would start to dive into what could be wrong.  In this particular situation, it was a driver issue with assigning a MAC address to the interface.</p>
<p>This is just one scenario to get you familiar with how to use <code>tcpdump</code> and <code>arp</code> and gather information about the networking issue.  Please refer to the utility man pages for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/07/troubleshooting-network-connection-with-tcpdump-and-arp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check For Empty Directories Using &#8216;find&#8217; Shell Command</title>
		<link>http://www.thelinuxdaily.com/2010/06/check-for-empty-directories-using-find-shell-command/</link>
		<comments>http://www.thelinuxdaily.com/2010/06/check-for-empty-directories-using-find-shell-command/#comments</comments>
		<pubDate>Tue, 29 Jun 2010 14:00:55 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[directory]]></category>
		<category><![CDATA[empty]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[remove]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[zero]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1947</guid>
		<description><![CDATA[find /path/to/directory -type d -empty -exec echo {} \; I think it&#8217;s easy to get the idea based on the example above, but just in case you need inspiration, you could automatically remove these empty directories with the following (Careful! This uses &#8216;-rf&#8217; flag which shows no warnings or mercy!): find /path/to/directory -type d -empty [...]]]></description>
			<content:encoded><![CDATA[<pre class="brush: bash;">
find /path/to/directory -type d -empty -exec echo {} \;
</pre>
<p>I think it&#8217;s easy to get the idea based on the example above, but just in case you need inspiration, you could automatically remove these empty directories with the following (Careful!  This uses &#8216;-rf&#8217; flag which shows no warnings or mercy!):</p>
<pre class="brush: bash;">
find /path/to/directory -type d -empty -exec rm -rf {} \;
</pre>
<p>Check out some additional methods here:</p>
<p>http://www.cyberciti.biz/faq/linux-unix-shell-check-if-directory-empty/</p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/06/check-for-empty-directories-using-find-shell-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prevent Time-Based &#8216;fsck&#8217; Checks on Root Partition with &#8216;tune2fs&#8217;</title>
		<link>http://www.thelinuxdaily.com/2010/06/prevent-time-based-fsck-checks-on-root-partition-with-tune2fs/</link>
		<comments>http://www.thelinuxdaily.com/2010/06/prevent-time-based-fsck-checks-on-root-partition-with-tune2fs/#comments</comments>
		<pubDate>Mon, 21 Jun 2010 14:00:12 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[disable]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[rtc]]></category>
		<category><![CDATA[tune2fs]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1924</guid>
		<description><![CDATA[In an embedded system without a battery backed real time clock (RTC), a time-based &#8216;fsck&#8217; check can be quite annoying. To disable the time-based check, use the tune2fs command on the drive containing the root partition like so: tune2fs -i 0 /dev/&#60;device node&#62; There&#8217;s more information here at this link for those of you interested: [...]]]></description>
			<content:encoded><![CDATA[<p>In an embedded system without a battery backed real time clock (RTC), a time-based &#8216;fsck&#8217; check can be quite annoying.  To disable the time-based check, use the <code>tune2fs</code> command on the drive containing the root partition like so:</p>
<pre class="brush: bash;">
tune2fs -i 0 /dev/&lt;device node&gt;
</pre>
<p>There&#8217;s more information here at this link for those of you interested:<br />
<a href="http://serverfault.com/questions/28343/will-my-system-fsck-when-i-reboot">http://serverfault.com/questions/28343/will-my-system-fsck-when-i-reboot</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/06/prevent-time-based-fsck-checks-on-root-partition-with-tune2fs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Minimize Linux Serial Port Latency</title>
		<link>http://www.thelinuxdaily.com/2010/06/minimize-linux-serial-port-latency/</link>
		<comments>http://www.thelinuxdaily.com/2010/06/minimize-linux-serial-port-latency/#comments</comments>
		<pubDate>Wed, 16 Jun 2010 14:00:45 +0000</pubDate>
		<dc:creator>Derek@TheDailyLinux</dc:creator>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[10ms]]></category>
		<category><![CDATA[delay]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[latency]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[real time]]></category>
		<category><![CDATA[serial]]></category>

		<guid isPermaLink="false">http://www.thelinuxdaily.com/?p=1925</guid>
		<description><![CDATA[When using Linux serial ports, the tty has a default 5 to 10ms latency time built-in. To drop this, use the low_latency parameter of setserial. This is useful for getting a more real-time response in Linux serial ports. Be sure to check out the man pages for more information. Minimize the receive latency of the [...]]]></description>
			<content:encoded><![CDATA[<p>When using Linux serial ports, the tty has a default 5 to 10ms latency time built-in.  To drop this, use the <code>low_latency</code> parameter of <code><a href="http://linux.die.net/man/8/setserial">setserial</a></code>.  This is useful for getting a more real-time response in Linux serial ports.  Be sure to check out the man pages for more information.</p>
<blockquote><p>
Minimize the receive latency of the serial device at the cost of greater CPU utilization. (Normally there is an average of 5-10ms latency before characters are handed off to the line discpline to minimize overhead.) This is off by default, but certain real-time applications may find this useful.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.thelinuxdaily.com/2010/06/minimize-linux-serial-port-latency/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
