<?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>TECH.kulish.com &#187; Linux</title>
	<atom:link href="http://tech.kulish.com/category/os/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.kulish.com</link>
	<description>Technology Junk Drawer</description>
	<lastBuildDate>Thu, 26 Aug 2010 20:36:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>MariaDB</title>
		<link>http://tech.kulish.com/2010/08/25/183/</link>
		<comments>http://tech.kulish.com/2010/08/25/183/#comments</comments>
		<pubDate>Thu, 26 Aug 2010 00:22:46 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MariaDB]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://tech.kulish.com/?p=183</guid>
		<description><![CDATA[We have upgraded the websites and email servers from MySQL to MariaDB. Currently researching changes in tuning, if any.]]></description>
			<content:encoded><![CDATA[<p>We have upgraded the websites and email servers from MySQL to MariaDB.</p>
<p>Currently researching changes in tuning, if any.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2010/08/25/183/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jolicloud Download Plop</title>
		<link>http://tech.kulish.com/2010/08/04/jolicloud-download-plop/</link>
		<comments>http://tech.kulish.com/2010/08/04/jolicloud-download-plop/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 02:20:33 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>

		<guid isPermaLink="false">http://tech.kulish.com/?p=180</guid>
		<description><![CDATA[I was going to try Jolicloud on my netbook but the only way to download it is via bittorrent. Which is ok, if it&#8217;s seeded correctly, but I&#8217;ll be damned if I am going sit around waiting for a 700MB download at 8k a second when I&#8217;m sitting on a 7Mb connect. I&#8217;d love to [...]]]></description>
			<content:encoded><![CDATA[<p>I was going to try Jolicloud on my netbook but the only way to download it is via bittorrent.</p>
<p>Which is ok, if it&#8217;s seeded correctly, but I&#8217;ll be damned if I am going sit around waiting for a 700MB download at 8k a second when I&#8217;m sitting on a 7Mb connect.</p>
<p>I&#8217;d love to try it, but screw that.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2010/08/04/jolicloud-download-plop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>6/08 Outage</title>
		<link>http://tech.kulish.com/2010/06/08/608-outage/</link>
		<comments>http://tech.kulish.com/2010/06/08/608-outage/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 16:02:47 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Drupal]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[restore]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=33</guid>
		<description><![CDATA[Apparently we had a power failure today that my UPS wasn&#8217;t quick enough to take over for. Everything is back up and running. One database was corrupted but we were able restore it from this morning&#8217;s backup. Backups will be more frequent during storm season.]]></description>
			<content:encoded><![CDATA[<p>Apparently we had a power failure today that my UPS wasn&#8217;t quick enough to take over for.</p>
<p>Everything is back up and running.</p>
<p>One database was corrupted but we were able restore it from this morning&#8217;s backup.<br />
Backups will be more frequent during storm season.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2010/06/08/608-outage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reduce / LV (ex. /dev/VolGroup00/LogVol00)</title>
		<link>http://tech.kulish.com/2010/05/28/reduce-lv-ex-devvolgroup00logvol00/</link>
		<comments>http://tech.kulish.com/2010/05/28/reduce-lv-ex-devvolgroup00logvol00/#comments</comments>
		<pubDate>Fri, 28 May 2010 06:39:42 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[linux lvm]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=36</guid>
		<description><![CDATA[1. Boot to systemrescue cd 2. vgscan 3. vgdisplay 4. vgchange -ay VolGroup00 5. e2fsck -f /dev/VolGroup00/LogVol00 6. resize2fs /dev/VolGroup00/LogVol00 xxG Note: &#8220;xxG&#8221; is the size in Gigabyte the FS is being reduced to. 7. Repeat step #5 8. lvreduce -LxxG /dev/VolGroup00/LogVol00 Note: &#8220;-LxxG&#8221; is the same value as xxG in step #6 in this [...]]]></description>
			<content:encoded><![CDATA[<p>1. Boot to systemrescue cd<br />
2. vgscan<br />
3. vgdisplay<br />
4. vgchange -ay VolGroup00<br />
5. e2fsck -f /dev/VolGroup00/LogVol00<br />
6. resize2fs /dev/VolGroup00/LogVol00 xxG<br />
Note: &#8220;xxG&#8221; is the size in Gigabyte the FS is being reduced to.</p>
<p>7. Repeat step #5<br />
8. lvreduce -LxxG /dev/VolGroup00/LogVol00<br />
Note: &#8220;-LxxG&#8221; is the same value as xxG in step #6 in this case.</p>
<p>9. Repeat step #5<br />
10. Remove CD and reboot<br />
11. vgdisplay -v | less<br />
12. vgs<br />
13. lvs<br />
14. Create new LV&#8217;s to re-use space</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2010/05/28/reduce-lv-ex-devvolgroup00logvol00/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Drupal Issue</title>
		<link>http://tech.kulish.com/2009/12/25/drupal-issue/</link>
		<comments>http://tech.kulish.com/2009/12/25/drupal-issue/#comments</comments>
		<pubDate>Fri, 25 Dec 2009 11:59:56 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Daemons]]></category>
		<category><![CDATA[Databases]]></category>
		<category><![CDATA[Drupal]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[php]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=42</guid>
		<description><![CDATA[We are currently experiencing an issue with editing account information. The problem is being researched and status will be provided when information is available. The following sites are affected: http://tech.kulish.com http://family.kulish.com http://www.iowajeep.net http://www.racebus.org]]></description>
			<content:encoded><![CDATA[<p>We are currently experiencing an issue with editing account information.<br />
The problem is being researched and status will be provided when information is available.</p>
<p>The following sites are affected:</p>
<p>http://tech.kulish.com<br />
http://family.kulish.com<br />
http://www.iowajeep.net<br />

http://www.racebus.org</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/12/25/drupal-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>D4rk Theme Issues</title>
		<link>http://tech.kulish.com/2009/11/02/d4rk-theme-issues/</link>
		<comments>http://tech.kulish.com/2009/11/02/d4rk-theme-issues/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 10:31:58 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Drupal]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[theme]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=44</guid>
		<description><![CDATA[New Drupal theme issues: (FIXED)1. Text &#8211; Links Too dark. The gray is a couple shades too dark for it&#8217;s background color. (FIXED)2. Text &#8211; Black text, in text entry areas, is too dark. (search box) (FIXED)3. Spacing &#8211; Spacing on articles and blocks. There needs to be a CR between the controls of an [...]]]></description>
			<content:encoded><![CDATA[<p>New Drupal theme issues:</p>
<p>(FIXED)1. Text &#8211; Links Too dark.  The gray is a couple shades too dark for it&#8217;s background color.</p>
<p>(FIXED)2. Text &#8211; Black text, in text entry areas, is too dark. (search box)</p>
<p>(FIXED)3. Spacing &#8211; Spacing on articles and blocks.<br />
    There needs to be a CR between the controls of an article teaser and the title of the next.<br />
    In blocks, there needs to be a CR at the end.</p>
<p>(MOSTLY)4. Preview &#8211; white text on white background.  Mostly fixed.  You can now see the body but some fields, like author, still have some white text on white background.  Comment preview works fine however.</p>
<p>(FIXED)5. Bottom AdSense block not showing properly. (Apparently main page only)</p>
<p>(FIXED)6. Pager black text too dark.</p>
<p><a href="http://www.cialug.org">CIALUG</a>, the local linux users group, suggested using firebug to find these issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/11/02/d4rk-theme-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building a MySQL Capable Postfix RPM</title>
		<link>http://tech.kulish.com/2009/10/18/building-a-mysql-capable-postfix-rpm/</link>
		<comments>http://tech.kulish.com/2009/10/18/building-a-mysql-capable-postfix-rpm/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 15:19:59 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Daemons]]></category>
		<category><![CDATA[Databases]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[smtp]]></category>
		<category><![CDATA[dovecot]]></category>
		<category><![CDATA[postfix]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=45</guid>
		<description><![CDATA[Build Environment: CentOS 5 x86_64 Postfix 2.3.3 Sources gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux # Get the src 1) wget http://mirror.centos.org/centos/5.3/centosplus/SRPMS/postfix-2.3.3-2.1.centos.mysql_pgsql.src.rpm # Install the src RPM 2) rpm -i postfix-2.3.3-2.1.centos.mysql_pgsql.src.rpm # Install some dependencies I didn&#8217;t have 3.1) yum install pcre-devel [...]]]></description>
			<content:encoded><![CDATA[<p>Build Environment:<br />
CentOS 5 x86_64<br />
Postfix 2.3.3 Sources<br />
gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)</p>
<p>2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux</p>
<p># Get the src<br />
1) wget http://mirror.centos.org/centos/5.3/centosplus/SRPMS/postfix-2.3.3-2.1.centos.mysql_pgsql.src.rpm</p>
<p># Install the src RPM<br />
2) rpm -i postfix-2.3.3-2.1.centos.mysql_pgsql.src.rpm</p>
<p># Install some dependencies I didn&#8217;t have<br />
3.1) yum install pcre-devel<br />
3.2) yum install rpm-build<br />
3.3) yum install mysql-devel.x86_64 openldap-devel.x86_64 db4-devel.x86_64<br />
3.4) yum install gcc.x86_64</p>
<p># Edit SPECS; remove postgres support<br />
4.1) cd /usr/src/redhat/SPECS<br />
4.2) vi postfix.spec and change &#8220;%%define PGSQL 1&#8243; to &#8220;%define PGSQL 0&#8243;<br />
     # I didn&#8217;t want Postgres support<br />
4.3) &#8220;%define MYSQL 1&#8243; was already defined for me</p>
<p># Build the new rpm<br />
5) rpmbuild -ba postfix.spec # Ignore warnings</p>
<p># Install the new rpm<br />
6.1) cd /usr/src/redhat/RPMS<br />
6.2) rpm -i postfix-2.3.3-2.1.centos.mysql_pgsql.x86_64.rpm</p>
<p>Building an RPM build environment: <a href="http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment">CentOS Wiki</a></p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/10/18/building-a-mysql-capable-postfix-rpm/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>50+ Hard Drives</title>
		<link>http://tech.kulish.com/2009/10/14/50-hard-drives/</link>
		<comments>http://tech.kulish.com/2009/10/14/50-hard-drives/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 19:52:09 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=55</guid>
		<description><![CDATA[I&#8217;ve used more than 50 hard drives in my home IT projects over the years and I&#8217;ve never had one start to fail. Keep in mind, these are commodity, off-the-shelf, drives. Meant for laptops, not the continual usage they see here. Don&#8217;t get me wrong, I&#8217;ve had them get loud. Loud to the point I [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve used more than 50 hard drives in my home IT projects over the years and I&#8217;ve never had one start to fail.  Keep in mind, these are commodity, off-the-shelf, drives.  Meant for laptops, not the continual usage they see here.</p>
<p>Don&#8217;t get me wrong, I&#8217;ve had them get loud.  Loud to the point I have replaced them to maintain sanity but I&#8217;ve never had one report bad sectors&#8230;  Until now.</p>
<p>I guess I&#8217;ve been lucky.</p>
<p>I&#8217;ve been having some reliability issues with my firewall and I think I&#8217;ve finally traced it down to the hard drive heading south for the winter.</p>
<p>It&#8217;s been a rock solid drive.  I really like the Barracudas from Seagate.  Enough that I will replace this one with another I have sitting in storage.</p>
<p>1111 days + 22 hours run-time is nothing to sneeze at for a PATA drive.</p>
<p>S.M.A.R.T. log:</p>
<p>Drive 0 (/dev/hda):<br />
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen<br />
Home page is http://smartmontools.sourceforge.net/</p>
<p>=== START OF INFORMATION SECTION ===<br />
Model Family:     Seagate Barracuda 7200.7 and 7200.7 Plus family<br />
Device Model:     ST3120022A<br />
Serial Number:    3JS31735<br />
Firmware Version: 3.54<br />
User Capacity:    120,034,123,776 bytes<br />
Device is:        In smartctl database [for details use: -P show]<br />
ATA Version is:   6<br />
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 2<br />
Local Time is:    Wed Oct 14 15:01:01 2009 CDT<br />
SMART support is: Available &#8211; device has SMART capability.<br />
SMART support is: Enabled</p>
<p>=== START OF READ SMART DATA SECTION ===<br />
SMART overall-health self-assessment test result: PASSED</p>
<p>General SMART Values:<br />
Offline data collection status:  (0&#215;82)	Offline data collection activity<br />
					was completed without error.<br />
					Auto Offline Data Collection: Enabled.<br />
Self-test execution status:      (   0)	The previous self-test routine completed<br />
					without error or no self-test has ever<br />
					been run.<br />
Total time to complete Offline<br />
data collection: 		 ( 430) seconds.<br />
Offline data collection<br />
capabilities: 			 (0x5b) SMART execute Offline immediate.<br />
					Auto Offline data collection on/off support.<br />
					Suspend Offline collection upon new<br />
					command.<br />
					Offline surface scan supported.<br />
					Self-test supported.<br />
					No Conveyance Self-test supported.<br />
					Selective Self-test supported.<br />
SMART capabilities:            (0&#215;0003)	Saves SMART data before entering<br />
					power-saving mode.<br />
					Supports SMART auto save timer.<br />
Error logging capability:        (0&#215;01)	Error logging supported.<br />
					No General Purpose Logging support.<br />
Short self-test routine<br />
recommended polling time: 	 (   1) minutes.<br />
Extended self-test routine<br />
recommended polling time: 	 (  85) minutes.</p>
<p>SMART Attributes Data Structure revision number: 10<br />
Vendor Specific SMART Attributes with Thresholds:<br />
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE<br />
  1 Raw_Read_Error_Rate     0x000f   057   054   006    Pre-fail  Always       &#8211;       110843279<br />
  3 Spin_Up_Time            0&#215;0003   097   095   000    Pre-fail  Always       &#8211;       0<br />
  4 Start_Stop_Count        0&#215;0032   100   100   020    Old_age   Always       &#8211;       56<br />
  5 Reallocated_Sector_Ct   0&#215;0033   100   100   036    Pre-fail  Always       &#8211;       0<br />
  7 Seek_Error_Rate         0x000f   087   060   030    Pre-fail  Always       &#8211;       628105282<br />
  9 Power_On_Hours          0&#215;0032   070   070   000    Old_age   Always       &#8211;       26687<br />
 10 Spin_Retry_Count        0&#215;0013   100   100   097    Pre-fail  Always       &#8211;       0<br />
 12 Power_Cycle_Count       0&#215;0032   100   100   020    Old_age   Always       &#8211;       957<br />
194 Temperature_Celsius     0&#215;0022   032   057   000    Old_age   Always       &#8211;       32<br />
195 Hardware_ECC_Recovered  0x001a   057   054   000    Old_age   Always       &#8211;       110843279<br />
197 Current_Pending_Sector  0&#215;0012   100   100   000    Old_age   Always       &#8211;       0<br />
198 Offline_Uncorrectable   0&#215;0010   100   100   000    Old_age   Offline      &#8211;       0<br />
199 UDMA_CRC_Error_Count    0x003e   200   190   000    Old_age   Always       &#8211;       27<br />
200 Multi_Zone_Error_Rate   0&#215;0000   100   253   000    Old_age   Offline      &#8211;       0<br />
202 TA_Increase_Count       0&#215;0032   100   253   000    Old_age   Always       &#8211;       0</p>
<p>SMART Error Log Version: 1<br />
ATA Error Count: 27 (device log contains only the most recent five errors)<br />
	CR = Command Register [HEX]<br />
	FR = Features Register [HEX]<br />
	SC = Sector Count Register [HEX]<br />
	SN = Sector Number Register [HEX]<br />
	CL = Cylinder Low Register [HEX]<br />
	CH = Cylinder High Register [HEX]<br />
	DH = Device/Head Register [HEX]<br />
	DC = Device Command Register [HEX]<br />
	ER = Error register [HEX]<br />
	ST = Status register [HEX]<br />
Powered_Up_Time is measured from power on, and printed as<br />
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,<br />
SS=sec, and sss=millisec. It &#8220;wraps&#8221; after 49.710 days.</p>
<p>Error 27 occurred at disk power-on lifetime: 26686 hours (1111 days + 22 hours)<br />
  When the command that caused the error occurred, the device was active or idle.</p>
<p>  After command completion occurred, registers were:<br />
  ER ST SC SN CL CH DH<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8211;<br />
  84 51 01 ee e9 7e e0  Error: ICRC, ABRT 1 sectors at LBA = 0x007ee9ee = 8317422</p>
<p>  Commands leading to the command that caused the error were:<br />
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8212; &#8211;  &#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
  25 00 04 eb e9 7e e0 00      00:05:31.146  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:05:31.143  READ DMA EXT<br />
  10 00 3f 00 00 00 e0 00      00:05:33.211  RECALIBRATE [OBS-4]<br />
  25 00 04 eb e9 7e e0 00      00:05:32.544  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:05:32.544  READ DMA EXT</p>
<p>Error 26 occurred at disk power-on lifetime: 26686 hours (1111 days + 22 hours)<br />
  When the command that caused the error occurred, the device was active or idle.</p>
<p>  After command completion occurred, registers were:<br />
  ER ST SC SN CL CH DH<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8211;<br />
  84 51 01 ee e9 7e e0  Error: ICRC, ABRT 1 sectors at LBA = 0x007ee9ee = 8317422</p>
<p>  Commands leading to the command that caused the error were:<br />
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8212; &#8211;  &#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
  25 00 04 eb e9 7e e0 00      00:05:31.146  READ DMA EXT<br />
  10 00 3f 00 00 00 e0 00      00:05:31.143  RECALIBRATE [OBS-4]<br />
  25 00 04 eb e9 7e e0 00      00:05:31.142  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:05:32.544  READ DMA EXT<br />
  25 00 02 91 98 7e e0 00      00:05:32.544  READ DMA EXT</p>
<p>Error 25 occurred at disk power-on lifetime: 26686 hours (1111 days + 22 hours)<br />
  When the command that caused the error occurred, the device was active or idle.</p>
<p>  After command completion occurred, registers were:<br />
  ER ST SC SN CL CH DH<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8211;<br />
  84 51 01 ee e9 7e e0  Error: ICRC, ABRT 1 sectors at LBA = 0x007ee9ee = 8317422</p>
<p>  Commands leading to the command that caused the error were:<br />
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8212; &#8211;  &#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
  25 00 04 eb e9 7e e0 00      00:05:31.146  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:05:31.143  READ DMA EXT<br />
  25 00 02 91 98 7e e0 00      00:05:31.142  READ DMA EXT<br />
  25 00 04 e7 e9 7e e0 00      00:05:31.142  READ DMA EXT<br />
  25 00 08 37 d1 7e e0 00      00:05:31.141  READ DMA EXT</p>
<p>Error 24 occurred at disk power-on lifetime: 26686 hours (1111 days + 22 hours)<br />
  When the command that caused the error occurred, the device was active or idle.</p>
<p>  After command completion occurred, registers were:<br />
  ER ST SC SN CL CH DH<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8211;<br />
  84 51 01 ee e9 7e e0  Error: ICRC, ABRT 1 sectors at LBA = 0x007ee9ee = 8317422</p>
<p>  Commands leading to the command that caused the error were:<br />
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8212; &#8211;  &#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
  25 00 04 eb e9 7e e0 00      00:05:31.146  READ DMA EXT<br />
  25 00 02 91 98 7e e0 00      00:05:31.143  READ DMA EXT<br />
  25 00 04 e7 e9 7e e0 00      00:05:31.142  READ DMA EXT<br />
  25 00 08 37 d1 7e e0 00      00:05:31.142  READ DMA EXT<br />
  25 00 c0 43 d1 7e e0 00      00:05:31.141  READ DMA EXT</p>
<p>Error 23 occurred at disk power-on lifetime: 26686 hours (1111 days + 22 hours)<br />
  When the command that caused the error occurred, the device was active or idle.</p>
<p>  After command completion occurred, registers were:<br />
  ER ST SC SN CL CH DH<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8211;<br />
  84 51 01 ee e9 7e e0  Error: ICRC, ABRT 1 sectors at LBA = 0x007ee9ee = 8317422</p>
<p>  Commands leading to the command that caused the error were:<br />
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name<br />
  &#8212; &#8211; &#8212; &#8211; &#8212; &#8211; &#8212; &#8211;  &#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
  25 00 04 eb e9 7e e0 00      00:01:47.681  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:01:47.025  READ DMA EXT<br />
  10 00 3f 00 00 00 e0 00      00:01:47.025  RECALIBRATE [OBS-4]<br />
  25 00 04 eb e9 7e e0 00      00:01:46.342  READ DMA EXT<br />
  25 00 04 eb e9 7e e0 00      00:01:45.689  READ DMA EXT</p>
<p>SMART Self-test log structure revision number 1<br />
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error<br />
# 1  Short offline       Completed without error       00%     26669         -<br />
# 2  Short offline       Completed without error       00%     26646         -<br />
# 3  Short offline       Completed without error       00%     26622         -<br />
# 4  Short offline       Completed without error       00%     26598         -<br />
# 5  Extended offline    Completed without error       00%     26577         -<br />
# 6  Short offline       Completed without error       00%     26575         -</p>
<p>SMART Selective self-test log data structure revision number 1<br />
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS<br />
    1        0        0  Not_testing<br />
    2        0        0  Not_testing<br />
    3        0        0  Not_testing<br />
    4        0        0  Not_testing<br />
    5        0        0  Not_testing<br />
Selective self-test flags (0&#215;0):<br />
  After scanning selected spans, do NOT read-scan remainder of disk.<br />
If Selective self-test is pending on power-up, resume after 0 minute delay.</p>
<p>See http://www.captain.at/howto-linux-smartmontools-smartctl.php for further SMART info.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/10/14/50-hard-drives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Maps and your Garmin on Ubuntu and Windows</title>
		<link>http://tech.kulish.com/2009/06/16/google-maps-and-your-garmin-on-ubuntu-and-windows/</link>
		<comments>http://tech.kulish.com/2009/06/16/google-maps-and-your-garmin-on-ubuntu-and-windows/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 08:17:10 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[garmin]]></category>
		<category><![CDATA[gps]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=56</guid>
		<description><![CDATA[Or, &#8220;Where the hell are we?!&#8221; Part 2: I recently bought a Nuvi 255W for some business travel coming up. I didn&#8217;t want to install Map Source since I don&#8217;t plan on buying any map packs any time soon. What I found was Garmin Communicator. Windows: Straight forward download and install. Linux (Ubuntu): apt-get install [...]]]></description>
			<content:encoded><![CDATA[<p>Or, &#8220;Where the hell are we?!&#8221; Part 2:</p>
<p>I recently bought a Nuvi 255W for some business travel coming up. I didn&#8217;t want to install Map Source since I don&#8217;t plan on buying any map packs any time soon. What I found was Garmin Communicator.</p>
<p>Windows:<br />
Straight forward download and install.</p>
<p>Linux (Ubuntu):<br />
apt-get install wine-gecko<br />
Download Garmin Communicator<br />
Download Firefox for Windows<br />
Use wine to install Firefox and the Communicator plugin</p>
<p>Adding Waypoints:<br />
To add waypoints using Google Maps, run the Windows version of Firefox.<br />
Navigate to Google Maps and search for the location you want to add a waypoint for.<br />
Click the &#8220;send&#8221; link, you should have a GPS selection now.<br />
Select your GPS Manufacturer, in this case &#8220;Garmin&#8221;. This will send you to my.garmin.com.<br />
At my.garmin.com, select which GPS you want to add the waypoint to.<br />
Click the &#8220;Send to GPS&#8221; button.</p>
<p>All done.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/06/16/google-maps-and-your-garmin-on-ubuntu-and-windows/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Raw FTP Commands</title>
		<link>http://tech.kulish.com/2009/05/22/raw-ftp-commands/</link>
		<comments>http://tech.kulish.com/2009/05/22/raw-ftp-commands/#comments</comments>
		<pubDate>Fri, 22 May 2009 14:04:11 +0000</pubDate>
		<dc:creator>Null</dc:creator>
				<category><![CDATA[Daemons]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[ftp]]></category>

		<guid isPermaLink="false">http://tech.lan.side/?p=57</guid>
		<description><![CDATA[I retrieved it from here: http://www.nsftools.com/tips/RawFTP.htm List of raw FTP commands (Warning: this is a technical document, not necessary for most FTP use.) Note that commands marked with a * are not implemented in a number of FTP servers. Common commands * ABOR &#8211; abort a file transfer * CWD &#8211; change working directory * [...]]]></description>
			<content:encoded><![CDATA[<p>I retrieved it from here: http://www.nsftools.com/tips/RawFTP.htm</p>
<p>List of raw FTP commands<br />
(Warning: this is a technical document, not necessary for most FTP use.)</p>
<p>Note that commands marked with a * are not implemented in a number of FTP servers.</p>
<p>Common commands</p>
<p>    * ABOR &#8211; abort a file transfer<br />
    * CWD &#8211; change working directory<br />
    * DELE &#8211; delete a remote file<br />
    * LIST &#8211; list remote files<br />
    * MDTM &#8211; return the modification time of a file<br />
    * MKD &#8211; make a remote directory<br />
    * NLST &#8211; name list of remote directory<br />
    * PASS &#8211; send password<br />
    * PASV &#8211; enter passive mode<br />
    * PORT &#8211; open a data port<br />
    * PWD &#8211; print working directory<br />
    * QUIT &#8211; terminate the connection<br />
    * RETR &#8211; retrieve a remote file<br />
    * RMD &#8211; remove a remote directory<br />
    * RNFR &#8211; rename from<br />
    * RNTO &#8211; rename to<br />
    * SITE &#8211; site-specific commands<br />
    * SIZE &#8211; return the size of a file<br />
    * STOR &#8211; store a file on the remote host<br />
    * TYPE &#8211; set transfer type<br />
    * USER &#8211; send username </p>
<p>Less common commands</p>
<p>    * ACCT* &#8211; send account information<br />
    * APPE &#8211; append to a remote file<br />
    * CDUP &#8211; CWD to the parent of the current directory<br />
    * HELP &#8211; return help on using the server<br />
    * MODE &#8211; set transfer mode<br />
    * NOOP &#8211; do nothing<br />
    * REIN* &#8211; reinitialize the connection<br />
    * STAT &#8211; return server status<br />
    * STOU &#8211; store a file uniquely<br />
    * STRU &#8211; set file transfer structure<br />
    * SYST &#8211; return system type </p>
<p>ABOR<br />
Syntax: ABOR</p>
<p>Aborts a file transfer currently in progress.</p>
<p>ACCT*<br />
Syntax: ACCT account-info</p>
<p>This command is used to send account information on systems that require it. Typically sent after a PASS command.</p>
<p>ALLO<br />
Syntax: ALLO size [R max-record-size]</p>
<p>Allocates sufficient storage space to receive a file. If the maximum size of a record also needs to be known, that is sent as a second numeric parameter following a space, the capital letter &#8220;R&#8221;, and another space.</p>
<p>APPE<br />
Syntax: APPE remote-filename</p>
<p>Append data to the end of a file on the remote host. If the file does not already exist, it is created. This command must be preceded by a PORT or PASV command so that the server knows where to receive data from.</p>
<p>CDUP<br />
Syntax: CDUP</p>
<p>Makes the parent of the current directory be the current directory.</p>
<p>CWD<br />
Syntax: CWD remote-directory</p>
<p>Makes the given directory be the current directory on the remote host.</p>
<p>DELE<br />
Syntax: DELE remote-filename</p>
<p>Deletes the given file on the remote host.</p>
<p>HELP<br />
Syntax: HELP [command]</p>
<p>If a command is given, returns help on that command; otherwise, returns general help for the FTP server (usually a list of supported commands).</p>
<p>LIST<br />
Syntax: LIST [remote-filespec]</p>
<p>If remote-filespec refers to a file, sends information about that file. If remote-filespec refers to a directory, sends information about each file in that directory. remote-filespec defaults to the current directory. This command must be preceded by a PORT or PASV command.</p>
<p>MDTM<br />
Syntax: MDTM remote-filename</p>
<p>Returns the last-modified time of the given file on the remote host in the format &#8220;YYYYMMDDhhmmss&#8221;: YYYY is the four-digit year, MM is the month from 01 to 12, DD is the day of the month from 01 to 31, hh is the hour from 00 to 23, mm is the minute from 00 to 59, and ss is the second from 00 to 59.</p>
<p>MKD<br />
Syntax: MKD remote-directory</p>
<p>Creates the named directory on the remote host.</p>
<p>MODE<br />
Syntax: MODE mode-character</p>
<p>Sets the transfer mode to one of:</p>
<p>    * S &#8211; Stream<br />
    * B &#8211; Block<br />
    * C &#8211; Compressed </p>
<p>The default mode is Stream.</p>
<p>NLST<br />
Syntax: NLST [remote-directory]</p>
<p>Returns a list of filenames in the given directory (defaulting to the current directory), with no other information. Must be preceded by a PORT or PASV command.</p>
<p>NOOP<br />
Syntax: NOOP</p>
<p>Does nothing except return a response.</p>
<p>PASS<br />
Syntax: PASS password</p>
<p>After sending the USER command, send this command to complete the login process. (Note, however, that an ACCT command may have to be used on some systems.)</p>
<p>PASV<br />
Syntax: PASV</p>
<p>Tells the server to enter &#8220;passive mode&#8221;. In passive mode, the server will wait for the client to establish a connection with it rather than attempting to connect to a client-specified port. The server will respond with the address of the port it is listening on, with a message like:<br />
227 Entering Passive Mode (a1,a2,a3,a4,p1,p2)<br />
where a1.a2.a3.a4 is the IP address and p1*256+p2 is the port number.</p>
<p>PORT<br />
Syntax: PORT a1,a2,a3,a4,p1,p2</p>
<p>Specifies the host and port to which the server should connect for the next file transfer. This is interpreted as IP address a1.a2.a3.a4, port p1*256+p2.</p>
<p>PWD<br />
Syntax: PWD</p>
<p>Returns the name of the current directory on the remote host.</p>
<p>QUIT<br />
Syntax: QUIT</p>
<p>Terminates the command connection.</p>
<p>REIN*<br />
Syntax: REIN</p>
<p>Reinitializes the command connection &#8211; cancels the current user/password/account information. Should be followed by a USER command for another login.</p>
<p>REST<br />
Syntax: REST position</p>
<p>Sets the point at which a file transfer should start; useful for resuming interrupted transfers. For nonstructured files, this is simply a decimal number. This command must immediately precede a data transfer command (RETR or STOR only); i.e. it must come after any PORT or PASV command.</p>
<p>RETR<br />
Syntax: RETR remote-filename</p>
<p>Begins transmission of a file from the remote host. Must be preceded by either a PORT command or a PASV command to indicate where the server should send data.</p>
<p>RMD<br />
Syntax: RMD remote-directory</p>
<p>Deletes the named directory on the remote host.</p>
<p>RNFR<br />
Syntax: RNFR from-filename</p>
<p>Used when renaming a file. Use this command to specify the file to be renamed; follow it with an RNTO command to specify the new name for the file.</p>
<p>RNTO<br />
Syntax: RNTO to-filename</p>
<p>Used when renaming a file. After sending an RNFR command to specify the file to rename, send this command to specify the new name for the file.</p>
<p>SITE*<br />
Syntax: SITE site-specific-command</p>
<p>Executes a site-specific command.</p>
<p>SIZE<br />
Syntax: SIZE remote-filename</p>
<p>Returns the size of the remote file as a decimal number.</p>
<p>STAT<br />
Syntax: STAT [remote-filespec]</p>
<p>If invoked without parameters, returns general status information about the FTP server process. If a parameter is given, acts like the LIST command, except that data is sent over the control connection (no PORT or PASV command is required).</p>
<p>STOR<br />
Syntax: STOR remote-filename</p>
<p>Begins transmission of a file to the remote site. Must be preceded by either a PORT command or a PASV command so the server knows where to accept data from.</p>
<p>STOU<br />
Syntax: STOU</p>
<p>Begins transmission of a file to the remote site; the remote filename will be unique in the current directory. The response from the server will include the filename.</p>
<p>STRU<br />
Syntax: STRU structure-character</p>
<p>Sets the file structure for transfer to one of:</p>
<p>    * F &#8211; File (no structure)<br />
    * R &#8211; Record structure<br />
    * P &#8211; Page structure </p>
<p>The default structure is File.</p>
<p>SYST<br />
Syntax: SYST</p>
<p>Returns a word identifying the system, the word &#8220;Type:&#8221;, and the default transfer type (as would be set by the TYPE command). For example: UNIX Type: L8</p>
<p>TYPE<br />
Syntax: TYPE type-character [second-type-character]</p>
<p>Sets the type of file to be transferred. type-character can be any of:</p>
<p>    * A &#8211; ASCII text<br />
    * E &#8211; EBCDIC text<br />
    * I &#8211; image (binary data)<br />
    * L &#8211; local format </p>
<p>For A and E, the second-type-character specifies how the text should be interpreted. It can be:</p>
<p>    * N &#8211; Non-print (not destined for printing). This is the default if second-type-character is omitted.<br />
    * T &#8211; Telnet format control (<CR>, <FF>, etc.)<br />
    * C &#8211; ASA Carriage Control </p>
<p>For L, the second-type-character specifies the number of bits per byte on the local system, and may not be omitted.</p>
<p>USER<br />
Syntax: USER username</p>
<p>Send this command to begin the login process. username should be a valid username on the system, or &#8220;anonymous&#8221; to initiate an anonymous login.</p>
]]></content:encoded>
			<wfw:commentRss>http://tech.kulish.com/2009/05/22/raw-ftp-commands/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
