Archives for: January 2013

01/24/13

  10:23:00 pm, by The Dreamer   , 1549 words  
Categories: Hardware, Computer, Storage, Ubuntu, FreeBSD

SSD Craziness

Over the last year, I started buying SSD drives. It used to be that they seemed pretty expensive, and of questionable performance and reliability. But, all things have improved over the years. And, when 120GB drives dropped under $1/GB (initially after rebates, later before rebate [if any]). I didn't have an immediate need for an SSD drive at the time, but I envisioned replacing the drive in my (u) laptop. And, perhaps my (w) laptop....beyond that I wasn't sure.

 3/05/12 - Patriot Pyro 120GB             - $159.99-$40 rebate = 119.99
 3/20/12 - OCZ Agility 3 120GB            - $139.99-$30 rebate = 109.99
 4/27/12 - Mushkin Enhanced Chronos 120GB - $ 99.99
 5/16/12 - OCZ Solid 3 60GB               - $ 74.99-$20 rebate =  54.99
 8/10/12 - Sandisk 128GB                  - $ 79.99
11/21/12 - Kingston HyperX 2K 240GB       - $149.99
 1/18/13 - Sandisk Extreme 120GB          - $ 89.99-$15 reward =  74.99
 1/18/13 - Sandisk Extreme 120GB          - $ 89.99-$15 reward =  74.99

But, during this time...I had the lhaven misstep Where I had picked up the 60GB drive for that, but ended up using the Mushkin 120GB drive instead. The OCZ Agility 3 120GB had gone in as OS drive for my Xen Cloud Experiment. And, stayed when I went on to making it FreeBSD. Cut up initially as 64k boot, 32GB swap, 16GB L2ARC for the mirrored 1.5TB drives to help with dedup...and the rest...63GB root zpool.

Somehow the Patriot got misplaced for a while, so it got overlooked during the chaos.

After a 'break'. I picked up the Sandisk 128GB drive. Thinking that it might be a better choice to use to finally replace the (u) laptop harddrive. Though I waited until after the NN conference in October to do it, but before I went to LISA in December. Though I didn't finally upgrade the the OS to 12.04 (from 10.04) until just last week. I had thought about doing a clean install to 64-bit....since there were some issues since I upgraded the memory to 8GB. But, changing the hibernate method seemed to have solved the issue....so decided to leave it 32-bit. Though my (w) laptop is 64-bit...though it only has 4GB. Not sure if I'll upgrade it to 8GB. Or when I'll upgrade its harddrive to SSD.

Things have been kind of tight since...on the 128GB Sandisk drive. partly because swap got a bit bigger...had suspected that 8GB swap was iffy for hibernation....so had bumped that up. Plus the original harddrive was 160GB. But, the lion share of space consumption is my Windows XP VM. But, it get's the job done.

Meanwhile...around this time I got the idea that instead of making the risky upgrade of my two Ubuntu servers from 10.04 to 12.04, that I would set up two new FreeBSD servers and migrate the essential services over before deciding the future of those systems. So, I acquired a pair of Shuttle XS36V's...4GB of memory for each...and then eventually the plan was to acquire a pair of SSDs for them. Which I finally did last week as a pair of SanDisk Extreme 120GB drives. (with the help of $30 from Best Buy Reward Zone....and this purchase should get me a $5 reward zone soon.) And, these will probably get installed as FreeBSD 9.1.

Pages: 1· 2

01/23/13

  12:05:00 am, by The Dreamer   , 493 words  
Categories: Software, b2evolution

Somehow my site got hacked....

...to inject bad SEO and links into Google. And, possibly collect info on my visitors?

Not entirely sure how it got in...the timestamp of the affected files is Apr 1, 2012. But, that was also the date that I upgraded to version 4.1.3, previous version was 4.1.2 done on January 16th....before that I was on 3.3.3 (Feb 14, 2010).

