<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Hexalist Forums - All Forums]]></title>
		<link>http://hexalist.com/forums/</link>
		<description><![CDATA[Hexalist Forums - http://hexalist.com/forums]]></description>
		<pubDate>Thu, 09 Sep 2010 07:04:05 +0200</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Submit your proxy sites - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-42.html</link>
			<pubDate>Tue, 13 Jul 2010 20:35:22 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-42.html</guid>
			<description><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.unblocksites.org" target="_blank">Unblock Sites</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></description>
			<content:encoded><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.unblocksites.org" target="_blank">Unblock Sites</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Submit your proxy sites - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-41.html</link>
			<pubDate>Tue, 18 May 2010 22:40:57 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-41.html</guid>
			<description><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.freeproxysites.us" target="_blank">Free Proxy</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></description>
			<content:encoded><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.freeproxysites.us" target="_blank">Free Proxy</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Submit your proxy sites - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-40.html</link>
			<pubDate>Tue, 27 Apr 2010 21:33:11 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-40.html</guid>
			<description><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxyservers.biz" target="_blank">Proxy Servers</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></description>
			<content:encoded><![CDATA[Hello friends,<br />
<br />
Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxyservers.biz" target="_blank">Proxy Servers</a><br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New proxy topsite - No backlink required.]]></title>
			<link>http://hexalist.com/forums/thread-39.html</link>
			<pubDate>Mon, 22 Feb 2010 23:09:16 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-39.html</guid>
			<description><![CDATA[Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxysites.ws/" target="_blank">http://www.proxysites.ws/</a><br />
<br />
All free domains disallowed (eg: .tk, .co.cc, .co.cz, etc)<br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites<br />
<br />
Subdomains not allowed]]></description>
			<content:encoded><![CDATA[Feel free to submit your web proxies, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxysites.ws/" target="_blank">http://www.proxysites.ws/</a><br />
<br />
All free domains disallowed (eg: .tk, .co.cc, .co.cz, etc)<br />
<br />
Only web proxies allowed, no proxy topsites, proxy blog, or any other proxy related sites<br />
<br />
Subdomains not allowed]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Submit your proxies - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-38.html</link>
			<pubDate>Wed, 23 Dec 2009 17:22:28 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-38.html</guid>
			<description><![CDATA[Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
If your proxy is made for youtube<br />
add it to here <a href="http://www.proxyforyoutube.com/" target="_blank">http://www.proxyforyoutube.com/</a><br />
<br />
if you proxy is made for facebook<br />
add it here <a href="http://www.proxyforfacebook.com/" target="_blank">http://www.proxyforfacebook.com/</a><br />
<br />
If you proxy works for both youtube and facebook, submit them to both topsites.<br />
<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Only web proxy sites allowed, no spamming please.]]></description>
			<content:encoded><![CDATA[Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
If your proxy is made for youtube<br />
add it to here <a href="http://www.proxyforyoutube.com/" target="_blank">http://www.proxyforyoutube.com/</a><br />
<br />
if you proxy is made for facebook<br />
add it here <a href="http://www.proxyforfacebook.com/" target="_blank">http://www.proxyforfacebook.com/</a><br />
<br />
If you proxy works for both youtube and facebook, submit them to both topsites.<br />
<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Only web proxy sites allowed, no spamming please.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Web Proxy Sites - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-37.html</link>
			<pubDate>Tue, 22 Dec 2009 17:13:35 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-37.html</guid>
			<description><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.webproxysites.org" target="_blank">http://www.webproxysites.org</a><br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></description>
			<content:encoded><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.webproxysites.org" target="_blank">http://www.webproxysites.org</a><br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Proxy Server Websites]]></title>
			<link>http://hexalist.com/forums/thread-36.html</link>
			<pubDate>Wed, 16 Dec 2009 14:59:31 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-36.html</guid>
			<description><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxyserverwebsites.com/" target="_blank">http://www.proxyserverwebsites.com/</a><br />
<br />
All free tld's allowed, example: co.cc, cz.cc, eu.tv, etc<br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.]]></description>
			<content:encoded><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxyserverwebsites.com/" target="_blank">http://www.proxyserverwebsites.com/</a><br />
<br />
All free tld's allowed, example: co.cc, cz.cc, eu.tv, etc<br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MyspaceProxyList.Com - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-35.html</link>
			<pubDate>Tue, 15 Dec 2009 16:17:45 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-35.html</guid>
			<description><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.myspaceproxylist.com" target="_blank">http://www.myspaceproxylist.com</a><br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Please make sure your proxy work on myspace.]]></description>
			<content:encoded><![CDATA[New proxy topsite<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.myspaceproxylist.com" target="_blank">http://www.myspaceproxylist.com</a><br />
<br />
Only web proxy sites allowed... Spam submissions will result in your IP banned.<br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Please make sure your proxy work on myspace.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ProxyServerList.Org - No backlink required]]></title>
			<link>http://hexalist.com/forums/thread-34.html</link>
			<pubDate>Tue, 24 Nov 2009 13:06:38 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-34.html</guid>
			<description><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
Only proxy sites , NO BLOGS, INFORMATION SITES OR TOPSITES<br />
<br />
<a href="http://www.proxyserverlist.org/" target="_blank">http://www.proxyserverlist.org/</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></description>
			<content:encoded><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
Only proxy sites , NO BLOGS, INFORMATION SITES OR TOPSITES<br />
<br />
<a href="http://www.proxyserverlist.org/" target="_blank">http://www.proxyserverlist.org/</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[GoodProxySites.Com - New Proxy Toplist]]></title>
			<link>http://hexalist.com/forums/thread-33.html</link>
			<pubDate>Wed, 04 Nov 2009 22:41:32 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-33.html</guid>
			<description><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.goodproxysites.com" target="_blank">http://www.goodproxysites.com</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></description>
			<content:encoded><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.goodproxysites.com" target="_blank">http://www.goodproxysites.com</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ProxySitesList.Net - New Proxy Topsite]]></title>
			<link>http://hexalist.com/forums/thread-32.html</link>
			<pubDate>Mon, 02 Nov 2009 22:12:33 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-32.html</guid>
			<description><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxysiteslist.net" target="_blank">http://www.proxysiteslist.net</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Your site gets auto approved, so no waiting for your site to go live.]]></description>
			<content:encoded><![CDATA[Announcing new proxy toplist,<br />
<br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
<br />
<a href="http://www.proxysiteslist.net" target="_blank">http://www.proxysiteslist.net</a><br />
<br />
All free domains allowed, co.cc, cz.cc, eu.tv, etc<br />
<br />
Your site gets auto approved, so no waiting for your site to go live.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SchoolProxySites.Net - New Proxy Toplist]]></title>
			<link>http://hexalist.com/forums/thread-31.html</link>
			<pubDate>Tue, 27 Oct 2009 12:01:40 +0100</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-31.html</guid>
			<description><![CDATA[Announcing new proxy toplist,<br />
 <br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
 <br />
<a href="http://www.schoolproxysites.net" target="_blank">http://www.schoolproxysites.net</a>]]></description>
			<content:encoded><![CDATA[Announcing new proxy toplist,<br />
 <br />
Feel free to submit your proxy sites, NO BACKLINK REQUIRED<br />
 <br />
<a href="http://www.schoolproxysites.net" target="_blank">http://www.schoolproxysites.net</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[UnblockedProxySites.Com Toplist - No backlink required.]]></title>
			<link>http://hexalist.com/forums/thread-30.html</link>
			<pubDate>Mon, 05 Oct 2009 15:08:01 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-30.html</guid>
			<description><![CDATA[<a href="http://www.unblockedproxysites.com/" target="_blank">http://www.unblockedproxysites.com/</a><br />
<br />
** New proxy list, Soon going to have loads of traffic..<br />
<br />
** No backlink required for limited time. It's best time to get your proxies on top of popular proxies page.<br />
<br />
** Just register an account and validate your email. Start submitting your proxies.<br />
<br />
** Your site will be approved automatically. So no waiting for your site to appear live.<br />
<br />
** After few days site will become 'backlink required', so this is right time to <a href="http://www.unblockedproxysites.com/submit-proxy.php" target="_blank">submit your proxies</a>..]]></description>
			<content:encoded><![CDATA[<a href="http://www.unblockedproxysites.com/" target="_blank">http://www.unblockedproxysites.com/</a><br />
<br />
** New proxy list, Soon going to have loads of traffic..<br />
<br />
** No backlink required for limited time. It's best time to get your proxies on top of popular proxies page.<br />
<br />
** Just register an account and validate your email. Start submitting your proxies.<br />
<br />
** Your site will be approved automatically. So no waiting for your site to appear live.<br />
<br />
** After few days site will become 'backlink required', so this is right time to <a href="http://www.unblockedproxysites.com/submit-proxy.php" target="_blank">submit your proxies</a>..]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Link with hexalist.com]]></title>
			<link>http://hexalist.com/forums/thread-29.html</link>
			<pubDate>Thu, 28 May 2009 02:01:38 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-29.html</guid>
			<description><![CDATA[If you would like a link to your site featured on hexalist.com (a dofollow link, permanent in the footer) you can send me a PM, <a href="http://hexalist.com/about.php" target="_blank">contact me at hexalist.com</a>, or reply here.<br />
<br />
If you have any site PR2 or higher, I would be interested in linking with you.]]></description>
			<content:encoded><![CDATA[If you would like a link to your site featured on hexalist.com (a dofollow link, permanent in the footer) you can send me a PM, <a href="http://hexalist.com/about.php" target="_blank">contact me at hexalist.com</a>, or reply here.<br />
<br />
If you have any site PR2 or higher, I would be interested in linking with you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SSL icons added]]></title>
			<link>http://hexalist.com/forums/thread-28.html</link>
			<pubDate>Fri, 22 May 2009 19:09:59 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-28.html</guid>
			<description><![CDATA[SSL icons have now been integrated for sites that support SSL.<br />
<br />
This should make it easier for people to find proxies that need to bypass websense. So far pretty much all proxies seem to be bypassing websense when they are SSL-enabled.]]></description>
			<content:encoded><![CDATA[SSL icons have now been integrated for sites that support SSL.<br />
<br />
This should make it easier for people to find proxies that need to bypass websense. So far pretty much all proxies seem to be bypassing websense when they are SSL-enabled.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Basic ip subnetting]]></title>
			<link>http://hexalist.com/forums/thread-27.html</link>
			<pubDate>Tue, 12 May 2009 20:29:19 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-27.html</guid>
			<description><![CDATA[This file is copyrighted, but i'm uploading it for educational use only! This is allowed as stated in the pdf:<br />
<br />
Copyright © 2006 – Dale R. Henninger – For Non-Commercial/Educational Use Only]]></description>
			<content:encoded><![CDATA[This file is copyrighted, but i'm uploading it for educational use only! This is allowed as stated in the pdf:<br />
<br />
Copyright © 2006 – Dale R. Henninger – For Non-Commercial/Educational Use Only]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Discovering whos on your network]]></title>
			<link>http://hexalist.com/forums/thread-26.html</link>
			<pubDate>Tue, 12 May 2009 20:26:24 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-26.html</guid>
			<description><![CDATA[This file is copyrighted, but I'm uploading it for educational use only! This is allowed as stated in the pdf:<br />
<br />
Copyright © 2006 – Dale R. Henninger – For Non-Commercial/Educational Use Only]]></description>
			<content:encoded><![CDATA[This file is copyrighted, but I'm uploading it for educational use only! This is allowed as stated in the pdf:<br />
<br />
Copyright © 2006 – Dale R. Henninger – For Non-Commercial/Educational Use Only]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Linux Structure]]></title>
			<link>http://hexalist.com/forums/thread-25.html</link>
			<pubDate>Tue, 12 May 2009 20:21:31 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-25.html</guid>
			<description><![CDATA[Credits too: <a href="http://tutorials.freeskills.com/the-structure-of-linux.htm" target="_blank">http://tutorials.freeskills.com/the-stru...-linux.htm</a><br />
<br />
    * The Kernel<br />
      This is the heart of the Linux Operating System. It performs the tasks that create and maintain the Linux environment. It keeps track of the disks, tapes, printers, terminals, communication lines and any other devices attached to the computer. It also interfaces between the computer's hardware and the users<br />
    * The Shell<br />
      This is a program that interfaces between the user and the Linux Operating System. It listens to the user's terminal and translates the actions requested by the user. There are a number of different Shells that may be used. See section on The Shell<br />
    * Utilities and Application Programs<br />
      Utilities are the Linux Commands. Application Programs, such as Word Processors, Spreadsheets and Database Management Systems, may be installed alongside the Linux Commands. A user may run a utility or application through the shell <br />
<br />
The Shell<br />
<br />
The Shell is a program that provides an interpreter and interface between the user and the Linux Operating System. It executes commands that are read either from a terminal or from a file. Files containing commands may be created, allowing users to build their own commands. In this manner, users may tailor Linux to their individual requirements and style.<br />
<br />
There are a number of different Shells. Each provides a slightly different interface between the user and the Linux Operating System. The most important shells that originated from the Unix operating system are:<br />
<br />
<img src="http://tutorials.freeskills.com/images/articles/266/image1.gif" border="0" alt="[Image: image1.gif&#93;" /><br />
<br />
There are other shells that are less widely used and not available on many machines. For example, there is the Restricted Shell - rsh. This restricts the area of memory the user may access to his or her own directory, thus limiting access to all other users' files.<br />
<br />
All of these shell interfaces are available to Linux. However, there are other shells that have been developed since, most generally for Linux: ash, tcsh and zsh are available on most versions of Linux. However, the most widely used, originally Linux-based shell is the Bourne-Again shell (bash). Based on the original Bourne shell, it has similar extensions as the Korn shell, plus its own further extensions.<br />
<br />
Linux also offers a windows-based shell interface, commonly known as X-Windows or simply as X. More akin to the Mackintosh windows than Microsoft windows, it is another method of interfacing with the Linux kernel. However, X-Windows interfaces are not considered on this course.<br />
<br />
A command issued by a user may be run in the present shell, or the shell itself may start up another copy of itself in which to run that command. In this way, a user may run several commands at the same time. A secondary shell is called a sub-shell.<br />
<br />
When a user logs onto the System, a shell is automatically started. This will monitor the user's terminal, waiting for the issue of any commands. The type of shell used is stored in a file called passwd in the subdirectory etc (see Section 3.2). Any other shell may be run as a sub-shell by issuing it as a command. For example, /usr/bin/ksh will run a Korn shell. The original shell will still be running - in background mode - until the Korn shell is terminated.<br />
<br />
Users<br />
<br />
Linux is a multi-user operating system. Each user will require to create and access his or her own files. These files must be secure from other users on the system. Because of this, each user has a unique identification on a Linux system, with the option of a password to enhance security.<br />
<br />
There are two types of user on a Linux system:<br />
<br />
    * Ordinary Users<br />
      An ordinary user has a Home Directory under which files and sub-directories are normally stored. After logging onto the system, a user is normally taken directly to that directory.<br />
<br />
      An ordinary user is a member of a Group of users. For security reasons, files (and directories) owned by a user may be accessed and used by the user, other members of the user's group and all other users at different levels of permission. For example, a file may be read and altered by the user that owns it, may only be read by other members of the same group and may not be accessed at all by any other user.<br />
    * Super-User<br />
      A super-user is a privileged user who has full access to all files, regardless to whoever owns them or what their access permissions are.<br />
<br />
      The super-user has a position of responsibility: to administer and maintain the system.<br />
<br />
      The super-user is normally known as root. root's Home directory is the primary directory of the system, under which all other directories and all files are stored.]]></description>
			<content:encoded><![CDATA[Credits too: <a href="http://tutorials.freeskills.com/the-structure-of-linux.htm" target="_blank">http://tutorials.freeskills.com/the-stru...-linux.htm</a><br />
<br />
    * The Kernel<br />
      This is the heart of the Linux Operating System. It performs the tasks that create and maintain the Linux environment. It keeps track of the disks, tapes, printers, terminals, communication lines and any other devices attached to the computer. It also interfaces between the computer's hardware and the users<br />
    * The Shell<br />
      This is a program that interfaces between the user and the Linux Operating System. It listens to the user's terminal and translates the actions requested by the user. There are a number of different Shells that may be used. See section on The Shell<br />
    * Utilities and Application Programs<br />
      Utilities are the Linux Commands. Application Programs, such as Word Processors, Spreadsheets and Database Management Systems, may be installed alongside the Linux Commands. A user may run a utility or application through the shell <br />
<br />
The Shell<br />
<br />
The Shell is a program that provides an interpreter and interface between the user and the Linux Operating System. It executes commands that are read either from a terminal or from a file. Files containing commands may be created, allowing users to build their own commands. In this manner, users may tailor Linux to their individual requirements and style.<br />
<br />
There are a number of different Shells. Each provides a slightly different interface between the user and the Linux Operating System. The most important shells that originated from the Unix operating system are:<br />
<br />
<img src="http://tutorials.freeskills.com/images/articles/266/image1.gif" border="0" alt="[Image: image1.gif]" /><br />
<br />
There are other shells that are less widely used and not available on many machines. For example, there is the Restricted Shell - rsh. This restricts the area of memory the user may access to his or her own directory, thus limiting access to all other users' files.<br />
<br />
All of these shell interfaces are available to Linux. However, there are other shells that have been developed since, most generally for Linux: ash, tcsh and zsh are available on most versions of Linux. However, the most widely used, originally Linux-based shell is the Bourne-Again shell (bash). Based on the original Bourne shell, it has similar extensions as the Korn shell, plus its own further extensions.<br />
<br />
Linux also offers a windows-based shell interface, commonly known as X-Windows or simply as X. More akin to the Mackintosh windows than Microsoft windows, it is another method of interfacing with the Linux kernel. However, X-Windows interfaces are not considered on this course.<br />
<br />
A command issued by a user may be run in the present shell, or the shell itself may start up another copy of itself in which to run that command. In this way, a user may run several commands at the same time. A secondary shell is called a sub-shell.<br />
<br />
When a user logs onto the System, a shell is automatically started. This will monitor the user's terminal, waiting for the issue of any commands. The type of shell used is stored in a file called passwd in the subdirectory etc (see Section 3.2). Any other shell may be run as a sub-shell by issuing it as a command. For example, /usr/bin/ksh will run a Korn shell. The original shell will still be running - in background mode - until the Korn shell is terminated.<br />
<br />
Users<br />
<br />
Linux is a multi-user operating system. Each user will require to create and access his or her own files. These files must be secure from other users on the system. Because of this, each user has a unique identification on a Linux system, with the option of a password to enhance security.<br />
<br />
There are two types of user on a Linux system:<br />
<br />
    * Ordinary Users<br />
      An ordinary user has a Home Directory under which files and sub-directories are normally stored. After logging onto the system, a user is normally taken directly to that directory.<br />
<br />
      An ordinary user is a member of a Group of users. For security reasons, files (and directories) owned by a user may be accessed and used by the user, other members of the user's group and all other users at different levels of permission. For example, a file may be read and altered by the user that owns it, may only be read by other members of the same group and may not be accessed at all by any other user.<br />
    * Super-User<br />
      A super-user is a privileged user who has full access to all files, regardless to whoever owns them or what their access permissions are.<br />
<br />
      The super-user has a position of responsibility: to administer and maintain the system.<br />
<br />
      The super-user is normally known as root. root's Home directory is the primary directory of the system, under which all other directories and all files are stored.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Regular Expressions: Perl (kahrns favorite language ;) )]]></title>
			<link>http://hexalist.com/forums/thread-24.html</link>
			<pubDate>Tue, 12 May 2009 20:19:07 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-24.html</guid>
			<description><![CDATA[Credits to: <a href="http://tutorials.freeskills.com/beginning-perl-part-1-regular-expressions-what-are-they-interpolation.htm" target="_blank">http://tutorials.freeskills.com/beginnin...lation.htm</a><br />
<br />
However, regular expressions are a very big area - they're one of the most powerful features of Perl. We're going to break our treatment of them up into six sections:<br />
<br />
    * Basic patterns<br />
    * Special characters to use<br />
    * Quantifiers, anchors and memorizing patterns<br />
    * Matching, substituting, and transforming text using patterns<br />
    * Backtracking<br />
    * A quick look at some simple pitfalls <br />
<br />
Generally speaking, if you want to ask perl something about a piece of text, regular expressions are going to be your first port of call - however, there's probably one simple question burning in your head...<br />
<br />
What Are They?<br />
<br />
The term "Regular Expression" (now commonly abbreviated to "RegExp" or even "RE") simply refers to a pattern that follows the rules of syntax outlined in the rest of this chapter. Regular expressions are not limited to perl - Unix utilities such as sed and egrep use the same notation for finding patterns in text. So why aren't they just called 'search patterns' or something less obscure?<br />
<br />
Well, the actual phrase itself originates from the mid-fifties when a mathematician called Stephen Kleene developed a notation for manipulating 'regular sets'. Perl's regular expressions have grown and grown beyond the original notation and have significantly extended the original system, but some of Kleene's notation remains, and the name has stuck.<br />
<br />
Patterns<br />
<br />
History lessons aside, it's all about identifying patterns in text. So what constitutes a pattern? And how do you compare it against something?<br />
<br />
The simplest pattern is a word - a simple sequence of characters - and we may, for example, want to ask perl whether a certain string contains that word. Now, we can do this with the techniques we have already seen: We want to split the string into separate words, and then test to see if each word is the one we're looking for. Here's how we might do that:<br />
<br />
#!/usr/bin/perl<br />
# match1.plx<br />
use warnings;<br />
use strict;<br />
my &#36;found = 0;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
my &#36;sought = "people";<br />
foreach my &#36;word (split) {<br />
if (&#36;word eq &#36;sought) {<br />
&#36;found = 1;<br />
last;<br />
}<br />
}<br />
if (&#36;found) {<br />
print "Hooray! Found the word 'people'\n";<br />
} <br />
<br />
Sure enough the program returns success:<br />
<br />
&gt;perl match1.plx<br />
<br />
Hooray! Found the word 'people'<br />
&gt;<br />
<br />
But that's messy! It's complicated, and it's slow to boot! Worse still, the split function (which breaks each of our lines up into a list of 'words' - we'll see more of this, later on in the chapter) actually keeps all the punctuation - the string 'you ' wouldn't be found in the above, whereas 'you... ' would. This looks like a hard problem, but it should be easy. Perl was designed to make easy tasks easy and hard things possible, so there should be a better way to do this. This is how it looks using a regular expression:<br />
<br />
#!/usr/bin/perl# match1.plxuse warnings;use strict;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case."; <br />
<br />
if (&#36;_ =~ /people/) {<br />
print "Hooray! Found the word 'people'\n";<br />
} <br />
<br />
This is much, much easier and yeilds the same result. We place the text we want to find between forward slashes - that's the regular expression part - that's our pattern, what we're trying to match. We also need to tell perl which particular string we're looking for in that pattern. We do this with the =~ operator. This returns 1 if the pattern match was successful (in our case, whether the character sequence 'people' was found in the string) and the undefined value if it wasn't.<br />
<br />
Before we go on to more complicated patterns, let's just have a quick look at that syntax. As we noted previously, a lot of Perl's operations take &#36;_ as a default argument, and regular expressions are one such operation. Since we have the text we want to test in &#36;_ , we don't need to use the =~ operator to 'bind' the pattern to another string. We could write the above even more simply:<br />
<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case."; <br />
<br />
if (/people/) { <br />
print "Hooray! Found the word 'people'\n";} <br />
<br />
Alternatively, we might want to test for the pattern not matching - the word not being found. Obviously, we could say unless (/people/) , but if the text we're looking at isn't in &#36;_ , we may also use the negative form of that =~ operator, which is !~ . For example:<br />
<br />
#!/usr/bin/perl<br />
# nomatch.plx<br />
use warnings;<br />
use strict;<br />
my &#36;gibson =<br />
"Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (&#36;gibson !~ /fish/) {<br />
print "There are no fish in William Gibson.\n";<br />
} <br />
<br />
True to form, for cyberpunk books that don't regularly involve fish, we get the result.<br />
<br />
&gt;perl nomatch.plx<br />
<br />
There are no fish in William Gibson.<br />
&gt; <br />
<br />
Literal text is the simplest regular expression of all to look for, but we needn't look for just the one word - we could look for any particular phrase. However, we need to make sure that we exactly match all the characters: words (with correct capitalization), numbers, punctuation, and even whitespace:<br />
<br />
#!/usr/bin/perl<br />
# match2.plx<br />
use warnings;<br />
use strict;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (/I do/) {<br />
print "'I do' is in that string.\n";<br />
}<br />
if (/sometimes Case/) {<br />
print "'sometimes Case' matched.\n";<br />
} <br />
<br />
Let's run this program and see what happens:<br />
<br />
&gt;perl match2.plx<br />
'I do' is in that string.<br />
&gt;<br />
<br />
The other string didn't match, even though those two words are there. This is because everything in a regular expression has to match the string, from start to finish: first "sometimes", then a space, then "Case". In &#36;_ , there was a comma before the space, so it didn't match exactly. Similarly, spaces inside the pattern are significant:<br />
<br />
#!/usr/bin/perl<br />
# match3.plx<br />
use warnings;<br />
use strict;<br />
my &#36;test1 = "The dog is in the kennel";<br />
my &#36;test2 = "The sheepdog is in the field";<br />
if (&#36;test1 =~ / dog/) {<br />
print "This dog's at home.\n";<br />
} <br />
if (&#36;test2 =~ / dog/) {<br />
print "This dog's at work.\n";<br />
} <br />
<br />
This will only find the first dog, as perl was looking for a space followed by the three letters, 'dog':<br />
<br />
&gt;perl match3.plx<br />
This dog's at home.<br />
&gt;<br />
<br />
So, for the moment, it looks like we shall have to specify our patterns with absolute precision. As another example, look at this:<br />
<br />
#!/usr/bin/perl<br />
# match4.plx<br />
use warnings;<br />
use strict; <br />
<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (/case/) {<br />
print "I guess it's just the way I'm made.\n";<br />
} else {<br />
print "Case? Where are you, Case?\n";<br />
} <br />
<br />
&gt; perl match4.plx<br />
Case? Where are you, Case?<br />
&gt; <br />
<br />
Hmm, no match. Why not? Because we asked for a small 'c' when we had a big 'C' - regexps are (if you'll pardon the pun) case-sensitive. We can get around this by asking perl to compare insensitively, and we do this by putting an 'i' (for 'insensitive') after the closing slash. If we alter the code above as follows:<br />
<br />
if (/case/i) { <br />
print "I guess it's just the way I'm made.\n";} else {<br />
print "Case? Where are you, Case?\n";} <br />
<br />
then we find him:<br />
<br />
&gt;perl match4.plx<br />
I guess it's just the way I'm made.<br />
&gt;<br />
<br />
This 'i ' is one of several modifiers that we can add to the end of the regular expression to change its behavior slightly. We'll see more of them later on.<br />
<br />
Continued... &lt;-vs_break&gt; Interpolation<br />
<br />
Regular expressions work a little like double-quoted strings; variables and metacharacters are interpolated. This allows us to store patterns in variables and determine what we are matching when we run the program - we don't need to have them hard-coded in:<br />
<br />
Try it out - Pattern Tester<br />
<br />
This program will ask the user for a pattern and then test to see if it matches our string. We can use this throughout the chapter to help us test the various different styles of pattern we'll be looking at:<br />
<br />
#!/usr/bin/perl<br />
# matchtest.plx<br />
use warnings;<br />
use strict;<br />
&#36;_ = q("I wonder what the Entish is for 'yes' and 'no'," he thought.);<br />
# Tolkien, Lord of the Rings<br />
print "Enter some text to find: ";<br />
my &#36;pattern = ;<br />
chomp(&#36;pattern); <br />
<br />
if (/&#36;pattern/) {<br />
print "The text matches the pattern '&#36;pattern'.\n";<br />
} else {<br />
print "'&#36;pattern' was not found.\n";<br />
} <br />
<br />
Now we can test out a few things:<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: wonder<br />
The text matches the pattern 'wonder'.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: entish<br />
'entish' was not found.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: hough<br />
The text matches the pattern 'hough'.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: and 'no',<br />
The text matches the pattern 'and 'no''.<br />
<br />
Pretty straightforward, and I'm sure you could all spot those not in &#36;_ as well.<br />
<br />
How It Works<br />
<br />
matchtest.plx has its basis in the three lines:<br />
<br />
my &#36;pattern = ;chomp(&#36;pattern);<br />
if (/&#36;pattern/) { <br />
<br />
We're taking a line of text from the user. Then, since it will end in a new line, and we don't necessarily want to find a new line in our pattern, we chomp it away. Now we do our test.<br />
<br />
Since we're not using the =~ operator, the test will be looking at the variable &#36;_ . The regular expression is /&#36;pattern/ , and just like the double-quoted string "&#36;pattern" , the variable &#36;pattern is interpolated. Hence, the regular expression is purely and simply whatever the user typed in, once we've got rid of the new line.]]></description>
			<content:encoded><![CDATA[Credits to: <a href="http://tutorials.freeskills.com/beginning-perl-part-1-regular-expressions-what-are-they-interpolation.htm" target="_blank">http://tutorials.freeskills.com/beginnin...lation.htm</a><br />
<br />
However, regular expressions are a very big area - they're one of the most powerful features of Perl. We're going to break our treatment of them up into six sections:<br />
<br />
    * Basic patterns<br />
    * Special characters to use<br />
    * Quantifiers, anchors and memorizing patterns<br />
    * Matching, substituting, and transforming text using patterns<br />
    * Backtracking<br />
    * A quick look at some simple pitfalls <br />
<br />
Generally speaking, if you want to ask perl something about a piece of text, regular expressions are going to be your first port of call - however, there's probably one simple question burning in your head...<br />
<br />
What Are They?<br />
<br />
The term "Regular Expression" (now commonly abbreviated to "RegExp" or even "RE") simply refers to a pattern that follows the rules of syntax outlined in the rest of this chapter. Regular expressions are not limited to perl - Unix utilities such as sed and egrep use the same notation for finding patterns in text. So why aren't they just called 'search patterns' or something less obscure?<br />
<br />
Well, the actual phrase itself originates from the mid-fifties when a mathematician called Stephen Kleene developed a notation for manipulating 'regular sets'. Perl's regular expressions have grown and grown beyond the original notation and have significantly extended the original system, but some of Kleene's notation remains, and the name has stuck.<br />
<br />
Patterns<br />
<br />
History lessons aside, it's all about identifying patterns in text. So what constitutes a pattern? And how do you compare it against something?<br />
<br />
The simplest pattern is a word - a simple sequence of characters - and we may, for example, want to ask perl whether a certain string contains that word. Now, we can do this with the techniques we have already seen: We want to split the string into separate words, and then test to see if each word is the one we're looking for. Here's how we might do that:<br />
<br />
#!/usr/bin/perl<br />
# match1.plx<br />
use warnings;<br />
use strict;<br />
my &#36;found = 0;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
my &#36;sought = "people";<br />
foreach my &#36;word (split) {<br />
if (&#36;word eq &#36;sought) {<br />
&#36;found = 1;<br />
last;<br />
}<br />
}<br />
if (&#36;found) {<br />
print "Hooray! Found the word 'people'\n";<br />
} <br />
<br />
Sure enough the program returns success:<br />
<br />
&gt;perl match1.plx<br />
<br />
Hooray! Found the word 'people'<br />
&gt;<br />
<br />
But that's messy! It's complicated, and it's slow to boot! Worse still, the split function (which breaks each of our lines up into a list of 'words' - we'll see more of this, later on in the chapter) actually keeps all the punctuation - the string 'you ' wouldn't be found in the above, whereas 'you... ' would. This looks like a hard problem, but it should be easy. Perl was designed to make easy tasks easy and hard things possible, so there should be a better way to do this. This is how it looks using a regular expression:<br />
<br />
#!/usr/bin/perl# match1.plxuse warnings;use strict;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case."; <br />
<br />
if (&#36;_ =~ /people/) {<br />
print "Hooray! Found the word 'people'\n";<br />
} <br />
<br />
This is much, much easier and yeilds the same result. We place the text we want to find between forward slashes - that's the regular expression part - that's our pattern, what we're trying to match. We also need to tell perl which particular string we're looking for in that pattern. We do this with the =~ operator. This returns 1 if the pattern match was successful (in our case, whether the character sequence 'people' was found in the string) and the undefined value if it wasn't.<br />
<br />
Before we go on to more complicated patterns, let's just have a quick look at that syntax. As we noted previously, a lot of Perl's operations take &#36;_ as a default argument, and regular expressions are one such operation. Since we have the text we want to test in &#36;_ , we don't need to use the =~ operator to 'bind' the pattern to another string. We could write the above even more simply:<br />
<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case."; <br />
<br />
if (/people/) { <br />
print "Hooray! Found the word 'people'\n";} <br />
<br />
Alternatively, we might want to test for the pattern not matching - the word not being found. Obviously, we could say unless (/people/) , but if the text we're looking at isn't in &#36;_ , we may also use the negative form of that =~ operator, which is !~ . For example:<br />
<br />
#!/usr/bin/perl<br />
# nomatch.plx<br />
use warnings;<br />
use strict;<br />
my &#36;gibson =<br />
"Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (&#36;gibson !~ /fish/) {<br />
print "There are no fish in William Gibson.\n";<br />
} <br />
<br />
True to form, for cyberpunk books that don't regularly involve fish, we get the result.<br />
<br />
&gt;perl nomatch.plx<br />
<br />
There are no fish in William Gibson.<br />
&gt; <br />
<br />
Literal text is the simplest regular expression of all to look for, but we needn't look for just the one word - we could look for any particular phrase. However, we need to make sure that we exactly match all the characters: words (with correct capitalization), numbers, punctuation, and even whitespace:<br />
<br />
#!/usr/bin/perl<br />
# match2.plx<br />
use warnings;<br />
use strict;<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (/I do/) {<br />
print "'I do' is in that string.\n";<br />
}<br />
if (/sometimes Case/) {<br />
print "'sometimes Case' matched.\n";<br />
} <br />
<br />
Let's run this program and see what happens:<br />
<br />
&gt;perl match2.plx<br />
'I do' is in that string.<br />
&gt;<br />
<br />
The other string didn't match, even though those two words are there. This is because everything in a regular expression has to match the string, from start to finish: first "sometimes", then a space, then "Case". In &#36;_ , there was a comma before the space, so it didn't match exactly. Similarly, spaces inside the pattern are significant:<br />
<br />
#!/usr/bin/perl<br />
# match3.plx<br />
use warnings;<br />
use strict;<br />
my &#36;test1 = "The dog is in the kennel";<br />
my &#36;test2 = "The sheepdog is in the field";<br />
if (&#36;test1 =~ / dog/) {<br />
print "This dog's at home.\n";<br />
} <br />
if (&#36;test2 =~ / dog/) {<br />
print "This dog's at work.\n";<br />
} <br />
<br />
This will only find the first dog, as perl was looking for a space followed by the three letters, 'dog':<br />
<br />
&gt;perl match3.plx<br />
This dog's at home.<br />
&gt;<br />
<br />
So, for the moment, it looks like we shall have to specify our patterns with absolute precision. As another example, look at this:<br />
<br />
#!/usr/bin/perl<br />
# match4.plx<br />
use warnings;<br />
use strict; <br />
<br />
&#36;_ = "Nobody wants to hurt you... 'cept, <br />
I do hurt people sometimes, Case.";<br />
if (/case/) {<br />
print "I guess it's just the way I'm made.\n";<br />
} else {<br />
print "Case? Where are you, Case?\n";<br />
} <br />
<br />
&gt; perl match4.plx<br />
Case? Where are you, Case?<br />
&gt; <br />
<br />
Hmm, no match. Why not? Because we asked for a small 'c' when we had a big 'C' - regexps are (if you'll pardon the pun) case-sensitive. We can get around this by asking perl to compare insensitively, and we do this by putting an 'i' (for 'insensitive') after the closing slash. If we alter the code above as follows:<br />
<br />
if (/case/i) { <br />
print "I guess it's just the way I'm made.\n";} else {<br />
print "Case? Where are you, Case?\n";} <br />
<br />
then we find him:<br />
<br />
&gt;perl match4.plx<br />
I guess it's just the way I'm made.<br />
&gt;<br />
<br />
This 'i ' is one of several modifiers that we can add to the end of the regular expression to change its behavior slightly. We'll see more of them later on.<br />
<br />
Continued... &lt;-vs_break&gt; Interpolation<br />
<br />
Regular expressions work a little like double-quoted strings; variables and metacharacters are interpolated. This allows us to store patterns in variables and determine what we are matching when we run the program - we don't need to have them hard-coded in:<br />
<br />
Try it out - Pattern Tester<br />
<br />
This program will ask the user for a pattern and then test to see if it matches our string. We can use this throughout the chapter to help us test the various different styles of pattern we'll be looking at:<br />
<br />
#!/usr/bin/perl<br />
# matchtest.plx<br />
use warnings;<br />
use strict;<br />
&#36;_ = q("I wonder what the Entish is for 'yes' and 'no'," he thought.);<br />
# Tolkien, Lord of the Rings<br />
print "Enter some text to find: ";<br />
my &#36;pattern = ;<br />
chomp(&#36;pattern); <br />
<br />
if (/&#36;pattern/) {<br />
print "The text matches the pattern '&#36;pattern'.\n";<br />
} else {<br />
print "'&#36;pattern' was not found.\n";<br />
} <br />
<br />
Now we can test out a few things:<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: wonder<br />
The text matches the pattern 'wonder'.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: entish<br />
'entish' was not found.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: hough<br />
The text matches the pattern 'hough'.<br />
<br />
&gt; perl matchtest.plx<br />
Enter some text to find: and 'no',<br />
The text matches the pattern 'and 'no''.<br />
<br />
Pretty straightforward, and I'm sure you could all spot those not in &#36;_ as well.<br />
<br />
How It Works<br />
<br />
matchtest.plx has its basis in the three lines:<br />
<br />
my &#36;pattern = ;chomp(&#36;pattern);<br />
if (/&#36;pattern/) { <br />
<br />
We're taking a line of text from the user. Then, since it will end in a new line, and we don't necessarily want to find a new line in our pattern, we chomp it away. Now we do our test.<br />
<br />
Since we're not using the =~ operator, the test will be looking at the variable &#36;_ . The regular expression is /&#36;pattern/ , and just like the double-quoted string "&#36;pattern" , the variable &#36;pattern is interpolated. Hence, the regular expression is purely and simply whatever the user typed in, once we've got rid of the new line.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Making a Wizards mind bomb]]></title>
			<link>http://hexalist.com/forums/thread-23.html</link>
			<pubDate>Tue, 12 May 2009 18:03:01 +0200</pubDate>
			<guid isPermaLink="false">http://hexalist.com/forums/thread-23.html</guid>
			<description><![CDATA[What you'll need:<br />
Two glasses or other suitable container for liquid<br />
One coffee filter<br />
A polar solvent. See notes.<br />
Fifteen grams of wormwood (powdered)<br />
Ten grams of morning glory seeds (powdered) or a few ounces of morning glory foliage (powdered). See notes.<br />
Five grams of calamus (powdered) or the equivalent in calamus oil<br />
Ten grams of scullcap (powdered)<br />
300 milligrams of diphenhydramine (in crushed pill form; syrup may not be entirely miscible in water.) See notes, lest you find your brain exploding.<br />
<br />
To make:<br />
Place the wormwood, morning glory seeds/plant material, calamus, scullcap, and diphenhydramine into the first glass. Add your polar solvent and stir for at least thirty minutes. Filter the mixture through your coffee filter into the second glass and remove all solids that slip through the filter. If you wish to make a solid out of the solution or if your solvent was poisonous (such as methanol and isopropyl alcohol), allow the solution to evaporate completely. Whether you made a solid or still have the liquid (if so, see notes), consume it and enjoy the effects of your brain being shot with a repeater rifle.<br />
<br />
A few notes:<br />
On all psychoactive ingredients: you can find all but the diphenhydramine at <a href="http://shamanhut.com" target="_blank">http://shamanhut.com</a>. Diphenhydramine can be found in Benadryl. Dimenhydrinate (Dramamine) is similar to diphenhydramine and you may use it, but it requires double the dose for the same effect.<br />
On polar solvents: keep in mind if you want to make an extract of the solution, you'll want the solvent to be volatile. Some volatile solvents are: ethanol (the alcohol your parents drink, dearie), methanol, isopropyl alcohol (rubbing alcohol). Water is not volatile, but good if you're drinking the mixture.<br />
On morning glories: you may want to do a rough extraction on the powdered seeds/plant material beforehand. See erowid.org's section on this.<br />
On diphenhydramine: it's a total deliriant. The best description of a diphenhydramine is to compare it to a dream. And no, you won't know the hallucinations are just the effects of drugs. You may forget you took anything in the first place. It's good stuff if used properly. Do not do when in a bad mood. Doing so is basically asking for a terrible trip.<br />
On drinking the solution: wormwood is fucking bitter. You can't drink it raw unless your tastebuds are all dead and gone. Add a generous amount of sugar and it'll become a very tasty drink.<br />
<br />
I've done my part now to get kids on drugs. Thank you, my dearies. Do describe your experiences from it if you try it, because it's fucking weird. Here's a picture of the final product, and yes, I know it's huge.<br />
<br />
<img src="http://img85.imageshack.us/img85/282/pict0286hy9.jpg" border="0" alt="[Image: pict0286hy9.jpg&#93;" />]]></description>
			<content:encoded><![CDATA[What you'll need:<br />
Two glasses or other suitable container for liquid<br />
One coffee filter<br />
A polar solvent. See notes.<br />
Fifteen grams of wormwood (powdered)<br />
Ten grams of morning glory seeds (powdered) or a few ounces of morning glory foliage (powdered). See notes.<br />
Five grams of calamus (powdered) or the equivalent in calamus oil<br />
Ten grams of scullcap (powdered)<br />
300 milligrams of diphenhydramine (in crushed pill form; syrup may not be entirely miscible in water.) See notes, lest you find your brain exploding.<br />
<br />
To make:<br />
Place the wormwood, morning glory seeds/plant material, calamus, scullcap, and diphenhydramine into the first glass. Add your polar solvent and stir for at least thirty minutes. Filter the mixture through your coffee filter into the second glass and remove all solids that slip through the filter. If you wish to make a solid out of the solution or if your solvent was poisonous (such as methanol and isopropyl alcohol), allow the solution to evaporate completely. Whether you made a solid or still have the liquid (if so, see notes), consume it and enjoy the effects of your brain being shot with a repeater rifle.<br />
<br />
A few notes:<br />
On all psychoactive ingredients: you can find all but the diphenhydramine at <a href="http://shamanhut.com" target="_blank">http://shamanhut.com</a>. Diphenhydramine can be found in Benadryl. Dimenhydrinate (Dramamine) is similar to diphenhydramine and you may use it, but it requires double the dose for the same effect.<br />
On polar solvents: keep in mind if you want to make an extract of the solution, you'll want the solvent to be volatile. Some volatile solvents are: ethanol (the alcohol your parents drink, dearie), methanol, isopropyl alcohol (rubbing alcohol). Water is not volatile, but good if you're drinking the mixture.<br />
On morning glories: you may want to do a rough extraction on the powdered seeds/plant material beforehand. See erowid.org's section on this.<br />
On diphenhydramine: it's a total deliriant. The best description of a diphenhydramine is to compare it to a dream. And no, you won't know the hallucinations are just the effects of drugs. You may forget you took anything in the first place. It's good stuff if used properly. Do not do when in a bad mood. Doing so is basically asking for a terrible trip.<br />
On drinking the solution: wormwood is fucking bitter. You can't drink it raw unless your tastebuds are all dead and gone. Add a generous amount of sugar and it'll become a very tasty drink.<br />
<br />
I've done my part now to get kids on drugs. Thank you, my dearies. Do describe your experiences from it if you try it, because it's fucking weird. Here's a picture of the final product, and yes, I know it's huge.<br />
<br />
<img src="http://img85.imageshack.us/img85/282/pict0286hy9.jpg" border="0" alt="[Image: pict0286hy9.jpg]" />]]></content:encoded>
		</item>
	</channel>
</rss>