<?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>jude pereira&#039;s blog &#187; another snippet | code</title>
	<atom:link href="http://judepereira.com/blog/category/code/feed/" rel="self" type="application/rss+xml" />
	<link>http://judepereira.com/blog</link>
	<description>a terminal, an interface... and me!</description>
	<lastBuildDate>Sat, 21 Jan 2012 19:41:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>SEED hits the pit again #iknowvention</title>
		<link>http://judepereira.com/blog/seed-hits-the-pit-again-iknowvention/</link>
		<comments>http://judepereira.com/blog/seed-hits-the-pit-again-iknowvention/#comments</comments>
		<pubDate>Fri, 20 Jan 2012 07:52:00 +0000</pubDate>
		<dc:creator>jude pereira</dc:creator>
				<category><![CDATA[another snippet | code]]></category>
		<category><![CDATA[blunder]]></category>
		<category><![CDATA[c++]]></category>
		<category><![CDATA[competition]]></category>
		<category><![CDATA[iknowvention]]></category>
		<category><![CDATA[Infotech]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[SEED]]></category>
		<category><![CDATA[SEED Infotech]]></category>

		<guid isPermaLink="false">http://judepereira.com/blog/?p=1234</guid>
		<description><![CDATA[SEED continues to make mistakes. So is today&#8217;s challenge: #include int main(int argc, char *argv[]) { printf("%d",4["seed"]); return 0; } The answer for the above is 0, as the fourth element in the array &#8220;seed&#8221; does not exist. This is because of the index value, which starts from 0. Had it been 3, then it [...]]]></description>
		<wfw:commentRss>http://judepereira.com/blog/seed-hits-the-pit-again-iknowvention/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>SEED makes Blunder! #iknowvention</title>
		<link>http://judepereira.com/blog/seed-makes-blunder-iknowvention/</link>
		<comments>http://judepereira.com/blog/seed-makes-blunder-iknowvention/#comments</comments>
		<pubDate>Wed, 18 Jan 2012 01:20:51 +0000</pubDate>
		<dc:creator>jude pereira</dc:creator>
				<category><![CDATA[another snippet | code]]></category>
		<category><![CDATA[c++]]></category>
		<category><![CDATA[contest]]></category>
		<category><![CDATA[day 2]]></category>
		<category><![CDATA[iknowvention]]></category>
		<category><![CDATA[Infotech]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[SEED]]></category>
		<category><![CDATA[SEED Infotech]]></category>

		<guid isPermaLink="false">http://judepereira.com/blog/?p=1231</guid>
		<description><![CDATA[Alright, so I&#8217;m taking part in this SEED Infotech C programming contest, and here&#8217;s one of yesterday&#8217;s challenges: main() { if(printf("C for yourself how it works \n"); main(); } One of the options were a) C for yourself how it works infinate times Now isn&#8217;t that catchy? Look at it clearly, there&#8217;s on pair of [...]]]></description>
		<wfw:commentRss>http://judepereira.com/blog/seed-makes-blunder-iknowvention/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>/usr/local/bin/waitpid</title>
		<link>http://judepereira.com/blog/usrlocalbinwaitpid/</link>
		<comments>http://judepereira.com/blog/usrlocalbinwaitpid/#comments</comments>
		<pubDate>Tue, 26 Apr 2011 17:49:29 +0000</pubDate>
		<dc:creator>jude pereira</dc:creator>
				<category><![CDATA[another snippet | code]]></category>
		<category><![CDATA[gnu linux]]></category>
		<category><![CDATA[command execute]]></category>
		<category><![CDATA[detect PID end]]></category>
		<category><![CDATA[detect PID life]]></category>
		<category><![CDATA[execute command after pid]]></category>
		<category><![CDATA[pid exit]]></category>
		<category><![CDATA[pid quit]]></category>
		<category><![CDATA[wait for pid]]></category>

		<guid isPermaLink="false">http://judepereira.com/blog/?p=903</guid>
		<description><![CDATA[A quick script to wait for a certain pid, then once that quits, execute a command. You may ask, why not just do command1 &#038;&#038; command2 ? Well, if command1 exits with a non-zero exit status value, command2 will not get executed. Hence, I&#8217;ve brewed a quick script for this purpose. File: /usr/local/bin/waitpid #!/bin/sh # [...]]]></description>
		<wfw:commentRss>http://judepereira.com/blog/usrlocalbinwaitpid/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Coloured /var/log/messages at tty12</title>
		<link>http://judepereira.com/blog/coloured-varlogmessages-at-tty12/</link>
		<comments>http://judepereira.com/blog/coloured-varlogmessages-at-tty12/#comments</comments>
		<pubDate>Tue, 26 Apr 2011 17:29:24 +0000</pubDate>
		<dc:creator>jude pereira</dc:creator>
				<category><![CDATA[another snippet | code]]></category>
		<category><![CDATA[gentoo | sabayon | fedora]]></category>
		<category><![CDATA[gnu linux]]></category>
		<category><![CDATA[ccze]]></category>
		<category><![CDATA[coloured log]]></category>
		<category><![CDATA[display log on tty]]></category>
		<category><![CDATA[gentoo tty log messages]]></category>
		<category><![CDATA[syslog]]></category>
		<category><![CDATA[syslog colour]]></category>
		<category><![CDATA[tty12 log]]></category>

		<guid isPermaLink="false">http://judepereira.com/blog/?p=893</guid>
		<description><![CDATA[Reading logs could never become any more easier, at just a keystroke, you have your logs displayed where you want, in some fancy colour. They look great too. TTY&#8217;s can be accessed by pressing Alt + Ctrl + F[1 - 12] simultaneously. In the following, you&#8217;ll get a decent, colourized log display of /var/log/messages when [...]]]></description>
		<wfw:commentRss>http://judepereira.com/blog/coloured-varlogmessages-at-tty12/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>QEMU &#124; Quick Networking for TCP/UDP</title>
		<link>http://judepereira.com/blog/qemu-quick-networking-for-tcpudp/</link>
		<comments>http://judepereira.com/blog/qemu-quick-networking-for-tcpudp/#comments</comments>
		<pubDate>Thu, 31 Mar 2011 09:58:49 +0000</pubDate>
		<dc:creator>jude pereira</dc:creator>
				<category><![CDATA[another snippet | code]]></category>
		<category><![CDATA[gnu linux]]></category>
		<category><![CDATA[guest host network]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[qemu]]></category>
		<category><![CDATA[qemu dhcp]]></category>
		<category><![CDATA[qemu map ports]]></category>

		<guid isPermaLink="false">http://judepereira.com/blog/?p=864</guid>
		<description><![CDATA[Networking with a guest in QEMU is often a headache, TUN/TAP, seriously? Too hectic, let&#8217;s stick to the basics, TCP/UDP based. Instead of setting up a really complex set of configuration files, wouldn&#8217;t it be easy to just emulate the network card, DHCP the guest, and let it work right out of the box? Well [...]]]></description>
		<wfw:commentRss>http://judepereira.com/blog/qemu-quick-networking-for-tcpudp/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

