Month: February 2013

Posted on

More on Contacts

My Eye

Well, last week, I had my checkup after trying contacts (Day 1, Day 2, Days 3 4 and 5).  I complained about how poorly I saw.  The doctor gave me a mini eye exam and said we’d make a slight change.  Well, I have another trial pair and can see much better.  Yesterday, I tried to take a picture of my eye (because they were nice and clear).  After 8 pictures, I got the one above.  it isn’t great but….

Posted on

Odd Finder Display Problem

20130210_FinderError

This morning, I downloaded a few sermons from Sermon Audio.  When I went to rename them in Finder (on Mac OSx), the picture above it what I saw.  Notice anything?  Yeah….characters are missing.  I tried doing a google search but didn’t find anything.  I’ll reboot and see if the problem is fixed.

[Update 2013-02-12 06:58:22] Well, it didn’t take a reboot.  After 30 minutes or so, everything returned to normal.  Don’t know why.  Don’t know what caused it.

Posted on

Apple, Filevault2, and CoreStorage

Fev08 {033/365} Dirty deeds, done dirt cheap!

Twice in as many weeks, I’ve had a Mac come across my desk with the disk hosed up.  I mean really hosed up.  In these cases, we give people a new computer, help them migrate whatever we can, then redo the old computer (it takes less time).  But, in both of these cases, the hard drive has been encrypted with FileVault2.  Now, that isn’t a problem (I had the passwords) but by this point, I just wanted to blow everything on the drive away and do a reinstall of everything.

But, if the disk is encrypted with FileVault2 (aka a Core Storage Volume) you can’t mess with it from disk utility.  Even if you unlock it.  You have to go out to the command line.  

The first time I really hosed the disk and had to erase it (which you can do).  The second time, I was able to simply erase the Core Storage Volume.

This site was where I found the commands:  http://blog.fosketts.net/2011/08/05/undocumented-corestorage-commands/

I’m posting it here to help me when I need it again.

Image from Antimidia via flickr

Posted on

Gay “Marriage”

IMG_7615

First off, I’m not going to spend this post talking about why I’m against gay “marriage.”  I am because the Bible says marriage is between 1 man and 1 woman.  Out of wedlock sex with anyone is a sin regardless of who it happens between.  Quite simply, I want to say this isn’t a “rights” issue.  It is a “we want to redefine a word to fit what we want” issue.  Why?

Well, quite simply gays, straights, upside-down, or right-side up, all people could get married.  What?!?!  I hear the cries.  No they couldn’t you say.  Yes they could I say.  Cyndi and I got married.  A gay, lesbian, purple-people-eater or whoever had the same right.  Any man could marry a woman and any woman could marry a man.  Everyone was equal and had the same rights.  But yet, the opponents of “traditional” marriage pressed on.

They wanted the word marriage redefined in the law so a man could marry a man or a woman a woman (or, I assume to a purple-people-eater).  Well, on Tuesday, that happened in the UK when the House of Commons in England voted to redefine marriage.

Interestingly enough, though, this has caused havoc with the definition of other words.  For example, adultery is defined something like out of wedlock sex between a man and a woman.  Interesting.  Did you catch that?  That means that gay people can’t commit adultery in the eyes of the law.  That causes all sorts of other havoc.  If you’re “married” then sex with anyone other than your “other” should be adultery.  Something similar happened in the US with divorce.  The laws in the states with gay marriage proposals didn’t adjust to include other terms.

You can’t have your cake and eat it too.  This isn’t a civil-rights issue.  It is a we-want-to-force-you-to-accept-our-way-of-life issue.  Before the law changes, everyone had exactly the same rights.  They just couldn’t  do what they wanted.  There is a difference.

Image from o. ortelpa via flickr