I do weekly backups of my site, so I narrowed down the alteration to having taken place between May 21st and May 28th.....though it wasn't easy...since I expire stored backups after 6 months....though fortunately I still had backups of my backups, so I could go back to before April 1st...and see that the file did change between March 26th and April 2nd, but php code wasn't prepended until later.

Perhaps I need to keep up on updates closer...

In the 4.1.0 line, the release dates were:

2011-09-08 - 4.1.0
2011-10-03 - 4.1.1-beta
2011-11-02 - 4.1.2
2012-03-02 - 4.1.3
2012-04-03 - 4.1.4
2012-07-24 - 4.1.5b
2012-11-23 - 4.1.6

Currently anything less than 4.1.6 isn't recommended. I see that 4.1.4 contained fixes against SQL and JS injection. Hmmm....

Wonder if I need to do some kind of change detection to my backup process....

Its hard to upgrade when there aren't diff bundles (which is why I stayed at 3.3.3 for so long), though I'm getting better at keeping my customizations out of the core (or fixing bugs on my own...) Plus discovering Meld has helped as well. Was interesting that one time, it showed diffs between releases, but no diff between latest release and my version. The bug I fixed got fixed the same way.... Though I think I have Meld ignoring differences in end of line and white space.... since the distribution files are CRLF, and I'm on Linux/FreeBSD...and the files are apparently such that vim can't figure out if its DOS and hide the ^M's or not.

Hopefully the upgrade to 5.0 will be simple...

In the history of my site...I was on 0.9.2 on June 7th, 2006 (released May 22)....from 0.9.0.12 on July 23rd, 2005 (released May 6). And, then finally upgrading to 2.4.1 on April 27, 2008 (released Mar 16), though prompted in part because I switched hosting providers....worked up to 2.4.7 on September 6, 2009 (released May 27)....and then to 3.3.1 on September 8, 2009 (released August 8). I did the upgrades to 3.3.2 and 3.3.3 on February 14, 2010 (3.3.2 was released Nov 9, 2009 and 3.3.3 was released Dec 15, 2009).

Guess it was good that I have my sites with Google's Webmaster tools...so that it could send me a "Notice of Suspected Hacking on ..." and stopped crawling my site until I address the problem.

And, looks like only my sites that are b2evolution were affected, my other sites are also 4.1.3 and hadn't been upgraded since.... Though its strange, since those sites were setup with fewer customizations with the intent that upgrading them would be easier. But, I had been thinking of shutting down the sites....

Pages: 1· 2

01/12/13

  05:26:00 pm, by The Dreamer   , 562 words  
Categories: Software, BOINC

New Chart option at Radioactive@Home

I was poking around on the Radioactive@home message boards, after finding that my sensor had stopped working when the app was updated from v1.69 to v1.72....it was complaining every 11 seconds with "No heartbeat from client for 30 sec - exiting".

And, it wasn't because I had to build my own newer boinc client for box last month. The Ubuntu apt version is 6.12.33, and didn't seem to be any moving to upgrade it for 10.04LTS or in any PPA that I could find. And, downloading the binaries from the boinc.berkeley.edu site didn't work, as they depend on newer libraries than exist for 10.04LTS. So, I had to grab the source

git clone git://boinc.berkeley.edu/boinc.git

and build that against my 10.04LTS system....and that worked (at least the client did, which is all I really needed)...until now.

Though I read in forums that v1.72 wasn't supposed to be released (very little testing had been done), but it was needed to support newer sensors which are out in the field now.....oh well.

Well, I supposed the HEAD of the boinc might be too bleeding edge as well. 7.0.44 is considered the development version, and not recommended. While the recommended version is 7.0.28.

The wiki page on getting source says:

Branches

Various versions of the code are available at any given point:

Development

The master branch contains the latest source code for all components of BOINC. It is always under development, and has not necessarily been thoroughly tested.

Client releases

The client software (client and manager) is maintained as follows:

