<?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>LEXO &#124; We don&#039;t learn for the school, we learn for life. &#187; Unix</title>
	<atom:link href="http://lexo.mx/category/unix/feed/" rel="self" type="application/rss+xml" />
	<link>http://lexo.mx</link>
	<description>Non scholae, sed vitae discimus</description>
	<lastBuildDate>Thu, 12 May 2011 01:07:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Story of Linux: Commemorating 20 Years of the Linux Operating System</title>
		<link>http://lexo.mx/2011/05/11/the-story-of-linux-commemorating-20-years-of-the-linux-operating-system/</link>
		<comments>http://lexo.mx/2011/05/11/the-story-of-linux-commemorating-20-years-of-the-linux-operating-system/#comments</comments>
		<pubDate>Thu, 12 May 2011 01:04:37 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>

		<guid isPermaLink="false">http://lexo.mx/?p=1570</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p><object style="height: 390px; width: 490px"><param name="movie" value="http://www.youtube.com/v/5ocq6_3-nEw?version=3"><param name="allowFullScreen" value="true"><param name="allowScriptAccess" value="always"><embed src="http://www.youtube.com/v/5ocq6_3-nEw?version=3" type="application/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width="490" height="390"></object></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2011/05/11/the-story-of-linux-commemorating-20-years-of-the-linux-operating-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Asterisk, DAHDI and Slackware 13.1</title>
		<link>http://lexo.mx/2011/01/14/asterisk-dahdi-and-slackware-13-1/</link>
		<comments>http://lexo.mx/2011/01/14/asterisk-dahdi-and-slackware-13-1/#comments</comments>
		<pubDate>Sat, 15 Jan 2011 00:08:44 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[Asterisk IP-PBX]]></category>
		<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1497</guid>
		<description><![CDATA[There&#8217;s just a &#8220;issue&#8221; for better configuration of Asterisk PBX/DAHDI with OpenVox A400P card under Slackware GNU/Linux 13.1 and here we&#8217;re going to see how to fix it. Lets go&#8230; Obviously, we need to install first (this isn&#8217;t a topic of installation): DAHDI Asterisk For setup the card OpenVox A400P we need to disable these [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s just a &#8220;issue&#8221; for better configuration of Asterisk PBX/DAHDI with OpenVox A400P card under Slackware GNU/Linux 13.1 and here we&#8217;re going to see how to fix it.</p>
<p>Lets go&#8230; Obviously, we need to install first (this isn&#8217;t a topic of installation):<br />
DAHDI<br />
Asterisk</p>
<p>For setup the card OpenVox A400P we need to disable these modules (we need use wctdm module of DAHDI):</p>
<p>hisax<br />
netjet</p>
<p>So well, we just add these next lines into /etc/modprobe.d/blacklist.conf and next boot there won&#8217;t be more conflicts between these modules. </p>
<p><code>blacklist netjet<br />
blacklist hisax</code></p>
<p>And that&#8217;s all, now we can configure/start the Asterisk IP PBX.</p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2011/01/14/asterisk-dahdi-and-slackware-13-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partition mounted with noexec option under GNU/Linux</title>
		<link>http://lexo.mx/2010/09/22/partition-mounted-with-noexec-option-under-gnulinux/</link>
		<comments>http://lexo.mx/2010/09/22/partition-mounted-with-noexec-option-under-gnulinux/#comments</comments>
		<pubDate>Wed, 22 Sep 2010 17:30:42 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1428</guid>
		<description><![CDATA[This experience happened when I was changing my home directory to other place/partition, you know there isn&#8217;t more free space xD The inconvenient for me went when I tried to execute a bash script, and I only got to see: /bin/sh: bad interpreter: Permission denied And I asked me: WTF? I checked first the script, [...]]]></description>
			<content:encoded><![CDATA[<p>This experience happened when I was changing my home directory to other place/partition, you know there isn&#8217;t more free space xD</p>
<p>The inconvenient for me went when I tried to execute a bash script, and I only got to see:</p>
<p>/bin/sh: bad interpreter: Permission denied</p>
<p>And I asked me: WTF? I checked first the script, then the permissions but all were ok, so again I asked me: WTF? so I looked the PATH variable and it was ok&#8230; and it was the moment when I decided to ask to san google xD</p>
<p>And I found the solution!!, the partition was mounted with noexec option and that&#8217;s why I couldn&#8217;t execute my bash script. </p>
<p>So the lesson for me was: If you want to execute something, don&#8217;t forget use exec option when mount the partition <img src='http://lexo.mx/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Have a nice execution!!</p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/09/22/partition-mounted-with-noexec-option-under-gnulinux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Modifying the home directory of an user in GNU/Linux</title>
		<link>http://lexo.mx/2010/09/21/modifying-the-home-directory-of-an-user-in-gnulinux/</link>
		<comments>http://lexo.mx/2010/09/21/modifying-the-home-directory-of-an-user-in-gnulinux/#comments</comments>
		<pubDate>Wed, 22 Sep 2010 00:17:08 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1422</guid>
		<description><![CDATA[Some times for some reason it&#8217;s necessary to change a home directory of a user and the correct form is using the command usermod: usermod -d /new/home username For more info about what other things we could do with this command look the man page.]]></description>
			<content:encoded><![CDATA[<p>Some times for some reason it&#8217;s necessary to change a home directory of a user and the correct form is using the command <em>usermod</em>:</p>
<p><code>usermod -d /new/home username</code></p>
<p>For more info about what other things we could do with this command look  the man page.</p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/09/21/modifying-the-home-directory-of-an-user-in-gnulinux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BASH tip &#8211; Search commands typed</title>
		<link>http://lexo.mx/2010/09/15/bash-tip-search-commands-typed/</link>
		<comments>http://lexo.mx/2010/09/15/bash-tip-search-commands-typed/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 22:57:37 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1389</guid>
		<description><![CDATA[If you want to make fast work helped by the commands used time ago, maybe you fond useful this tip: ctrl + r]]></description>
			<content:encoded><![CDATA[<p>If you want to make fast work helped by the commands used time ago, maybe you fond useful this tip:</p>
<p>ctrl + r</p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/09/15/bash-tip-search-commands-typed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HAProxy &#8211; High Availability Platform</title>
		<link>http://lexo.mx/2010/07/20/haproxy-high-availability-platform/</link>
		<comments>http://lexo.mx/2010/07/20/haproxy-high-availability-platform/#comments</comments>
		<pubDate>Tue, 20 Jul 2010 15:42:53 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1284</guid>
		<description><![CDATA[HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. HAProxy is known to reliably run on the following OS/Platforms : * Linux 2.4 on x86, [...]]]></description>
			<content:encoded><![CDATA[<p>HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing.</p>
<p> HAProxy is known to reliably run on the following OS/Platforms :</p>
<p>    * Linux 2.4 on x86, x86_64, Alpha, SPARC, MIPS, PARISC<br />
    * Linux 2.6 on x86, x86_64, ARM (ixp425), PPC64<br />
    * Solaris 8/9 on UltraSPARC 2 and 3<br />
    * Solaris 10 on Opteron and UltraSPARC<br />
    * FreeBSD 4.10 &#8211; 6.2 on x86<br />
    * OpenBSD 3.1 to -current on i386, amd64, macppc, alpha, sparc64 and VAX (check the ports) </p>
<p>Source:<br />
<a href="http://haproxy.1wt.eu">http://haproxy.1wt.eu</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/07/20/haproxy-high-availability-platform/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CMUcam3: Open Source Programmable Embedded Color Vision Platform</title>
		<link>http://lexo.mx/2010/07/09/cmucam3-open-source-programmable-embedded-color-vision-platform/</link>
		<comments>http://lexo.mx/2010/07/09/cmucam3-open-source-programmable-embedded-color-vision-platform/#comments</comments>
		<pubDate>Fri, 09 Jul 2010 23:59:38 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1252</guid>
		<description><![CDATA[The goal of the CMUcam project is to provide simple vision capabilities to small embedded systems in the form of an intelligent sensor. The CMUcam3 extends upon this idea by providing a flexible and easy to use open source development environment that complements a low cost hardware platform. The CMUcam3 is an ARM7TDMI based fully [...]]]></description>
			<content:encoded><![CDATA[<p>The goal of the CMUcam project is to provide simple vision capabilities to small embedded systems in the form of an intelligent sensor. The CMUcam3 extends upon this idea by providing a flexible and easy to use open source development environment that complements a low cost hardware platform. The CMUcam3 is an  ARM7TDMI based fully programmable embedded computer vision sensor. The main processor is the  NXP LPC2106 connected to an  Omnivision CMOS camera sensor module. Custom C code can be developed for the CMUcam3 using a port of the  GNU toolchain along with a set of open source libraries and example programs. Executables can be flashed onto the board using the serial port with no external downloading hardware required. </p>
<p>Source:<br />
<a href="http://cmucam.org/">http://cmucam.org</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/07/09/cmucam3-open-source-programmable-embedded-color-vision-platform/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GlusterFS</title>
		<link>http://lexo.mx/2010/05/12/glusterfs/</link>
		<comments>http://lexo.mx/2010/05/12/glusterfs/#comments</comments>
		<pubDate>Thu, 13 May 2010 03:40:50 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1147</guid>
		<description><![CDATA[Gluster Storage Platform is an open source clustered storage solution. The software is a powerful and flexible solution that simplifies the task of managing unstructured file data whether you have a few terabytes of storage or multiple petabytes. Gluster Storage Platform integrates the file system, an operating system layer, and a web-based management interface and [...]]]></description>
			<content:encoded><![CDATA[<p>Gluster Storage Platform is an open source clustered storage solution. The software is a powerful and flexible solution that simplifies the task of managing unstructured file data whether you have a few terabytes of storage or multiple petabytes. Gluster Storage Platform integrates the file system, an operating system layer, and a web-based management interface and installer.</p>
<p>Source:<br />
<a href="http://www.gluster.org">http://www.gluster.org</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/05/12/glusterfs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nano-X Window System</title>
		<link>http://lexo.mx/2010/05/11/nano-x-window-system/</link>
		<comments>http://lexo.mx/2010/05/11/nano-x-window-system/#comments</comments>
		<pubDate>Tue, 11 May 2010 21:11:07 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1138</guid>
		<description><![CDATA[The Nano-X Window System is an Open Source project aimed at bringing the features of modern graphical windowing environments to smaller devices and platforms. Nano-X allows applications to be built and tested on the Linux desktop, as well as cross-compiled for the target device. The Nano-X Window System was previously named Microwindows, but has been [...]]]></description>
			<content:encoded><![CDATA[<p>The Nano-X Window System is an Open Source project aimed at bringing the features of modern graphical windowing environments to smaller devices and platforms.  Nano-X allows applications to be built and tested on the Linux desktop, as well as cross-compiled for the target device.  The Nano-X Window System was previously named Microwindows, but has been renamed due to conflicts with Microsoft&#8217;s Windows trademark. There are two APIs implemented in the system, a Win32 API and an Xlib-like API.</p>
<p>Source:<br />
<a href="http://www.microwindows.org">http://www.microwindows.org</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/05/11/nano-x-window-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ceroboot/LinuxBIOS</title>
		<link>http://lexo.mx/2010/02/28/cerobootlinuxbios/</link>
		<comments>http://lexo.mx/2010/02/28/cerobootlinuxbios/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 05:27:07 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=1028</guid>
		<description><![CDATA[coreboot (formerly known as LinuxBIOS) is a Free Software project aimed at replacing the proprietary BIOS (firmware) you can find in most of today&#8217;s computers. It performs just a little bit of hardware initialization and then executes a so-called payload. With this separation of hardware initialization and later boot logic, coreboot is capable of scaling [...]]]></description>
			<content:encoded><![CDATA[<p><center><object width="320" height="265"><param name="movie" value="http://www.youtube.com/v/nuzRsXKm_NQ&#038;hl=en_US&#038;fs=1&#038;rel=0"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/nuzRsXKm_NQ&#038;hl=en_US&#038;fs=1&#038;rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="320" height="265"></embed></object></center><br />
</p>
<p><strong>coreboot</strong> (formerly known as LinuxBIOS) is a Free Software project aimed at replacing the proprietary BIOS (firmware) you can find in most of today&#8217;s computers. It performs just a little bit of hardware initialization and then executes a so-called payload.</p>
<p>With this separation of hardware initialization and later boot logic, coreboot is capable of scaling from specialized applications run directly from firmware, operating systems in Flash, and custom bootloaders to implementations of firmware standards like PCBIOS and EFI without having to carry features not necessary in the target application, reducing the amount of code and flash space required.</p>
<p>Source:<br />
<a href="http://www.coreboot.org">http://www.coreboot.org</a><code></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/02/28/cerobootlinuxbios/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The process tree with ps command</title>
		<link>http://lexo.mx/2010/02/11/the-process-tree-with-ps-command/</link>
		<comments>http://lexo.mx/2010/02/11/the-process-tree-with-ps-command/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 18:33:52 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=986</guid>
		<description><![CDATA[How to see the process tree with ps command? There&#8217;s some options: ps -ejH ps axjf Or also we can use other command: pstree More info: http://www.linfo.org/pstree.html http://linux.die.net/man/1/ps]]></description>
			<content:encoded><![CDATA[<p>How to see the process tree with ps command?</p>
<p>There&#8217;s some options: </p>
<p><code>ps -ejH</code><br />
<code>ps axjf</code></p>
<p>Or also we can use other command:</p>
<p><code>pstree</code></p>
<p>More info:<br />
<a href="http://www.linfo.org/pstree.html">http://www.linfo.org/pstree.html</a><br />
<a href="http://linux.die.net/man/1/ps">http://linux.die.net/man/1/ps</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/02/11/the-process-tree-with-ps-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check RAM speed and type</title>
		<link>http://lexo.mx/2010/02/10/check-ram-speed-and-type/</link>
		<comments>http://lexo.mx/2010/02/10/check-ram-speed-and-type/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 20:25:54 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=981</guid>
		<description><![CDATA[If you want to know the speed and type of your computer RAM module, it&#8217;s a method who helps you. So lets begin, we need to use biosdecode command, and this is the correct option: dmidecode --type 17 More info about this: http://www.cyberciti.biz/faq/check-ram-speed-linux http://linux.die.net/man/8/biosdecode]]></description>
			<content:encoded><![CDATA[<p>If you want to know the speed and type of your computer RAM module, it&#8217;s a method who helps you.</p>
<p>So lets begin,  we need to use <strong>biosdecode</strong> command, and this is the correct option:</p>
<p><code>dmidecode --type 17</code></p>
<p>More info about this:</p>
<p>http://www.cyberciti.biz/faq/check-ram-speed-linux</p>
<p>http://linux.die.net/man/8/biosdecode</p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/02/10/check-ram-speed-and-type/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>trapper sniffer</title>
		<link>http://lexo.mx/2010/01/14/trapper-sniffer/</link>
		<comments>http://lexo.mx/2010/01/14/trapper-sniffer/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 04:57:19 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=909</guid>
		<description><![CDATA[trapper is a sniffer &#038; ARP poisoning tool made in perl. The current version supports sniffing protocols like HTTP, FTP, telnet POP3, IMAP, SMTP, MSN, IRC, SMB, SIP, TeamSpeak and VCN. Also this tool include the attack known as APR ( ARP Poison Routing ). More protocols and types of attacks will be added in [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://nediam.com.mx/trapper/home.html">trapper</a> is a sniffer &#038; ARP poisoning tool made in perl. The current version supports sniffing protocols like HTTP, FTP, telnet POP3, IMAP, SMTP, MSN, IRC, SMB, SIP, TeamSpeak and VCN. Also this tool include the attack known as APR ( ARP Poison Routing ). More protocols and types of attacks will be added in the future. The development of Trapper was inspired in the excellent tool Cain, but we wanted a tool that also worked under Linux/Unix.</p>
<p><strong>Features:</strong><br />
   1. Supported protocols: HTTP, SMPT, IMAP, SMB, SIP, POP3, FTP, Telnet, IRC<br />
   2. HTTP Cookie Sniffing<br />
   3. IRC Chat Sniffing<br />
   4. SMPT sniffing (attachments supported)<br />
   5. MSN Chat Sniffing<br />
   6. ARP poison tool<br />
   7. Different types of ARP attack<br />
   8. Fake MAC tool<br />
   9. Firefox cookie injector<br />
  10. Passwords are saved automatically<br />
  11. Lenght of the packet option<br />
  12. Automatic Network Detection<br />
  13. Trapper.conf: You can add your own parameters to sniff HTTP values (yes like Cain); also choose if you wanna save or not the sniffed data and put your own ports on supported protocols</p>
<p>Source:<br />
 <a href="http://nediam.com.mx/trapper/home.html">http://nediam.com.mx/trapper/home.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/01/14/trapper-sniffer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LXDE &#8211; Lightweight X11 Desktop Environment</title>
		<link>http://lexo.mx/2010/01/08/lxde-lightweight-x11-desktop-environment/</link>
		<comments>http://lexo.mx/2010/01/08/lxde-lightweight-x11-desktop-environment/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 21:20:12 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[GNU/Linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=905</guid>
		<description><![CDATA[LXDE is an energy saving and extremely fast and performing desktop solution. It works well with computers on the low end of the performance spectrum such as new generation netbooks and other small mobile computers. Source: http://lxde.org]]></description>
			<content:encoded><![CDATA[<p>LXDE is an energy saving and extremely fast and performing desktop solution. It works well with computers on the low end of the performance spectrum such as new generation netbooks and other small mobile computers.</p>
<p>Source:<br />
<a href="http://lxde.org">http://lxde.org</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/01/08/lxde-lightweight-x11-desktop-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Howto see IP firewall rules via terminal</title>
		<link>http://lexo.mx/2010/01/08/howto-eee-ip-firewall-rules-via-terminal/</link>
		<comments>http://lexo.mx/2010/01/08/howto-eee-ip-firewall-rules-via-terminal/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 04:20:41 +0000</pubDate>
		<dc:creator>lexo</dc:creator>
				<category><![CDATA[pfSense]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://lexo.lx-networks.net/?p=898</guid>
		<description><![CDATA[If you want to see all rules of you firewall with PF using terminal you can do it with: pfctl -s rules We need to do it because the web manager of pfSense only shows the rules that you add by yourself, but there&#8217;s more roles created by default. More info]]></description>
			<content:encoded><![CDATA[<p>If you want to see all rules of you firewall with PF using terminal you can do it with:</p>
<p><code>pfctl -s rules</code></p>
<p>We need to do it because the web manager of pfSense only shows the rules that you add by yourself, but there&#8217;s more roles created by default.</p>
<p>More <a href="http://www.thedeepsky.com/howto/newbie_pf_guide.php">info</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lexo.mx/2010/01/08/howto-eee-ip-firewall-rules-via-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

