<?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>Imaging and a little bit of OSS</title>
	<atom:link href="http://nuclear-imaging.info/site_content/feed/" rel="self" type="application/rss+xml" />
	<link>http://nuclear-imaging.info/site_content</link>
	<description>Yet another techno blog</description>
	<lastBuildDate>Wed, 04 Jan 2012 18:29:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>When gvfsd-metadata starts using 100% processor</title>
		<link>http://nuclear-imaging.info/site_content/2011/12/28/when-gvfsd-metadata-starts-using-100-processor/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=when-gvfsd-metadata-starts-using-100-processor</link>
		<comments>http://nuclear-imaging.info/site_content/2011/12/28/when-gvfsd-metadata-starts-using-100-processor/#comments</comments>
		<pubDate>Thu, 29 Dec 2011 05:03:49 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[cpu 100%]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[gvfs-metadata]]></category>
		<category><![CDATA[mint]]></category>
		<category><![CDATA[processor]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=430</guid>
		<description><![CDATA[Sluggishness on your system running Linux can be caused by numerous factors &#8211; among them is a process called gvfsd-metadata. From what I&#8217;ve heard other people say, its caused by fragmentation &#8211; possibly due to a partition that&#8217;s nearly full. All you can do is just terminate the process or delete the script from your <a href='http://nuclear-imaging.info/site_content/2011/12/28/when-gvfsd-metadata-starts-using-100-processor/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Sluggishness on your system running Linux can be caused by numerous factors &#8211; among them is a process called gvfsd-metadata.</p>
<p>From what I&#8217;ve heard other people say, its caused by fragmentation &#8211; possibly due to a partition that&#8217;s nearly full.</p>
<p>All you can do is just terminate the process or delete the script from your ~/ folder.</p>
<pre>rm -rf ~/.local/share/gvfs-metadata</pre>
<p>Every now and then its a good idea to make sure that your home folder is not filled up past 90% or so.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/12/28/when-gvfsd-metadata-starts-using-100-processor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Monitor network usage with ifstat in bash</title>
		<link>http://nuclear-imaging.info/site_content/2011/12/28/monitor-network-usage-with-ifstat-in-bash/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=monitor-network-usage-with-ifstat-in-bash</link>
		<comments>http://nuclear-imaging.info/site_content/2011/12/28/monitor-network-usage-with-ifstat-in-bash/#comments</comments>
		<pubDate>Wed, 28 Dec 2011 18:02:39 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[download rate]]></category>
		<category><![CDATA[ifstat]]></category>
		<category><![CDATA[MB/s]]></category>
		<category><![CDATA[network usage]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[upload rate]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=427</guid>
		<description><![CDATA[To monitor the instantaneous network usage, execute the ifstat command in bash. You may need to acquire it from a repository if you don&#8217;t have it already. sudo apt-get install ifstat To display usage on eth0, with a 5 second delay, just once: ifstat -i eth0 5 1 You can change the number of seconds, <a href='http://nuclear-imaging.info/site_content/2011/12/28/monitor-network-usage-with-ifstat-in-bash/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>To monitor the instantaneous network usage, execute the ifstat command in bash. You may need to acquire it from a repository if you don&#8217;t have it already.</p>
<pre>sudo apt-get install ifstat</pre>
<p>To display usage on eth0, with a 5 second delay, just once:</p>
<pre>ifstat -i eth0 5 1</pre>
<p>You can change the number of seconds, and the number of times you want the output displayed. If you don&#8217;t specify the count, it will go on forever until you ctrl-c out of it.</p>
<p>So here is a script that displays the download rates in MB/s and upload rates in KB/s every 5 seconds until you hit ctrl-c.</p>
<pre>while :
do
# Press ctrl-c to exit
x=`ifstat -i eth0 5 1 | tail -1 | tr '\t' ' '`;  #tail -1 takes the DL and UL speeds in KB/S
x1=`echo $x | cut -d ' ' -f1`; x2=`echo $x | cut -d ' ' -f2`;
x1=$(echo "scale=3; $x1/1024" | bc); # Convert DL rate to MB/S
printf "D: %0.3f MB/s\t U: %0.3f KB/s\n" "$x1" "$x2"
done</pre>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/12/28/monitor-network-usage-with-ifstat-in-bash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change &#8220;Linux Mint flavoured&#8221; Google search to original Google search</title>
		<link>http://nuclear-imaging.info/site_content/2011/12/27/change-linux-mint-flavoured-google-search-to-original-google-search/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=change-linux-mint-flavoured-google-search-to-original-google-search</link>
		<comments>http://nuclear-imaging.info/site_content/2011/12/27/change-linux-mint-flavoured-google-search-to-original-google-search/#comments</comments>
		<pubDate>Wed, 28 Dec 2011 00:33:46 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[en-US]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[google.xml]]></category>
		<category><![CDATA[katya]]></category>
		<category><![CDATA[linux mint]]></category>
		<category><![CDATA[rebranding. google search]]></category>
		<category><![CDATA[search bar]]></category>
		<category><![CDATA[searchplugin]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=421</guid>
		<description><![CDATA[One mild inconvenience while using Linux Mint is the default Google search in Firefox search bar. The plain ol&#8217; google search is reformatted, and wrapped within a Linux Mint flavoured wrapper. Its not the end of the world &#8211; you can always go to google.com and then search the same word or phrase. However, many <a href='http://nuclear-imaging.info/site_content/2011/12/27/change-linux-mint-flavoured-google-search-to-original-google-search/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>One mild inconvenience while using Linux Mint is the default Google search in Firefox search bar. The plain ol&#8217; google search is reformatted, and wrapped within a Linux Mint flavoured wrapper. Its not the end of the world &#8211; you can always go to google.com and then search the same word or phrase. However, many people have gotten into the habit of performing their search using the search bar on top left corner within Firefox. Getting a Linux Mint wrapper around just doesn&#8217;t look right.</p>
<p>Someone figured out that the google.xml file used in the search plugin was modified in the Mint distribution to create give the modified results. In order to get the original google results, just type in the following command lines:</p>
<pre>cd /usr/share/linuxmint/common/artwork/firefox/
sudo wget http://mxr.mozilla.org/firefox/source/browser/locales/en-US/searchplugins/google.xml?raw=1 -O google.xml.fixed
sudo mv google.xml google.xml.orig
sudo mv google.xml.fixed google.xml
sudo cp google.xml /usr/lib/firefox-addons/searchplugins/en-US/google.xml</pre>
<p>Restarting Firefox (maybe a few times) is required to get the google results in the plain old familiar format.</p>
<p><span style="color: #339966;">The above code was obtained from:<span style="color: #008080;"> <a title="Revert to original google search in Linux Mint" href="http://danielj.se/2011/05/02/change-back-google-search-in-linux-mint/"><span style="color: #008080;">Change Back Google Search in Linux Mint</span></a></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/12/27/change-linux-mint-flavoured-google-search-to-original-google-search/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Booting halts with kernel_thread_helper</title>
		<link>http://nuclear-imaging.info/site_content/2011/12/06/booting-halts-with-kernel_thread_helper/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=booting-halts-with-kernel_thread_helper</link>
		<comments>http://nuclear-imaging.info/site_content/2011/12/06/booting-halts-with-kernel_thread_helper/#comments</comments>
		<pubDate>Tue, 06 Dec 2011 17:31:33 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[acpi=off]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[distribution]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[freeze]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[grub.cfg]]></category>
		<category><![CDATA[hang]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[linux mint]]></category>
		<category><![CDATA[linux_thread_helper]]></category>
		<category><![CDATA[liveCD]]></category>
		<category><![CDATA[nolapic]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=406</guid>
		<description><![CDATA[The newer releases of Ubuntu and Linux Mint have started getting stuck during LiveCD installation or after distribution/kernel upgrade.  Usually the point where it gets stagnant is when it reaches this line: kernel_thread_helper+0x7/0x10 Nothing happens past that point. A solution or a workaround to this is to insert the nolapic acpi=off switch in the grub <a href='http://nuclear-imaging.info/site_content/2011/12/06/booting-halts-with-kernel_thread_helper/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>The newer releases of Ubuntu and Linux Mint have started getting stuck during LiveCD installation or after distribution/kernel upgrade.  Usually the point where it gets stagnant is when it reaches this line:</p>
<pre><code>kernel_thread_helper+0x7/0x10</code></pre>
<p>Nothing happens past that point. A solution or a workaround to this is to insert the <span style="color: #3366ff;">nolapic acpi=off</span> switch in the grub boot line. There are 3 ways to do this:</p>
<p>1: If you are starting a fresh install from a CD and the installation pauses at the kernel_thread_helper line, you need to restart your computer.</p>
<p>When you boot from your installation CD,<span style="color: #3366ff;"> choose F6</span> before you continue trying out the LiveCD. This give you boot option at the bottom of your screen.</p>
<p>At the very end of the line add <span style="color: #3366ff;">nolapic acpi=off</span> and hit enter to continue booting from LiveCD. In most cases this should work.</p>
<p>2. The same problem may arise when you do a distribution upgrade or even a kernel upgrade. In that case you need to change your grub.cfg file. Follow these steps:</p>
<blockquote>
<pre>sudo nano /boot/grub/grub.cfg</pre>
</blockquote>
<p>Enter your sudo password and it will bring you to your grub menu configuration.</p>
<p>Look for the section that read similar to this:</p>
<blockquote>
<pre>menuentry 'Ubuntu, with Linux 2.6.38-11-generic' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 set gfxpayload=$linux_gfx_mode
 insmod part_msdos
 insmod ext2
 set root='(hd0,msdos6)'
 search --no-floppy --fs-uuid --set=root 337e2841-fc82-61b3-84be-5a9c71ae43b8
 <span style="color: #3366ff;"> linux   /boot/vmlinuz-2.6.38-11-generic root=UUID=337e2841-fc82-61b3-84be-5a9c71ae43b8 ro quiet splash vt.handoff=7</span>
 initrd  /boot/initrd.img-2.6.38-11-generic
 }</pre>
</blockquote>
<p>You want to change the line that I have identified above to read:</p>
<blockquote>
<pre>linux   /boot/vmlinuz-2.6.38-11-generic root=UUID=337e2841-fc82-61b3-84be-5a9c71ae43b8 ro quiet splash vt.handoff=7 <span style="color: #3366ff;">nolapic acpi=off</span></pre>
</blockquote>
<p>After adding these switches to the boot menu option, press ctrl-X, then save and exit.</p>
<p><strong>This is for a permanent change if you can boot using an older kernel.</strong></p>
<p>3: If you cannot login to an older kernel or recovery mode because of the kernel_thread_helper error,  you have to press &#8220;e&#8221; (without the quotation marks)  to edit the boot options when you get the grub menu.</p>
<p>For the kernel you want to use, edit the end of the line that reads</p>
<blockquote>
<pre>linux   /boot/vmlinuz-2.6.38-11-generic root=UUID=337e2841-fc82-61b3-84be-5a9c71ae43b8 ro quiet splash vt.handoff=7</pre>
</blockquote>
<p>to</p>
<blockquote>
<pre>linux   /boot/vmlinuz-2.6.38-11-generic root=UUID=337e2841-fc82-61b3-84be-5a9c71ae43b8 ro quiet splash vt.handoff=7 <span style="color: #3366ff;">nolapic acpi=off</span></pre>
</blockquote>
<p>Press Enter and you should be able to boot.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/12/06/booting-halts-with-kernel_thread_helper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Saving images to postscript format in Matlab</title>
		<link>http://nuclear-imaging.info/site_content/2011/11/16/saving-images-to-postscript-format-in-matlab/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=saving-images-to-postscript-format-in-matlab</link>
		<comments>http://nuclear-imaging.info/site_content/2011/11/16/saving-images-to-postscript-format-in-matlab/#comments</comments>
		<pubDate>Thu, 17 Nov 2011 00:17:13 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Imaging]]></category>
		<category><![CDATA[non-OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[-dpsc2]]></category>
		<category><![CDATA[.pdf]]></category>
		<category><![CDATA[.ps]]></category>
		<category><![CDATA[append]]></category>
		<category><![CDATA[figure]]></category>
		<category><![CDATA[image]]></category>
		<category><![CDATA[matlab]]></category>
		<category><![CDATA[pdf conversion]]></category>
		<category><![CDATA[postscript]]></category>
		<category><![CDATA[print]]></category>
		<category><![CDATA[ps2pdf]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=403</guid>
		<description><![CDATA[On most Linux/Unix based systems, you can save your Matlab figure as a postscript instead of saving it as a png or jpg. One advantage of saving figures in this manner is that you can save multiple images as separate pages on that .ps document, whereas with png/jpg you have to save each image as <a href='http://nuclear-imaging.info/site_content/2011/11/16/saving-images-to-postscript-format-in-matlab/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>On most Linux/Unix based systems, you can save your Matlab figure as a postscript instead of saving it as a png or jpg. One advantage of saving figures in this manner is that you can save multiple images as separate pages on that .ps document, whereas with png/jpg you have to save each image as a separate file.</p>
<p>To print the current image to postscript, all you need to run is:</p>
<blockquote><p>print(&#8216;-dpsc2&#8242;,&#8217;filename&#8217;);</p></blockquote>
<p>To have multiple images appended within the postscript document, you need to use the <em>-append</em> switch.</p>
<blockquote><p>print(&#8216;-dpsc2&#8242;, &#8216;-append&#8217;, &#8216;filename&#8217;);</p></blockquote>
<p>Your output postscript will have the name <em>filename.ps</em></p>
<p>To convert the postscripts to pdf format, just run the ps2pdf command in the terminal window:</p>
<blockquote><p>ps2fpdf filename.ps</p></blockquote>
<p>The output of this would be <em>filename.pdf</em></p>
<p>And you&#8217;re done.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/11/16/saving-images-to-postscript-format-in-matlab/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>/usr/bin/ld: cannot find -lbz2</title>
		<link>http://nuclear-imaging.info/site_content/2011/11/10/usrbinld-cannot-find-lbz2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=usrbinld-cannot-find-lbz2</link>
		<comments>http://nuclear-imaging.info/site_content/2011/11/10/usrbinld-cannot-find-lbz2/#comments</comments>
		<pubDate>Thu, 10 Nov 2011 17:05:35 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[non-OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[-lbz2]]></category>
		<category><![CDATA[/usr/bin/ld]]></category>
		<category><![CDATA[libbz2-dev]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=399</guid>
		<description><![CDATA[In order to install l1-SPIRiT Compressed Sensing Parallel MRI, we need to have a couple of programs installed &#8211; fftw3, lbz2.  Usually you encounter the following error while running build routine in Matlab. /usr/bin/ld: cannot find -lbz2 collect2: ld returned 1 exit status sudo apt-get install libbz2-dev After installing libbz2-dev this error is corrected.]]></description>
			<content:encoded><![CDATA[<p>In order to install l1-SPIRiT Compressed Sensing Parallel MRI, we need to have a couple of programs installed &#8211; fftw3, lbz2.  Usually you encounter the following error while running build routine in Matlab.</p>
<blockquote>
<pre dir="ltr">/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
</pre>
<p>sudo apt-get install libbz2-dev</p></blockquote>
<p>After installing libbz2-dev this error is corrected.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/11/10/usrbinld-cannot-find-lbz2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating an index for .avi files</title>
		<link>http://nuclear-imaging.info/site_content/2011/11/09/creating-in-index-file-for-avi-files/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=creating-in-index-file-for-avi-files</link>
		<comments>http://nuclear-imaging.info/site_content/2011/11/09/creating-in-index-file-for-avi-files/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 13:18:07 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Entertainment]]></category>
		<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[non-OSS]]></category>
		<category><![CDATA[-idx]]></category>
		<category><![CDATA[avi]]></category>
		<category><![CDATA[fast forward]]></category>
		<category><![CDATA[index files]]></category>
		<category><![CDATA[mencoder]]></category>
		<category><![CDATA[recreate]]></category>
		<category><![CDATA[reverse]]></category>
		<category><![CDATA[scroll]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=395</guid>
		<description><![CDATA[Some .avi files tend to have an out of sync audio track, some can&#8217;t be scrolled through (forward/reverse), while others might show an message that says the index file needs to be recreated. Solution is to create a copy of that file that has an index recreated and remove the original and save the copy <a href='http://nuclear-imaging.info/site_content/2011/11/09/creating-in-index-file-for-avi-files/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Some .avi files tend to have an out of sync audio track, some can&#8217;t be scrolled through (forward/reverse), while others might show an message that says the index file needs to be recreated.</p>
<p>Solution is to create a copy of that file that has an index recreated and remove the original and save the copy and all the usual replacement methods.</p>
<blockquote><p>mencoder -idx files1.avi -ovc copy -oac copy -o file2.avi</p></blockquote>
<p>Here file1.avi is the input file, and file2 is the output file with corrected index.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/11/09/creating-in-index-file-for-avi-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exit Ubuntu &#8211; Enter Linux Mint</title>
		<link>http://nuclear-imaging.info/site_content/2011/09/19/exit-ubuntu-enter-linux-mint/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=exit-ubuntu-enter-linux-mint</link>
		<comments>http://nuclear-imaging.info/site_content/2011/09/19/exit-ubuntu-enter-linux-mint/#comments</comments>
		<pubDate>Mon, 19 Sep 2011 19:12:44 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[non-OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[gnome]]></category>
		<category><![CDATA[graphics]]></category>
		<category><![CDATA[linux mint]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[unity]]></category>
		<category><![CDATA[vnc]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=381</guid>
		<description><![CDATA[The latest version of Ubuntu is heavily based upon Unity environment. Unfortunately Unity has no track record of playing nice with existing gnome programs. For network applications such as VNC, Unity crashes the program with whole bunch of errors. These crashes are observed occasionally in the Ubuntu 11.04 (Natty Narwhal) release, and most certainly in <a href='http://nuclear-imaging.info/site_content/2011/09/19/exit-ubuntu-enter-linux-mint/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>The latest version of Ubuntu is heavily based upon Unity environment. Unfortunately Unity has no track record of playing nice with existing gnome programs. For network applications such as VNC, Unity crashes the program with whole bunch of errors. These crashes are observed occasionally in the Ubuntu 11.04 (Natty Narwhal) release, and most certainly in the latest beta 1 release of Ubuntu 11.10 (Oneiric Ocelot).</p>
<p>If you have gotten comfortable with Ubuntu and want to continue using Gnome as the main environment, you can do so by using Linux Mint 11 (Katya). It has the same repositories as Ubuntu and you can even use the ubuntu-restricted-extras and build-essential packages which lets you obtain some of the fonts, codecs and libraries that Ubuntu fetches for you.</p>
<p style="text-align: center;"><a href="http://nuclear-imaging.info/site_content/2011/09/19/exit-ubuntu-enter-linux-mint/linux-mint/" rel="attachment wp-att-385"><img class="aligncenter size-full wp-image-385" style="border: 1px solid black; margin: 1px;" title="linux-mint" src="http://nuclear-imaging.info/site_content/wp-content/uploads/2011/09/linux-mint.png" alt="" width="200" height="200" /></a></p>
<p>Ubuntu is starting to put more emphasis on making their release into an eye-candy, at the cost of reduced functionality. Having used Ubuntu since Dapper Drake days, its sad to ditch it for another distro. IMO Ubuntu 10.04 was the cleanest distro they put out &#8211; things have been going downhill after that. Linux Mint on the other hand picked up at the point when Ubuntu started to go dysfunctional. It has everything that Ubuntu should have been. There isn&#8217;t much to write about Mint 11. Its very similar to Ubuntu 10.04, has a newer kernel 2.6.38.xx, clean graphics, and the same repositories as Ubuntu. The transition is very easy, and things look a lot more neater in Mint.</p>
<p>To recap: If you are currently using Ubuntu and are afraid to upgrade to the 11.10 release, your fear is quite justified. Make a backup of your /home folder and go for a clean install of Linux Mint instead. I moved to Mint about a month ago and have had a rather smooth sailing so far.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/09/19/exit-ubuntu-enter-linux-mint/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VNC server setup for Ubuntu 11.04 (Natty Narwhal)</title>
		<link>http://nuclear-imaging.info/site_content/2011/05/11/vnc-server-setup-for-ubuntu-11-04-natty-narwhal/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=vnc-server-setup-for-ubuntu-11-04-natty-narwhal</link>
		<comments>http://nuclear-imaging.info/site_content/2011/05/11/vnc-server-setup-for-ubuntu-11-04-natty-narwhal/#comments</comments>
		<pubDate>Thu, 12 May 2011 00:26:07 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[setup]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[ssh server]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[ubuntu 11.04]]></category>
		<category><![CDATA[vnc]]></category>
		<category><![CDATA[vnc4server]]></category>
		<category><![CDATA[vncserver]]></category>
		<category><![CDATA[vncviewer]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=375</guid>
		<description><![CDATA[For the first time I was able to get VNC to work with Ubuntu with Gnome session instead of a xterm on gray background. The steps involved were exactly the same as I was following earlier, with one exception: the setup of xstartup in the ~/.vnc folder. For your xstartup file in ~/.vnc (the &#8220;.vnc&#8221; <a href='http://nuclear-imaging.info/site_content/2011/05/11/vnc-server-setup-for-ubuntu-11-04-natty-narwhal/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>For the first time I was able to get VNC to work with Ubuntu with  Gnome session instead of a xterm on gray background. The steps involved  were exactly the same as I was following earlier, with one exception:   the setup of xstartup in the ~/.vnc folder.</p>
<blockquote><p>For your xstartup file in ~/.vnc (the &#8220;.vnc&#8221; folder in</p>
<p>your home directory), you need the following:</p>
<p>#&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>#!/bin/sh</p>
<p># Uncomment the following two lines for normal desktop:</p>
<p># unset SESSION_MANAGER</p>
<p># exec /etc/X11/xinit/xinitrc</p>
<p>[ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup</p>
<p>[ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources</p>
<p>xsetroot -solid grey</p>
<p>vncconfig -iconic &amp;</p>
<p>xterm -geometry 80&#215;24+10+10 -ls -title &#8220;$VNCDESKTOP Desktop&#8221; &amp;</p>
<p>gnome-session  &amp;</p>
<p># twm &amp;</p>
<p>#&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>instead of uncommenting the lines as the script suggests, you change  the window manager to gnome-session</p>
<p>make sure restart vnc4server</p>
</blockquote>
<p>The line which got Gnome working was &#8220;gnome-session &amp;&#8221;</p>
<p>========================================</p>
<p>Now for all the steps involved (works in Karmic Koala Alpha 2, Ubuntu  9.10, kernel 2.6.30-10)</p>
<p>1. Install ssh server, ssh client, VNC viewer, VNC server, and xinetd</p>
<blockquote><p>sudo apt-get install openssh-server openssh-client  vnc4server xinetd  vncviewer</p>
</blockquote>
<p>2. Setup the ssh password for your login</p>
<blockquote><p>ssh-keygen</p>
</blockquote>
<p>3. Test out the ssh server by typing in</p>
<blockquote><p>ssh localhost  or ssh your_login@your_ip_address</p>
</blockquote>
<p>4. Then create a vnc password</p>
<blockquote><p>sudo vncpasswd ~/.vncpasswd</p>
</blockquote>
<p>5. Edit the xstartup file in ~/.vnc directory</p>
<blockquote><p>For your xstartup file in ~/.vnc (the &#8220;.vnc&#8221; folder in</p>
<p>your home directory), you need the following:</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>#!/bin/sh</p>
<p># Uncomment the following two lines for normal desktop:</p>
<p># unset SESSION_MANAGER</p>
<p># exec /etc/X11/xinit/xinitrc</p>
<p>[ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup</p>
<p>[ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources</p>
<p>xsetroot -solid grey</p>
<p>vncconfig -iconic &amp;</p>
<p>xterm -geometry 80&#215;24+10+10 -ls -title &#8220;$VNCDESKTOP Desktop&#8221; &amp;</p>
<p>gnome-session &amp;</p>
<p># twm &amp;</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
</blockquote>
<p>instead of uncommenting the lines as the script suggests, you change  the window manager to gnome-session</p>
<p>6. Create a VNC desktop</p>
<blockquote><p>vnc4server :1 -geometry 1024&#215;768</p>
</blockquote>
<p>7. Then to tunnel into your VNC desktop, first create a SSH tunnel by  logging into SSH with the comand:</p>
<blockquote><p>ssh -L 5901:your_ip_address:5901  your_username@your_ipaddress</p>
</blockquote>
<p>8. Finally, load up your VNC desktop</p>
<blockquote><p>vncviewer localhost:1</p>
</blockquote>
<p>And now you are ready to use connect to your machine remotely and use administer the computer remotely.</p>
<p>P.S: If you are using a firewall (hardware or software, you need to get enable port forwarding and unblock ports 22 and 5900-5999 on the Ubuntu machine to allow SSH and VNC to be accessed.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/05/11/vnc-server-setup-for-ubuntu-11-04-natty-narwhal/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>GNU Parallel</title>
		<link>http://nuclear-imaging.info/site_content/2011/05/11/gnu-parallel/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=gnu-parallel</link>
		<comments>http://nuclear-imaging.info/site_content/2011/05/11/gnu-parallel/#comments</comments>
		<pubDate>Thu, 12 May 2011 00:16:35 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[gnu parallel]]></category>
		<category><![CDATA[parallel processing]]></category>
		<category><![CDATA[parallelization]]></category>
		<category><![CDATA[shell scripting]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[ubuntu 11.04]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=369</guid>
		<description><![CDATA[Running scripts in serial order on a multi-core machine will take quite a bit of time. If the tasks are repetitive, the command can be run under GNU Parallel. You can install it on RPM or Debian based distribution from the GNU Parallel repository. Install the binary that fits your flavour of Linux. Please note <a href='http://nuclear-imaging.info/site_content/2011/05/11/gnu-parallel/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Running scripts in serial order on a multi-core machine will take quite a bit of time. If the tasks are repetitive, the command can be run under GNU Parallel.</p>
<p>You can install it on RPM or Debian based distribution from the <a href="https://build.opensuse.org/package/show?package=parallel&amp;project=home%3Atange">GNU Parallel repository</a>. Install the binary that fits your flavour of Linux. Please note that even though the latest release of GNU Parallel has a flavour of Linux associated with it, it runs on most of the older AND newer distributions. For instance I was able to install the April 21st 2011 release of amd_64 RPM on a RHEL5 machine, and it ran just fine for that 8 core machine.</p>
<p>After installation you can try it out on a sample directory by running:</p>
<blockquote><p>ls -d */ | sed &#8216;s/\///g&#8217; | parallel zip -r -q {}.zip {}</p></blockquote>
<p>This will recursively zip all the directories within a given folder, in parallel. By default, it will use up the maximum number of cores, but you can check the man pages of parallel to check how to employ N number of processors to run the task in parallel.</p>
<blockquote><p>ls *.jpg | parallel convert {} -resize 75% -quality 80% {}</p></blockquote>
<p>If you have imagemagick installed, you could save a whole bunch of space by converting some of the high-res images to a slightly lower resolution. The above example will resize the images to 75% of their original size with 80% quality. The original images will be overwritten by the resize and downsampled ones. While this is running, you can fire up htop in another terminal window to watch all the processors working in parallel.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/05/11/gnu-parallel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Percentage signal change (over time)</title>
		<link>http://nuclear-imaging.info/site_content/2011/04/27/percentage-signal-change-over-time/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=percentage-signal-change-over-time</link>
		<comments>http://nuclear-imaging.info/site_content/2011/04/27/percentage-signal-change-over-time/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 20:10:24 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Imaging]]></category>
		<category><![CDATA[Programming]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=364</guid>
		<description><![CDATA[Basic formula goes: Matlab code: psc=((signal-mean(signal))./signal).*100;]]></description>
			<content:encoded><![CDATA[<p>Basic formula goes:</p>
<p>Matlab code:</p>
<blockquote><p>psc=((signal-mean(signal))./signal).*100;  </p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/04/27/percentage-signal-change-over-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bounding box for wfu-pickatlas masks</title>
		<link>http://nuclear-imaging.info/site_content/2011/04/14/bounding-box-for-wfu-pickatlas-masks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=bounding-box-for-wfu-pickatlas-masks</link>
		<comments>http://nuclear-imaging.info/site_content/2011/04/14/bounding-box-for-wfu-pickatlas-masks/#comments</comments>
		<pubDate>Thu, 14 Apr 2011 14:01:38 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Imaging]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Science]]></category>
		<category><![CDATA[79x95x68]]></category>
		<category><![CDATA[91x109x91]]></category>
		<category><![CDATA[bounding box]]></category>
		<category><![CDATA[conversion]]></category>
		<category><![CDATA[fmri]]></category>
		<category><![CDATA[mask]]></category>
		<category><![CDATA[matlab]]></category>
		<category><![CDATA[nifti]]></category>
		<category><![CDATA[spm8]]></category>
		<category><![CDATA[toobox]]></category>
		<category><![CDATA[wfu pickatlas]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=361</guid>
		<description><![CDATA[Assuming the nifti toolbox is in Matlab path, we can get the 91x109x91 mask to have the same dimensions as the normalized images generated with bounding boxes. If we are making a mask for hippocampus, first we save that mask from WFU Pickatlas. Then to make it 79x95x68 voxels, run the following small script. x=load_untouch_nii(&#8216;hipp.img&#8217;); <a href='http://nuclear-imaging.info/site_content/2011/04/14/bounding-box-for-wfu-pickatlas-masks/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Assuming the <a href="http://www.mathworks.com/matlabcentral/fileexchange/8797">nifti toolbox</a> is in Matlab path, we can get the 91x109x91 mask to have the same dimensions as the normalized images generated with bounding boxes.</p>
<p>If we are making a mask for hippocampus, first we save that mask from WFU Pickatlas. Then to make it 79x95x68 voxels, run the following small script.</p>
<blockquote><p>
x=load_untouch_nii(&#8216;hipp.img&#8217;);<br />
x=x.img;xdim=[1:6 86:91]; ydim=[1:6 102:109]; zdim=[1:11 80:91];<br />
origin=[40 57 26]; datatype=16;<br />
x(xdim,:,:)=[]; x(:,ydim,:)=[]; x(:,:,zdim)=[];<br />
nii=make_nii(x, [2 2 2], origin, datatype);<br />
save_nii(nii, &#8216;boxedhippo.nii&#8217;)</p></blockquote>
<p>We can then use these masks for signal extraction or any further processing.</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/04/14/bounding-box-for-wfu-pickatlas-masks/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Normalization in FSL</title>
		<link>http://nuclear-imaging.info/site_content/2011/03/30/normalization-in-fsl/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=normalization-in-fsl</link>
		<comments>http://nuclear-imaging.info/site_content/2011/03/30/normalization-in-fsl/#comments</comments>
		<pubDate>Wed, 30 Mar 2011 16:33:05 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Imaging]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[fsl]]></category>
		<category><![CDATA[normalization]]></category>
		<category><![CDATA[spatial]]></category>
		<category><![CDATA[warping]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=357</guid>
		<description><![CDATA[FSL: flirt is used to compute an intial affine normalization of the T1 weighted images; this is then fed to fnirt to compute the overall transformation. flirt is also used to register the EPI&#8217;s to the subject&#8217;s structural image. This was then used along with fnirt-s warp in applywarp to normalize the EPIs. Script for <a href='http://nuclear-imaging.info/site_content/2011/03/30/normalization-in-fsl/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p><strong>FSL:</strong> flirt is used to compute an intial affine normalization of the T1 weighted images; this is then fed to fnirt to compute the overall transformation. flirt is also used to register the EPI&#8217;s to the subject&#8217;s structural image. This was then used along with fnirt-s warp in applywarp to normalize the EPIs.</p>
<p><strong>
<p>Script for normalizing the T1-weighted structurals to the template: </p>
<p></strong></p>
<p><strong>Registering T1-structural to MNI152</strong></p>
<blockquote><p>bet my_structural my_betted_structural<br />
flirt -ref ${FSLDIR}/data/standard/MNI152_T1_2mm_brain -in my_betted_structural -omat my_affine_transf.mat<br />
fnirt &#8211;in=my_structural &#8211;aff=my_affine_transf.mat &#8211;cout=my_nonlinear_transf &#8211;config=T1_2_MNI152_2mm<br />
applywarp &#8211;ref=${FSLDIR}/data/standard/MNI152_T1_2mm &#8211;in=my_structural &#8211;warp=my_nonlinear_transf &#8211;out=my_warped_structural</p></blockquote>
<p><strong>Registering functional data to MNI152 (via structural scan)</strong></p>
<blockquote><p>bet my_structural my_betted_structural<br />
flirt -ref my_betted_structural -in my_functional -dof 7 -omat func2struct.mat<br />
flirt -ref ${FSLDIR}/data/standard/MNI152_T1_2mm_brain -in my_betted_structural -omat my_affine_transf.mat<br />
fnirt &#8211;in=my_structural &#8211;aff=my_affine_transf.mat &#8211;cout=my_nonlinear_transf &#8211;config=T1_2_MNI152_2mm<br />
applywarp &#8211;ref=${FSLDIR}/data/standard/MNI152_T1_2mm &#8211;in=my_functional &#8211;warp=my_nonlinear_transf &#8211;premat=func2struct.mat &#8211;out=my_warped_functional
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/03/30/normalization-in-fsl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reverse SSH tunnel: Home  NAT organizational network</title>
		<link>http://nuclear-imaging.info/site_content/2011/03/17/reverse-ssh-tunnel-home-nat-organizational-network/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=reverse-ssh-tunnel-home-nat-organizational-network</link>
		<comments>http://nuclear-imaging.info/site_content/2011/03/17/reverse-ssh-tunnel-home-nat-organizational-network/#comments</comments>
		<pubDate>Thu, 17 Mar 2011 18:13:12 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[nat]]></category>
		<category><![CDATA[reverse tunnel]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=351</guid>
		<description><![CDATA[On the destination computer type the following command. Replaceing middleuser with your name and replacing middle with the domain of the middle computer. ssh -R 10002:localhost:22 middleuser@middle This will open port 10002 for listening and forward all future connections to port 22 at destination. This connection must remain on the entire time to ensure that <a href='http://nuclear-imaging.info/site_content/2011/03/17/reverse-ssh-tunnel-home-nat-organizational-network/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>On the destination computer type the following command. Replaceing middleuser with your name and replacing middle with the domain of the middle computer.</p>
<blockquote><p>ssh -R 10002:localhost:22 middleuser@middle</p></blockquote>
<p>This will open port 10002 for listening and forward all future connections to port 22 at destination. This connection must remain on the entire time to ensure that you can access your destination computer whenever you want.</p>
<p>Now if sshd is set to use GatewayPorts you should be able to connect with this:</p>
<blockquote><p>ssh destinationuser@middle -p 10002</p></blockquote>
<p>If you are not sure if GatewayPorts is on or you don’t have the access to change it use the following method to connect:</p>
<p>First connect to the middle computer how you would normally.</p>
<blockquote><p>ssh user@middle</p></blockquote>
<p>Then connect to the localhost of the middle computer on port 10002.</p>
<blockquote><p>ssh user@localhost -p 10002</p></blockquote>
<p>Note: The port 10002 is arbitrary you can use any port you want.</p>
<p>You should now be remotely logged into your computer behind the NAT/Firewall. Enjoy.</p>
<p>Content copied from :http://www.marksanborn.net/howto/bypass-firewall-and-nat-with-reverse-ssh-tunnel/</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/03/17/reverse-ssh-tunnel-home-nat-organizational-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MAC address spoofing on Linux</title>
		<link>http://nuclear-imaging.info/site_content/2011/03/15/mac-address-spoofing-on-linux/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mac-address-spoofing-on-linux</link>
		<comments>http://nuclear-imaging.info/site_content/2011/03/15/mac-address-spoofing-on-linux/#comments</comments>
		<pubDate>Tue, 15 Mar 2011 23:17:58 +0000</pubDate>
		<dc:creator>slash_boot</dc:creator>
				<category><![CDATA[Linux and OSS]]></category>
		<category><![CDATA[duplicate MAC address]]></category>
		<category><![CDATA[MAC address]]></category>
		<category><![CDATA[manual edit]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[spoofing]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://nuclear-imaging.info/site_content/?p=349</guid>
		<description><![CDATA[If you are on a network that has MAC addresses hardwired, i.e. you can only access the network if a certain MAC address is plugged into a specific ethernet jack on the wall, you don&#8217;t have too many options. One option I used recently is spoofing the MAC address of your device. Its done by <a href='http://nuclear-imaging.info/site_content/2011/03/15/mac-address-spoofing-on-linux/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>If you are on a network that has MAC addresses hardwired, i.e. you can only access the network if a certain MAC address is plugged into a specific ethernet jack on the wall, you don&#8217;t have too many options.</p>
<p>One option I used recently is spoofing the MAC address of your device. Its done by editing the hardware address to match the MAC address of the device that&#8217;s allowed on that ethernet jack.</p>
<p>If you are using Linux, make a note of your current IP address in a text file.</p>
<blockquote><p>sudo ifconfig -a | grep eth0 > ~/Desktop/netaddressbak.txt</p></blockquote>
<p>Run the same command on the device that&#8217;s attached to the network to find its MAC address: Lets say its &#8211; 01:82:39:B2:41:30</p>
<p>Before you attach your new device to the ethernet cable, change its MAC address to the one listed above.</p>
<blockquote><p>sudo ifconfig eth0 down<br />
sudo ifconfig eth0 hw ether 01:82:39:B2:41:30<br />
sudo ifconfig eth0 up<br />
sudo ifconfig eth0 | grep HWaddr</p></blockquote>
<p>This should now list the address as 01:82:39:B2:41:30.</p>
<p>You can now attach this device on the network to gain full connectivity (unless there are some programs that are supposed to ping every once in a while).</p>
]]></content:encoded>
			<wfw:commentRss>http://nuclear-imaging.info/site_content/2011/03/15/mac-address-spoofing-on-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

