<?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>killdash9.org &#187; Syntaxy</title>
	<atom:link href="http://www.killdash9.org/category/syntaxy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.killdash9.org</link>
	<description>babblings</description>
	<lastBuildDate>Thu, 03 Jun 2010 13:01:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Moving &#8220;My Documents&#8221; with an extra step.</title>
		<link>http://www.killdash9.org/2009/04/23/moving-my-documents-with-an-extra-step/</link>
		<comments>http://www.killdash9.org/2009/04/23/moving-my-documents-with-an-extra-step/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 18:38:57 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[windows junction symlink "My Documents"]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=210</guid>
		<description><![CDATA[There&#8217;s lots of documents on the web that show how to move &#8220;My Documents&#8221; to another drive, so I won&#8217;t bother show how here. One step I found missing however was brought on by my use of Linux. Whenever you move a directory to a bigger drive, I just symlink it so I don&#8217;t have [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s lots of documents on the web that show how to move &#8220;My Documents&#8221; to another drive, so I won&#8217;t bother show how here.  One step I found missing however was brought on by my use of Linux.  Whenever you move a directory to a bigger drive, I just symlink it so I don&#8217;t have to reconfigure anything that doesn&#8217;t follow along.  Granted, Windows management of &#8220;My Documents&#8221; is a little more internal than just a directory (or folder in this case), so most everything followed along.  Except for Google Desktop.  It actually created it&#8217;s own folder in &#8220;C:\Documents and Settings\<user>&#8221; (after I moved everything and deleted the original) and made use of that, so obviously, it uses a full path.  Windows doesn&#8217;t have a simple/proper symlinking unless you purchased some lame Resource Pack or something.  Someone was nice enough to write a tool to fix this, called Junction.  You can find it <a href="http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx" onclick="pageTracker._trackPageview('/outgoing/technet.microsoft.com/en-us/sysinternals/bb896768.aspx?referer=');">here.</a></user></p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2009/04/23/moving-my-documents-with-an-extra-step/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Router tinkering.</title>
		<link>http://www.killdash9.org/2009/01/09/router-tinkering/</link>
		<comments>http://www.killdash9.org/2009/01/09/router-tinkering/#comments</comments>
		<pubDate>Fri, 09 Jan 2009 15:51:41 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[Dlink DIR-655 gigabit router]]></category>
		<category><![CDATA[Dlink router]]></category>
		<category><![CDATA[gigabit router]]></category>
		<category><![CDATA[home network]]></category>
		<category><![CDATA[Rogers]]></category>
		<category><![CDATA[two routers]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=193</guid>
		<description><![CDATA[So for various reasons, I run two routers on my home network. One is the Rogers supplied SMC POS. I treat this basically as a modem and connect to it with my new Dlink DIR-655 gigabit router. I recently had a need to get some traffic routed to an internal machine and dreaded having to [...]]]></description>
			<content:encoded><![CDATA[<p>So for various reasons, I run two routers on my home network.  One is the Rogers supplied SMC POS.  I treat this basically as a modem and connect to it with my new Dlink DIR-655 gigabit router.  I recently had a need to get some traffic routed to an internal machine and dreaded having to figure it all out.  Looking at the SMC, I realized it had a DMZ option.  Setting that to the &#8220;external&#8221; IP of my Dlink router would in effect pass all traffic to my Dlink, letting it handle all security related issues, including routing of traffic to internal IPs.  Done and Done.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2009/01/09/router-tinkering/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Source</title>
		<link>http://www.killdash9.org/2005/09/28/source/</link>
		<comments>http://www.killdash9.org/2005/09/28/source/#comments</comments>
		<pubDate>Wed, 28 Sep 2005 16:01:30 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[jpeg]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Private]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[SSL]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=109</guid>
		<description><![CDATA[I like Open Source as much as the next geek, but I also like it when I&#8217;m shielded from the pain the way I am in Gentoo. Check this `configure` command out from a recent Solaris PHP compile: $ ./configure \ &#8211;with-gd=/usr/local \ &#8211;with-jpeg-dir=/usr/local \ &#8211;with-freetype-dir=/usr/local \ &#8211;with-png-dir=/usr/local \ &#8211;with-xpm-dir=/usr/local \ &#8211;with-iconv-dir=/usr/local \ &#8211;enable-freetype \ [...]]]></description>
			<content:encoded><![CDATA[<p>I like Open Source as much as the next geek, but I also like it when I&#8217;m shielded from the pain the way I am in Gentoo.  Check this `configure` command out from a recent Solaris PHP compile:</p>
<blockquote><p>
$ ./configure \<br />
&#8211;with-gd=/usr/local \<br />
&#8211;with-jpeg-dir=/usr/local \<br />
&#8211;with-freetype-dir=/usr/local \<br />
&#8211;with-png-dir=/usr/local \<br />
&#8211;with-xpm-dir=/usr/local \<br />
&#8211;with-iconv-dir=/usr/local \<br />
&#8211;enable-freetype \<br />
&#8211;enable-jpeg \<br />
&#8211;with-zip \<br />
&#8211;enable-memory-limit \<br />
&#8211;disable-debug \<br />
&#8211;with-regex=php \<br />
&#8211;with-pic \<br />
&#8211;enable-exif \<br />
&#8211;enable-filepro \<br />
&#8211;enable-ftp \<br />
&#8211;with-gettext \<br />
&#8211;enable-mbstring \<br />
&#8211;enable-sockets \<br />
&#8211;enable-sysvsem \<br />
&#8211;enable-sysvshm \<br />
&#8211;with-mysql=/opt/private/path/mysql \<br />
&#8211;with-apxs2=/opt/private/path/apache/bin/apxs \<br />
&#8211;with-zlib \<br />
&#8211;with-openssl=/usr/local/ssl \<br />
&#8211;enable-ftp  \<br />
&#8211;enable-shared \<br />
&#8211;enable-libgcc \<br />
&#8211;prefix=/opt/private/path/php</p></blockquote>
<p>Isn&#8217;t that just sick?  Sure, I would have had to use lots of USE flags in Gentoo to make that work, but it&#8217;s still a lot less typing/headaches, not to mention the fact that it would have gone out and compiled GD and everything else for me.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2005/09/28/source/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mozilla password migration.</title>
		<link>http://www.killdash9.org/2005/03/07/mozilla-password-migration/</link>
		<comments>http://www.killdash9.org/2005/03/07/mozilla-password-migration/#comments</comments>
		<pubDate>Mon, 07 Mar 2005 20:42:42 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[extra encryption]]></category>
		<category><![CDATA[Password Manager]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=85</guid>
		<description><![CDATA[I hate Mozilla sometimes. Something screwed up my profile to the point that the preferences windows wasn&#8217;t populated with data. &#8220;No problem,&#8221; I thought, &#8220;I&#8217;ll just make a new profile and get a fresh start.&#8221; Went well until I tried to migrate/import my passwords to the new profile. Long story short, here&#8217;s what you need [...]]]></description>
			<content:encoded><![CDATA[<p>I hate Mozilla sometimes.  Something screwed up my profile to the point that the preferences windows wasn&#8217;t populated with data.  &#8220;No problem,&#8221; I thought, &#8220;I&#8217;ll just make a new profile and get a fresh start.&#8221;  Went well until I tried to migrate/import my passwords to the new profile.  Long story short, here&#8217;s what you need to do:</p>
<li>Make a new profile and go to a page that will let you save a password in the Password Manager.</li>
<li>Find the < random number >.s file from your previous profile and copy it to your new one.</li>
<li>Close Mozilla and edit prefs.js and find the &#8220;signon.SignonFileName&#8221; entry.  Change the < random number >.s to be the file you just copied.</li>
<li>Start Mozilla and you should have all your passwords recovered.  If you don&#8217;t, chances are good you either didn&#8217;t do it right, or, like me, you had the extra encryption enabled.  That&#8217;s the &#8220;Use Encryption when storing sensitive data&#8221; option under Passwords in the Preferences.  If so, you&#8217;ll need to copy the key3.db and cert8.db files over from your old profile as well.</li>
<p>There&#8217;s  a very good chance you don&#8217;t need both of those .db files, but I simply don&#8217;t care.  I killed a good hour jerking around with this POS and I don&#8217;t care to look it up any further.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2005/03/07/mozilla-password-migration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partition multiple drives in Solaris</title>
		<link>http://www.killdash9.org/2004/12/10/partition-multiple-drives-in-solaris/</link>
		<comments>http://www.killdash9.org/2004/12/10/partition-multiple-drives-in-solaris/#comments</comments>
		<pubDate>Fri, 10 Dec 2004 18:32:22 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[Solaris]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=75</guid>
		<description><![CDATA[Say you have an ol E450 with a whack of drive in it (they fit 20). You want to put all those drives in a RAID5 or something and wish to have them all laid out the same way, partition wise. Here&#8217;s a shortcut. Format one of the drives the way you want it. Then [...]]]></description>
			<content:encoded><![CDATA[<p>Say you have an ol E450 with a whack of drive in it (they fit 20).  You want to put all those drives in a RAID5 or something and wish to have them all laid out the same way, partition wise.  Here&#8217;s a shortcut.  Format one of the drives the way you want it.  Then run the following:</p>
<p>prtvtoc /dev/rdsk/<source> | fmthard -s &#8211; /dev/rdsk/<destination></p>
<p>This will copy the partition table from the <source> drive (example c0t0d0s2) to the <destination> (example c0t2d0s2). Obviously you can script this to hit all the drives.</destination></source></destination></source></p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/12/10/partition-multiple-drives-in-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>df and du dont&#8217; match?</title>
		<link>http://www.killdash9.org/2004/12/03/df-and-du-dont-match/</link>
		<comments>http://www.killdash9.org/2004/12/03/df-and-du-dont-match/#comments</comments>
		<pubDate>Fri, 03 Dec 2004 14:30:18 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[large active server]]></category>
		<category><![CDATA[Solaris]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=73</guid>
		<description><![CDATA[If you have a large active server running (possibly applies to Solaris only here), and find your disk space seems to dissappear quickly, and running `df` and `du` bring back different results, try running the following: find /proc -type f -size +100000000c -ls This will look at running processes on the system and find each [...]]]></description>
			<content:encoded><![CDATA[<p>If you have a large active server running (possibly applies to Solaris only here), and find your disk space seems to dissappear quickly, and running `df` and `du` bring back different results, try running the following:</p>
<blockquote><p>find /proc -type f -size +100000000c -ls</p></blockquote>
<p>This will look at running processes on the system and find each one that has a file descriptor larger than 100M.  If you have quite a few (like I do), try chaning the &#8220;100000000&#8243; to &#8220;500000000&#8243;.  From there, investigate each process to see which is larger, and whether its handling its files properly.  Use `lsof` to see which files that PID has open, and if the files sizes match the file descriptor size of your above command.  If not, that process isn&#8217;t closing its files properly, and will need restarting (and subsequent complaints to the developers).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/12/03/df-and-du-dont-match/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Useful bash history</title>
		<link>http://www.killdash9.org/2004/10/06/useful-bash-history/</link>
		<comments>http://www.killdash9.org/2004/10/06/useful-bash-history/#comments</comments>
		<pubDate>Wed, 06 Oct 2004 14:47:56 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=59</guid>
		<description><![CDATA[Putting the following in your .bashrc (either in your home, or globally if its just a desktop), will increase the number of entries your bash history will show (when typing `history` or using C-r). The HISTCONTROL variable will cause your bash_history to ignore consecutive commands, so only one will display in your history. export HISTSIZE=1000 [...]]]></description>
			<content:encoded><![CDATA[<p>Putting the following in your .bashrc (either in your home, or globally if its just a desktop), will increase the number of entries your bash history will show (when typing `history` or using C-r).  The HISTCONTROL variable will cause your bash_history to ignore consecutive commands, so only one will display in your history.</p>
<p>export HISTSIZE=1000<br />
export HISTFILESIZE=1000<br />
export HISTCONTROL=ignoredups</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/10/06/useful-bash-history/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bash 3 and line wrapping.</title>
		<link>http://www.killdash9.org/2004/09/13/bash-3-and-line-wrapping/</link>
		<comments>http://www.killdash9.org/2004/09/13/bash-3-and-line-wrapping/#comments</comments>
		<pubDate>Mon, 13 Sep 2004 14:43:06 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[Gentoo]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=54</guid>
		<description><![CDATA[I had some trouble with my command line shortly after emerging Bash 3.0. My line was wrapping at very odd places and I couldn&#8217;t really figure out why. I originally had this for a prompt: export PS1="u@h: [$(/bin/ls -1 &#124; /usr/bin/wc -l &#124; /bin/sed 's: ::g') files - $(/bin/ls -lah &#124; /bin/grep -m 1 total [...]]]></description>
			<content:encoded><![CDATA[<p>I had some trouble with my command line shortly after emerging Bash 3.0.  My line was wrapping at very odd places and I couldn&#8217;t really figure out why.  I originally had this for a prompt:</p>
<p><code>export PS1="u@h: [$(/bin/ls -1 | /usr/bin/wc -l | /bin/sed 's: ::g') files - $(/bin/ls -lah | /bin/grep -m 1 total | /bin/sed 's/total //')] w n$ "<br />
</code></p>
<p>This will show the number of files in the current directory, as well as the size of the files.  This was neat, but useless so I took it out and ended up with this:</p>
<p><code>export PS1='u@h: w n$ '</code></p>
<p>Now, this was smaller, but it still messed up my line wrap.  In fact, it looked as though it was wrapping the line according the size of the prompt.  Some searching in the Gentoo forums revealed that Bash wasn&#8217;t counting the characters properly, thinking my prompt was part of my command line.  A post from someone who actually bothered to investigate further suggested you have to escape your entire prompt with []&#8216;s, but also escape those with &#8216;s.  So, my final prompt is this, which works wonderfully:</p>
<p><code>export PS1='[u@h: w n$] '</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/09/13/bash-3-and-line-wrapping/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>du handiness.</title>
		<link>http://www.killdash9.org/2004/08/30/du-handiness/</link>
		<comments>http://www.killdash9.org/2004/08/30/du-handiness/#comments</comments>
		<pubDate>Mon, 30 Aug 2004 20:24:36 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=48</guid>
		<description><![CDATA[I use &#8216;du&#8217; often to see what directories are using up all the space. Often, this gets annoying as it delves down in to several thousand directory trees, so I use the following to keep it limited: du -h &#8211;max-depth=1 This will spit out, in human readable format, the size of each of the directories [...]]]></description>
			<content:encoded><![CDATA[<p>I use &#8216;du&#8217; often to see what directories are using up all the space.  Often, this gets annoying as it delves down in to several thousand directory trees, so I use the following to keep it limited:</p>
<p>du -h &#8211;max-depth=1</p>
<p>This will spit out, in human readable format, the size of each of the directories in the current directory, limiting the output to one directory.  Try it to see what I mean.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/08/30/du-handiness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Backup config</title>
		<link>http://www.killdash9.org/2004/06/25/backup-config/</link>
		<comments>http://www.killdash9.org/2004/06/25/backup-config/#comments</comments>
		<pubDate>Fri, 25 Jun 2004 16:50:53 +0000</pubDate>
		<dc:creator>Ren West</dc:creator>
				<category><![CDATA[Syntaxy]]></category>
		<category><![CDATA[USD]]></category>
		<guid isPermaLink="false">http://www.killdash9.org/?p=33</guid>
		<description><![CDATA[Now that I&#8217;m hosting other peoples data, I decided perhaps I should try and create some better backups of things. This script can be called to backup any directory you want, and will store the backups on a local filesystem. I did it this way because I have 2 drives in my server, but it [...]]]></description>
			<content:encoded><![CDATA[<p>Now that I&#8217;m hosting other peoples data, I decided perhaps I should try and create some better backups of things.  This script can be called to backup any directory you want, and will store the backups on a local filesystem.  I did it this way because I have 2 drives in my server, but it could be modified easily to send data to a remote host via ssh, or just use an NFS mount.</p>
<p>
I got a lot of help from <a href="http://www.mikerubel.org/computers/rsync_snapshots/" onclick="pageTracker._trackPageview('/outgoing/www.mikerubel.org/computers/rsync_snapshots/?referer=');">this</a> page, which explains some of what I&#8217;ve done below.  Feel free to use this and modify it to suit your needs.  I assume no responsibility if it doesn&#8217;t work for you.</p>
<blockquote><p>#!/bin/bash</p>
<p># &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
# Creating rsync backups, then making daily copies of those backups<br />
# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
unset PATH</p>
<p>ID=/bin/id;<br />
CP=/bin/cp;<br />
MV=/bin/mv;<br />
RM=/bin/rm;<br />
RSYNC=/usr/bin/rsync;<br />
BZIP=/bin/bzip2;<br />
TAR=/bin/tar;</p>
<p>if [ ! $2 ] ; then<br />
        echo &#8220;Usage: `/bin/basename $0` SOURCE NAME_SET&#8221;<br />
        exit 1<br />
fi      </p>
<p>SOURCE=$1<br />
NAME=$2<br />
DEST=/root/temp/</p>
<p># make sure we&#8217;re running as root<br />
if (( `$ID -u` != 0 )); then { $ECHO &#8220;Sorry, must be root.  Exiting&#8230;&#8221;; exit; } fi</p>
<p># Step 1, rotate older backups, deleting the 6th backup, as its too old to care about<br />
if [ -e ${DEST}/${NAME}.6.tar.bz2 ] ; then<br />
        $RM ${DEST}/${NAME}.6.tar.bz2<br />
fi</p>
<p>if [ -e ${DEST}/${NAME}.5.tar.bz2 ] ; then<br />
        $MV ${DEST}/${NAME}.5.tar.bz2 ${DEST}/${NAME}.6.tar.bz2<br />
fi</p>
<p>if [ -e ${DEST}/${NAME}.4.tar.bz2 ] ; then<br />
         $MV ${DEST}/${NAME}.4.tar.bz2 ${DEST}/${NAME}.5.tar.bz2<br />
fi</p>
<p>if [ -e ${DEST}/${NAME}.3.tar.bz2 ] ; then<br />
         $MV ${DEST}/${NAME}.3.tar.bz2 ${DEST}/${NAME}.4.tar.bz2<br />
fi</p>
<p>if [ -e ${DEST}/${NAME}.2.tar.bz2 ] ; then<br />
         $MV ${DEST}/${NAME}.2.tar.bz2 ${DEST}/${NAME}.3.tar.bz2<br />
fi</p>
<p>if [ -e ${DEST}/${NAME}.1.tar.bz2 ] ; then<br />
         $MV ${DEST}/${NAME}.1.tar.bz2 ${DEST}/${NAME}.2.tar.bz2<br />
fi</p>
<p># This one is different.  To save a little stress on the system being backed up,<br />
# make a copy (cp -a) of the last ${NAME}, instead of moving it.  This will allow<br />
# rsync to only write the changes in the filesystem, rather than everything.<br />
# Also, bzip2 the previous ${NAME} to save drive space.<br />
if [ -d ${DEST}/${NAME}.0/ ] ; then<br />
        $CP -a ${DEST}/${NAME}.0/ ${DEST}/${NAME}.1/<br />
        if ( `$TAR cjf ${DEST}/${NAME}.1.tar.bz2 ${DEST}/${NAME}.1/` ); then { $RM -r ${DEST}/${NAME}.1/; } fi<br />
fi</p>
<p># Step 2, make a new backup, and call it ${NAME}.0/</p>
<p>$RSYNC &#8211;delete -avz ${SOURCE} ${DEST}/${NAME}.0/
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.killdash9.org/2004/06/25/backup-config/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
