<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Joey's Linux Scams</title>
	<atom:link href="http://sartorius.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://sartorius.wordpress.com</link>
	<description>Just another WordPress.com weblog about Linux</description>
	<lastBuildDate>Mon, 28 Sep 2009 07:02:04 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Samba setup by oes tsetnoc</title>
		<link>http://sartorius.wordpress.com/2006/12/13/samba-setup/#comment-260</link>
		<dc:creator>oes tsetnoc</dc:creator>
		<pubDate>Mon, 28 Sep 2009 07:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://sartorius.wordpress.com/2006/12/13/samba-setup/#comment-260</guid>
		<description>Hi, Just like to tell you that this piece of info is one quick to the point, no nonsense, workable and effective way to have directories shared in Linux as fast as possible. It worked for me and thank you for the effort. Keep up the good work.</description>
		<content:encoded><![CDATA[<p>Hi, Just like to tell you that this piece of info is one quick to the point, no nonsense, workable and effective way to have directories shared in Linux as fast as possible. It worked for me and thank you for the effort. Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing, setting up, and using Greasemonkey by Dataquester</title>
		<link>http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-257</link>
		<dc:creator>Dataquester</dc:creator>
		<pubDate>Tue, 17 Mar 2009 14:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-257</guid>
		<description>Great info, i appreciate the fact that u gave info about linux thing.</description>
		<content:encoded><![CDATA[<p>Great info, i appreciate the fact that u gave info about linux thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ripping DVD audio to ogg in Ubuntu by J.B. Nicholson-Owens</title>
		<link>http://sartorius.wordpress.com/2006/08/30/ripping-dvd-audio-to-ogg-in-ubuntu/#comment-253</link>
		<dc:creator>J.B. Nicholson-Owens</dc:creator>
		<pubDate>Wed, 31 Dec 2008 19:38:29 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/ripping-dvd-audio-to-ogg-in-ubuntu/#comment-253</guid>
		<description>I guess I should have simplified that a bit before posting.

The jist of my first post applies to both of the for loops, not just the audio encoding: use find and xargs for big jobs or jobs where you&#039;re dealing with arbitrary numbers of objects.

The task here is twofold:

1. Do the entire movie file -&gt; Ogg Vorbis audio file transcoding completely and correctly for one file.  Make a script for this.  Later on, consider enhancing this script with more features (deleting temp files, logging, etc.).

2. Call the aforementioned script with xargs as I illustrated before:

  find . -maxdepth 1 -iname &#039;*.avi&#039; -print0 &#124; xargs -0I{} /path/to/script &#039;{}&#039;

and let the computer work for a long time doing all the transcoding, leaving Ogg Vorbis files alongside the corresponding movie files.

The -I option on xargs lets you position the argument where you wish.

find and xargs are a far better way to make this scale up than using for loops in the shell (I like GNU find and GNU xargs because they&#039;re free software and ever so flexible).</description>
		<content:encoded><![CDATA[<p>I guess I should have simplified that a bit before posting.</p>
<p>The jist of my first post applies to both of the for loops, not just the audio encoding: use find and xargs for big jobs or jobs where you&#8217;re dealing with arbitrary numbers of objects.</p>
<p>The task here is twofold:</p>
<p>1. Do the entire movie file -&gt; Ogg Vorbis audio file transcoding completely and correctly for one file.  Make a script for this.  Later on, consider enhancing this script with more features (deleting temp files, logging, etc.).</p>
<p>2. Call the aforementioned script with xargs as I illustrated before:</p>
<p>  find . -maxdepth 1 -iname &#8216;*.avi&#8217; -print0 | xargs -0I{} /path/to/script &#8216;{}&#8217;</p>
<p>and let the computer work for a long time doing all the transcoding, leaving Ogg Vorbis files alongside the corresponding movie files.</p>
<p>The -I option on xargs lets you position the argument where you wish.</p>
<p>find and xargs are a far better way to make this scale up than using for loops in the shell (I like GNU find and GNU xargs because they&#8217;re free software and ever so flexible).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ripping DVD audio to ogg in Ubuntu by J.B. Nicholson-Owens</title>
		<link>http://sartorius.wordpress.com/2006/08/30/ripping-dvd-audio-to-ogg-in-ubuntu/#comment-252</link>
		<dc:creator>J.B. Nicholson-Owens</dc:creator>
		<pubDate>Wed, 31 Dec 2008 19:11:32 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/ripping-dvd-audio-to-ogg-in-ubuntu/#comment-252</guid>
		<description>If you have a lot of WAV files to encode, a for loop will fail (too many arguments).  Also, the for loop will not descend recursively into subdirectories.  This could be handy if you have an entire jukebox you want to convert and everything is arranged in directories (perhaps you just ripped your CD collection into a series of directories named after artists and CD titles).

Fortunately find with xargs scales up far better and can handle the recursion without problem:

find . -maxdepth 1 -iname &#039;*.wav&#039; -print0 &#124; xargs -0 oggenc -q6

You&#039;ll notice I didn&#039;t bother computing the new name (&quot;foo.wav&quot; becomes &quot;foo.ogg&quot;).  This is because oggenc already encodes &quot;foo.wav&quot; as &quot;foo.ogg&quot;.

I used -print0 and -0 on xargs to properly handle pathnames with spaces.

It&#039;s trivial to change this command to do as you wish.  You can have the WAV file removed after successful encoding.  For this, you might want to make a shell script that only handles one file (specified via argument), checks oggenc&#039;s return code, and the existence of the output file before removing the source WAV file.  Then call that script from xargs instead of calling oggenc directly.  I leave that as an exercise for the reader.

If you want the recursion to find all *.wav files starting from the current directory, delete &quot;-maxdepth 1&quot;.</description>
		<content:encoded><![CDATA[<p>If you have a lot of WAV files to encode, a for loop will fail (too many arguments).  Also, the for loop will not descend recursively into subdirectories.  This could be handy if you have an entire jukebox you want to convert and everything is arranged in directories (perhaps you just ripped your CD collection into a series of directories named after artists and CD titles).</p>
<p>Fortunately find with xargs scales up far better and can handle the recursion without problem:</p>
<p>find . -maxdepth 1 -iname &#8216;*.wav&#8217; -print0 | xargs -0 oggenc -q6</p>
<p>You&#8217;ll notice I didn&#8217;t bother computing the new name (&#8220;foo.wav&#8221; becomes &#8220;foo.ogg&#8221;).  This is because oggenc already encodes &#8220;foo.wav&#8221; as &#8220;foo.ogg&#8221;.</p>
<p>I used -print0 and -0 on xargs to properly handle pathnames with spaces.</p>
<p>It&#8217;s trivial to change this command to do as you wish.  You can have the WAV file removed after successful encoding.  For this, you might want to make a shell script that only handles one file (specified via argument), checks oggenc&#8217;s return code, and the existence of the output file before removing the source WAV file.  Then call that script from xargs instead of calling oggenc directly.  I leave that as an exercise for the reader.</p>
<p>If you want the recursion to find all *.wav files starting from the current directory, delete &#8220;-maxdepth 1&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating cron jobs in Ubuntu by bob</title>
		<link>http://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-251</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Mon, 10 Nov 2008 21:22:41 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-251</guid>
		<description>try this

*/5  * * * * sh /etc/init.d</description>
		<content:encoded><![CDATA[<p>try this</p>
<p>*/5  * * * * sh /etc/init.d</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing, setting up, and using Greasemonkey by red555rod</title>
		<link>http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-250</link>
		<dc:creator>red555rod</dc:creator>
		<pubDate>Sat, 11 Oct 2008 22:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-250</guid>
		<description>maybe i can make it work now lol i stared to delete it , butt not yet , ok thanks have a great day</description>
		<content:encoded><![CDATA[<p>maybe i can make it work now lol i stared to delete it , butt not yet , ok thanks have a great day</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating cron jobs in Ubuntu by alexrose</title>
		<link>http://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-248</link>
		<dc:creator>alexrose</dc:creator>
		<pubDate>Sun, 16 Mar 2008 13:45:34 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-248</guid>
		<description>Doesn&#039;t work for me. And I don&#039;t undersand why.
I saved: 0,5,10,15,20,25,30,35,40,45,50,55 * * * * sh /etc/init.d/firewall in /home/firewall/fw
Then: crontab -u root /home/firewall/fw
I don&#039;t understand what&#039;s wrong :(</description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t work for me. And I don&#8217;t undersand why.<br />
I saved: 0,5,10,15,20,25,30,35,40,45,50,55 * * * * sh /etc/init.d/firewall in /home/firewall/fw<br />
Then: crontab -u root /home/firewall/fw<br />
I don&#8217;t understand what&#8217;s wrong :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating cron jobs in Ubuntu by tbb</title>
		<link>http://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-247</link>
		<dc:creator>tbb</dc:creator>
		<pubDate>Thu, 21 Feb 2008 21:43:02 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-247</guid>
		<description>Every minute of every day, not every second - sorry.</description>
		<content:encoded><![CDATA[<p>Every minute of every day, not every second &#8211; sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating cron jobs in Ubuntu by tbb</title>
		<link>http://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-246</link>
		<dc:creator>tbb</dc:creator>
		<pubDate>Thu, 21 Feb 2008 21:39:31 +0000</pubDate>
		<guid isPermaLink="false">https://sartorius.wordpress.com/2006/08/30/creating-cron-jobs-in-ubuntu/#comment-246</guid>
		<description>A good quick tip, but I would encourage everyone to check the crontab manpage (man crontab).  The &#039;* * * * *&#039; will cause the command to be run every second of every day, which is inappropriate and unnecessary for most tasks - and will flood some system logs with cron messages.  Have a look at what each * represents and tailor your solution to your problem.</description>
		<content:encoded><![CDATA[<p>A good quick tip, but I would encourage everyone to check the crontab manpage (man crontab).  The &#8216;* * * * *&#8217; will cause the command to be run every second of every day, which is inappropriate and unnecessary for most tasks &#8211; and will flood some system logs with cron messages.  Have a look at what each * represents and tailor your solution to your problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing, setting up, and using Greasemonkey by bray_john</title>
		<link>http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-94</link>
		<dc:creator>bray_john</dc:creator>
		<pubDate>Thu, 15 Feb 2007 16:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://sartorius.wordpress.com/2006/12/19/installing-setting-up-and-using-greasemonkey/#comment-94</guid>
		<description>I also can&#039;t get the install button to work. I&#039;ve tried version 0.6.6.20061017.0 and 0.6.7.20070131.0

At this stage, I&#039;m figuring I&#039;ll just give up. 

But, thanks. At least I know that clicking on New User Script isn&#039;t supposed to be for installing a script.</description>
		<content:encoded><![CDATA[<p>I also can&#8217;t get the install button to work. I&#8217;ve tried version 0.6.6.20061017.0 and 0.6.7.20070131.0</p>
<p>At this stage, I&#8217;m figuring I&#8217;ll just give up. </p>
<p>But, thanks. At least I know that clicking on New User Script isn&#8217;t supposed to be for installing a script.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
