<?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>LinuxNut.org &#187; Linux</title>
	<atom:link href="http://linuxnut.org/tag/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://linuxnut.org</link>
	<description>Nuts about Linux and Stuff...</description>
	<lastBuildDate>Fri, 09 Apr 2010 15:52:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Resizing and Renaming Batches of Images</title>
		<link>http://linuxnut.org/2010/04/resizing-and-renaming-batches-of-images/</link>
		<comments>http://linuxnut.org/2010/04/resizing-and-renaming-batches-of-images/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 11:11:59 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[batch]]></category>
		<category><![CDATA[images]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[rename]]></category>
		<category><![CDATA[resize]]></category>

		<guid isPermaLink="false">http://linuxnut.org/?p=149</guid>
		<description><![CDATA[I recently had the need to resize a hundred jpeg images of varying sizes, and to get them all down to consistent widths (or heights for the portrait images), and then finally to rename the thumbnail preview images that I had also created.

Resizing
My first thought was that I could use Gimp, but alas it does [...]]]></description>
			<content:encoded><![CDATA[<p>I recently had the need to resize a hundred jpeg images of varying sizes, and to get them all down to consistent widths (or heights for the portrait images), and then finally to rename the thumbnail preview images that I had also created.<br />
<span id="more-149"></span></p>
<h3>Resizing</h3>
<p>My first thought was that I could use Gimp, but alas it does not by default have a batch conversion process. There is a plug-in called “<a href="http://members.ozemail.com.au/~hodsond/dbp.html">David&#8217;s Batch Processor</a>”, but it doesn&#8217;t allow you to specify just the X or Y dimension by itself.</p>
<p>The resizing tool I went for was &#8216;<a href="http://www.imagemagick.org/www/mogrify.html">mogrify</a>&#8216;, which is a command line utility with awesome image manipulation capabilities. Since I wanted to get all my landscape format images down to 400 pixels wide, I just entered the following command:</p>
<pre>mogrify -resize 400 *.jpg</pre>
<p>For the portrait images that I wanted to all be 400 pixels high I entered:</p>
<pre>mogrify -resize x400 *.jpg</pre>
<h3>Renaming</h3>
<p>Once I had all the images resized, I wanted to set the names of my preview thumbnails to end &#8216;_pre.jpg&#8217;. It turns out that this is very easy to do with the &#8216;rename&#8217; command, which was written by the creator of Perl &#8211; Larry Wall. The command is included by default with Debian and Ubuntu, and is easily added to other distros.</p>
<p>Just supply &#8216;rename&#8217; with a <a href="http://www.regular-expressions.info/reference.html">regular expression</a>, and it renames your files as required. The important part of the command parameter is:</p>
<pre>'s/ [pattern to match] / [what to replace it with] /'</pre>
<p>To rename my images I just entered:</p>
<pre>rename -v 's/\.jpg$/_pre\.jpg/' *.jpg</pre>
<p>To test the command without actually renaming anything, just change &#8216;-v&#8217; to &#8216;-n&#8217;.</p>
<p>For more information on the &#8216;rename&#8217; command see <a href="http://tips.webdesign10.com/how-to-bulk-rename-files-in-linux-in-the-terminal">http://tips.webdesign10.com/how-to-bulk-rename-files-in-linux-in-the-terminal</a></p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2010/04/resizing-and-renaming-batches-of-images/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>umask</title>
		<link>http://linuxnut.org/2009/08/umask/</link>
		<comments>http://linuxnut.org/2009/08/umask/#comments</comments>
		<pubDate>Fri, 21 Aug 2009 13:59:16 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[command]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[umask]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=119</guid>
		<description><![CDATA[umask determines what permissions any new files or directories will have by default. Like file permissions, it historically takes an octal value (e.g. &#8216;umask 002&#8242;), but can also symbolic values (e.g. &#8216;umask a=rx,ug+w&#8217;). I&#8217;m going to just focus on the octal values.

The octal value appears to have a lower than what you&#8217;d normally set with [...]]]></description>
			<content:encoded><![CDATA[<p>umask determines what permissions any new files or directories will have by default. Like file permissions, it historically takes an octal value (e.g. &#8216;umask 002&#8242;), but can also symbolic values (e.g. &#8216;umask a=rx,ug+w&#8217;). I&#8217;m going to just focus on the octal values.<br />
<span id="more-119"></span><br />
The octal value appears to have a lower than what you&#8217;d normally set with chmod, but this is because it is actually subtracted from the maximum possible file (666) or directory (777) permissions.</p>
<p>For example if you create a new directory with umask set to 022, the resulting permissions are set to 755, since 777 &#8211; 022 = 755.</p>
<p>Most of the time umask is set sensibly from the beginning, and you don&#8217;t have to worry about it. If you do need to change it, you&#8217;ll probably find it being set in one of your login scripts &#8211; &#8216;/etc/profile&#8217; or &#8216;~/.bashrc&#8217;.</p>
<p>For more information just check the man page.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2009/08/umask/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unix time</title>
		<link>http://linuxnut.org/2009/08/unix-time/</link>
		<comments>http://linuxnut.org/2009/08/unix-time/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 16:23:10 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[UTC]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=122</guid>
		<description><![CDATA[If you should happen to need to know the current time as a unix timestamp, try http://www.unixtime.se/. Alternatively typing
date +%s
at a convenient command line might be faster, and more accurate&#8230;
]]></description>
			<content:encoded><![CDATA[<p>If you should happen to need to know the current time as a unix timestamp, try <a href="http://www.unixtime.se/" target="_blank">http://www.unixtime.se/</a>. Alternatively typing</p>
<pre>date +%s</pre>
<p>at a convenient command line might be faster, and more accurate&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2009/08/unix-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finally &#8211; A 64-bit version of Adobe Flash Player for Linux</title>
		<link>http://linuxnut.org/2008/11/finally-a-64-bit-version-of-adobe-flash-player-for-linux/</link>
		<comments>http://linuxnut.org/2008/11/finally-a-64-bit-version-of-adobe-flash-player-for-linux/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 22:41:02 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[Adobe Flash]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=22</guid>
		<description><![CDATA[It seems to have been a long time coming, but finally an alpha version has been released. Although it&#8217;s an alpha, it&#8217;s still a vast improvement over the 32-bit version which I&#8217;ve used up until now with the aid of NPS Wrapper.
Because it can now running natively on a 64-bit architecture without the aid of [...]]]></description>
			<content:encoded><![CDATA[<p>It seems to have been a long time coming, but finally an alpha version has been released. Although it&#8217;s an alpha, it&#8217;s still a vast improvement over the 32-bit version which I&#8217;ve used up until now with the aid of NPS Wrapper.</p>
<p><span id="more-22"></span>Because it can now running natively on a 64-bit architecture without the aid of a wrapper, it has a smaller memory footprint and is vastly more stable. With the 32-bit version I usually had to restart Firefox at least once a day to free up some RAM, or just to get Flash Player working again.</p>
<p>To get your copy, just go to <a href="http://labs.adobe.com/downloads/flashplayer10.html">http://labs.adobe.com/downloads/flashplayer10.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/11/finally-a-64-bit-version-of-adobe-flash-player-for-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GNU/Linux Distro Timeline</title>
		<link>http://linuxnut.org/2008/08/gnulinux-distro-timeline/</link>
		<comments>http://linuxnut.org/2008/08/gnulinux-distro-timeline/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 19:48:32 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[GNU]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[timeline]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=18</guid>
		<description><![CDATA[Andreas has produced a cladogram (tree diagram) showing the timeline and relationship of probably every known Linux distribution. You can see the latest version of the diagram (v7.6) here, or visit the homepage http://futurist.se/gldt/.
]]></description>
			<content:encoded><![CDATA[<p>Andreas has produced a cladogram (tree diagram) showing the timeline and relationship of probably every known Linux distribution. You can see the latest version of the diagram (v7.6) <a href="http://futurist.se/gldt/gldt76.png">here</a>, or visit the homepage <a href="http://futurist.se/gldt/">http://futurist.se/gldt/</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/gnulinux-distro-timeline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux Outlaws Podcast</title>
		<link>http://linuxnut.org/2008/08/linux-outlaws-podcast/</link>
		<comments>http://linuxnut.org/2008/08/linux-outlaws-podcast/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 19:10:29 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Linux Outlaws]]></category>
		<category><![CDATA[netcast]]></category>
		<category><![CDATA[podcast]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=15</guid>
		<description><![CDATA[Linux Outlaws is a weekly podcast, primarily about Linux, but also covering other open source goodness. The hosts of the show are Fabian Scherschel in Germany, and Dan Lynch in the UK. The show is presented in a humorous, laid-back manner, and fills the gap left after the demise of LUG Radio.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.linuxoutlaws.com/">Linux Outlaws</a> is a weekly podcast, primarily about Linux, but also covering other open source goodness. The hosts of the show are Fabian Scherschel in Germany, and Dan Lynch in the UK. The show is presented in a humorous, laid-back manner, and fills the gap left after the demise of LUG Radio.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/linux-outlaws-podcast/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Remotely shutdown a Windows PC from Linux</title>
		<link>http://linuxnut.org/2008/08/remotely-shutdown-a-windows-pc-from-linux/</link>
		<comments>http://linuxnut.org/2008/08/remotely-shutdown-a-windows-pc-from-linux/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 10:35:12 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[command]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Remote]]></category>
		<category><![CDATA[Shutdown]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=27</guid>
		<description><![CDATA[A remote Windows PC can easily be shutdown, assuming you have Samba installed on your Linux box, and you have a user account on the Windows PC that has the necessary rights.
Just enter the following command, where &#8216;thehostname&#8217; is the hostname of the remote PC, and &#8216;theusername&#8217; is a valid user account on the remote [...]]]></description>
			<content:encoded><![CDATA[<p>A remote Windows PC can easily be shutdown, assuming you have Samba installed on your Linux box, and you have a user account on the Windows PC that has the necessary rights.</p>
<p><span id="more-27"></span>Just enter the following command, where &#8216;thehostname&#8217; is the hostname of the remote PC, and &#8216;theusername&#8217; is a valid user account on the remote PC:</p>
<pre>net rpc shutdown -S thehostname -U theusername</pre>
<p>If the hostname is not known, or cannot be resolved, then use the following instead, where &#8216;123.123.123.123&#8242; is the IP address of the remote PC:</p>
<pre>net rpc shutdown -I 123.123.123.123 -U theusername</pre>
<p>For more information on the command, just enter the following:</p>
<pre>net help shutdown</pre>
<p>Additionally, the parameters that can be used with Windows&#8217; own shutdown command such as &#8216;-f&#8217; to force or &#8216;-t&#8217; to set a timeout, can also be applied to the net rpc shutdown command as well. For example the following will wait 60 seconds, and then force all running programs to terminate before shutting down:</p>
<pre>net rpc shutdown -S thehostname -U theusername -f -t 60</pre>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/remotely-shutdown-a-windows-pc-from-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux is Not Windows</title>
		<link>http://linuxnut.org/2008/08/linux-is-not-windows/</link>
		<comments>http://linuxnut.org/2008/08/linux-is-not-windows/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 09:56:08 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=29</guid>
		<description><![CDATA[OneAndOneIs2 has an article that gives some reasons on why &#8216;Linux is Not Windows&#8217;.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://linux.oneandoneis2.org/">OneAndOneIs2</a> has an article that gives some reasons on why <a href="http://linux.oneandoneis2.org/LNW.htm">&#8216;Linux is Not Windows&#8217;</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/linux-is-not-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to mount an ISO file in Linux</title>
		<link>http://linuxnut.org/2008/08/how-to-mount-an-iso-file-in-linux/</link>
		<comments>http://linuxnut.org/2008/08/how-to-mount-an-iso-file-in-linux/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 08:59:50 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[How-Tos]]></category>
		<category><![CDATA[command]]></category>
		<category><![CDATA[ISO]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[mount]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=31</guid>
		<description><![CDATA[Sometimes burning an ISO file to a CD-ROM just to access its contents is overkill, but there is another way.
As root, simply enter the following command, where &#8216;cd1.iso&#8217; is the name of the ISO image file, and &#8216;/mnt/cd&#8217; is an existing directory:
mount -o loop cd1.iso /mnt/cd
]]></description>
			<content:encoded><![CDATA[<p>Sometimes burning an ISO file to a CD-ROM just to access its contents is overkill, but there is another way.</p>
<p><span id="more-31"></span>As root, simply enter the following command, where &#8216;cd1.iso&#8217; is the name of the ISO image file, and &#8216;/mnt/cd&#8217; is an existing directory:</p>
<pre>mount -o loop cd1.iso /mnt/cd</pre>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/how-to-mount-an-iso-file-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Inside the Linux Boot Process</title>
		<link>http://linuxnut.org/2008/08/inside-the-linux-boot-process/</link>
		<comments>http://linuxnut.org/2008/08/inside-the-linux-boot-process/#comments</comments>
		<pubDate>Fri, 15 Aug 2008 19:49:45 +0000</pubDate>
		<dc:creator>Bryce</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://admin.linuxnut.org/?p=20</guid>
		<description><![CDATA[The IBM developerWorks website is filled with many interesting articles. Tonight&#8217;s pick is &#8216;Inside the Linux boot process&#8217;. This article guides you from the initial power on through to the user-space being available. However if you really want to get down and dirty with the boot process, then I would suggest having a go at [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.ibm.com/developerworks/">IBM developerWorks website</a> is filled with many interesting articles. Tonight&#8217;s pick is <a href="http://www.ibm.com/developerworks/linux/library/l-linuxboot/index.html">&#8216;Inside the Linux boot process&#8217;</a>. This article guides you from the initial power on through to the user-space being available. However if you really want to get down and dirty with the boot process, then I would suggest having a go at <a href="http://www.linuxfromscratch.org/">Linux From Scratch</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://linuxnut.org/2008/08/inside-the-linux-boot-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