The code for each release is 'tagged'. For example, the code for version 6.3.14 is tagged with client_release_6_3_14.
A 'branch' is created for each released minor version. For example, the branch client_release_6_2 is the code for the latest release of version 6.2.

Except I tried to git checkout client_release_7_0_28, and it couldn't be found. Nor could I do git checkout client_release_7_0. Eventually, poking around on the site some more, I found that the tags were different. They uses '.' instead of '_' in version separators. Though couldn't get to 7.0.28 directly...had to get 7.0 first.

So, git checkout client_release_7.0 followed by git checkout client_release_7.0.28. Got me the source for the current recommended version.

Now at 7.0.28, I couldn't get _autosetup to complete...missing test/version.inc.in and py/Boinc/version.py.in. Well, copy those from the HEAD down, seemed to kind of work...though configure was having a lot of issues. Lots of SAH_LIBEXT and SAH_DLLEXT command not founds, along with others. Turns out files were missing from the m4 directory. Compare with HEAD, and copy over Makefile.in, ax_lang_compiler_ms.m4, sah_links.m4, sah_largefile_breaks_cxx.m4, sah_libext.m4, sah_select_bitness.m4, and sah_staticize_ldflags.m4.

Now I do configure, this time I look to see what things its complaining about missing, and add more -dev libraries, along with wxWidgets....now I have a boincmgr, should I choose to use it.... Though the compile didn't go well.

Missing a couple of header files.... lib/md5.h and client/dhrystone.h. And, then I go and blunder with doing a make install, which clobbers my /etc/init.d/boinc-client and /etc/default/boinc-client with something that doesn't fit the Ubuntu environment. So, once again a quick restore from BackupPC of these two files, and BOINC is working again.

While writing my post on the Radioactive@Home forum, I spotted a new chart.... Which I have now made into the footer of this site:

However, what was interesting...was going back through the last couple of weeks, to find this span....

12/17/2012 to 12/23/2012

Maybe the world was supposed to end on December 21st?

01/06/13

  04:28:00 pm, by The Dreamer   , 401 words  
Categories: Home, Safety & Security

Better Late than Dead?

On account that I was out of town over Christmas this year, I delayed the annual Christmas present to my home.... The gift of new smoke detector batteries.

I decided that I would do it New Year's day instead. But, when I went to replace the smoke detector batteries, I discovered that I had neglected to purchase a 4 pack. So, eventually I remembered to order a 4 pack via Amazon.com...evidently the same item that I had ordered previously....but in mid-November before last Christmas....

So, I finally got around to doing it today....and I hadn't done a full test of my home security system in a few months, and since the siren detector will always alert the monitoring company unless I'm doing a sensor test. It seemed like a good time to test things. Might be the only activity some of the less active locations get, to make sure they're working.

It was hard to test the motion detectors, since my main keypad is seen by both detectors and the test requires that the detector 'clear' before seeing the new motion event and recording the test success. And, the detectors don't have any visual indication normally that they've seen anything. The activity light is only active a short while for initial configuration. I actually prefer the sensor this way....not like other people's systems where its always active, so you get tempted to see if there's a way to get past it and not be seen by it :>>

A second keypad is on my wish list....though not entire sure where I would put it for the most benefit but not get in my way. The handset version might be better, except that I already have enough trouble misplacing other things around my home...I wouldn't want to be misplacing this.

Later I also decided that I should replace the batteries in my CO detector and test it...just to complete things.

Always interesting that it has a peak reading...though not ever high enough to have gone off. But, every time that I've looked at it...its always read 0. Wonder when there is CO?

Full story »

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop

bloglovin

There are 20 years 1 month 24 days 12 hours 32 minutes and 48 seconds until the end of time.
And, it has been 4 years 11 months 3 days 1 hour 30 minutes and 8 seconds since The Doctor saved us all from the end of the World!

Search

January 2013
Mon Tue Wed Thu Fri Sat Sun
 << < Current> >>
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 1
This seal is issued to lawrencechen.net by StopTheHacker Inc.
multiblog engine

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime