0

The Joy of Wrong

I’m writing down this excerpt from “Poke the Box” by Seth Godin, as a reminder that we have to start and deliver. Even if it’s not the ideal solution for our application, program module, system integration, or network design. If we don’t have that initial stuff running we may procrastinate and spend all of our time just on research.

In the Pike Place Market in Seattle, you can still find the first Starbucks. There’s something wrong with it, though. It’s not quite right, not quite a Starbucks . The logo is different; the layout is different.

 

It turns out that the original Starbucks didn’t sell coffee.

 

They sold coffee beans and tea leaves and even herbs. But except for a sip or a taste of coffee brewed from a particular bean (drip, no espresso!), there was no cup of coffee to be had.

 

Starbucks was wrong. Jerry Baldwin, one of the founders, made a mistake. He thought the beans were the point, not the coffee. Left to Jerry’s vision of the future, Starbucks would certainly have failed. It took Howard Schultz, a trip to Italy, and an obsession with espresso to turn Starbucks into Starbucks. And Howard gets a lot of credit for making that happen.

 

But what if the “wrong” Starbucks had never been built? What if Jerry and his partners had said, “Well, we’re not sure if this bean thing is going to work, so let’s do nothing”? Without Jerry Baldwin and his flawed idea for a coffee bean store, there’d be no Frappuccino. One led to the other by the usual route, which is never a straight line.

 

The original Starship Enterprise was conceived by Matt Jefferies. It looked like a cross between a Frisbee and a can opener. Clearly wrong.

 

But Matt had the drive to deliver. He took the wrong start and revised and improved and innovated until the Enterprise we know and love came to be. The hardest part, it seems to me, was the first one, the wrong one.

 

Poking doesn’t mean right. In means action.

 

1

How to automount a remote share in Mavericks


You want to use Time Machine over a remote share. It is important to permanently mount it when you login to your Mac.

As an example let’s connect to a Western Digital My Cloud that has the default name WDMyCloud.

How to mount it

After launching the Finder you may see it at the Shared section

Shared WDMyCloud

and just click it and connect with the share you want.

If it’s not visible just select from the Finder’s Menu Go / Connect to Server...

At the Server Address: type

cifs://wdmycloud.local

You may change wdmycloud.local with the IP address of your NAS or remote share. Choose the type of connection and then just choose a share. It will show up like this

Shared wdmycloud.local

Auto mounting the share

Select from the top menu Apple / System Preferences... / Users & Groups / Login Items

Click the + button and now select your remote device from the left list under Shared.

WDMyCloud Connect As

Make the connection and select the share you want.

It’s done! Now every time you enter your Mac it will try to mount that share immediately.

A little note…

Apple guys like to be funny. See what would show up if you used smb: instead of cifs:

smb wdmycloud.local Connect As

You may be interested in Using an SMB share from Mac OS X in Linux

0

Apache2 rewrite rules are not working

You have just edited your .htaccess on the root of your new site with RewriteRules and it’s not working. Something like this for a WordPress installation

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>

There are two reasons for this to happen. The mod_rewrite is not enabled by default and your configuration may not allow the use of .htaccess

Enabling mod_rewrite

As I usually don’t mess with Apache I often forget it has a command to enable modules. It’s just like this.

sudo a2enmod rewrite

Enabling .htaccess files

Edit your site configuration file under /etc/apache2/sites-available/. At the Directory entry for your site files you need to allow the reading of directives in .htaccess files.

If you were editing the default site

        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

you would have to use AllowOverride FileInfo or even AllowOverride All. It’s your choice.

Get it to work

Finally you have to restart the Apache server to activate the changes

sudo service apache2 restart

That’s it!