Mel’s Hole
Broadcasting from his double-wide trailer in Nevada, Art bell was good at what he did, and in his heyday, there was one broadcast that had me completely enthralled. Mel's hole is one of those stories I listened to on the edge of my seating cursing commercials because they where too long.
I came across some mp3s of the broadcast(s) and here they are. The story is basically this
The hole, the story goes, exists outside of town on land once owned by a man who calls himself Mel Waters. For years, he said, it was used as the neighborhood dump for trash, old appliances, dead cattle. When the hole never filled up, Waters measured its depth by lowering weighted fishing line into it. After 80,000 feet, he gave up. Amazed by this odd place (which dogs and birds avoided), Waters called radio host Art Bell, whose late-night show on conspiracies and the paranormal attracts a huge national audience.
Download The Radio Broadcast Here:
http://files.tnlsoft.com/melshole.zip
A short video about Mel's Hole
http://www.uwtv.org/programs/displayevent.aspx?rID=5160&fID=1474
News Story:
http://community.seattletimes.nwsource.com/archive/?date=20020414&slug=melshole14m
A quick google search for Mel's Hole will bring you tons more information.
I run a radio stream that plays all of Mel's hole plus a lot of similar things at http://www.u7radio.org
Mel’s HoleGoogle Hardware in 1998
I remember in 1997 when someone first pointed me to http://google.stanford.edu a student project that was supposed to beat out WebCrawler as a search engine. I wasn't too impressed at the time... It's interesting to think how huge Google has become and how I don't really use anything else to search the web. Let alone the dozens of other services I use Google for regularly. At the time the Google.standford.edu homepage looked something like , complete with the default to only show 10 results.
What is even more impressive is the hardware that ran google back then:
- 2 300 MHz Dual Pentium II Servers with 512MB of RAM. There are 9 9G drives between the two machines. The main search engine ran on these.
- An IBM RS6000 with 4 processors and 512MB of memory. It had 8 9G drives internal.
- A Machine with 3 9G drives, and there are 6 4G drives attached to a Sun Ultra II.
- An IBM disk expansion box had another 8 9G drives.
- A Sun Ultra II with dual 200MHz processors, and 256MB of RAM.
- A homemade disk box which contains 10 9G SCSI drives.
All of Google in 1998 as a whole:
Installing A Subversion Server On Windows
While I would never recommend running a subversion server on anything but a Linux machine, I was recently asked to write a tutorial on doing so on a Windows based machine. Installing a subversion server on windows can be a daunting task. Luckily a project has come forth to make that task significantly easier called Visual SVN.
VisualSVN serves as a front end management console for your windows based subversion server. This will save you from manually editing configuration files, generating ssh keys and many other things.
Drop by their homepage and grab the free version of VisualSVN here:
http://www.visualsvn.com/server/download/
The installer has will ask a handful of questions. The first will ask if you want to install VisualSVN Server and the management console together:

It is recommended that you choose “VisualSVN Server and Management Console” which should already be selected for you.
Next you will be asked for the specifics of how your server is going to run:

1) Location: This is where the server’s program files will reside. Usually the default works just fine.
2) Repositories: This is where your subversion repositories will live. As your repositories will grow over time, it is best to choose a location with plenty of space.
3) Server Port: You can usually leave this to port 443 and keep the secure connection checkbox ticked. Be sure your not running anything on that port such as a website with an SSL certificate. Also be sure your firewall is configured to allow connections on the port you specify here.
4) Subversion Authentication: I typically recommend to use this method as opposed to windows authentication as it allows you a bit more flexibility. However your in house requirements may be a bit different. This tutorial covers using subversion authentication.
At this point the installer has everything it needs to install both subversion and the management console. Upon completetion you will be given the option to start the management console. Leave that checked and press finish.
CONFIGURING THE SERVER:When the management console first opens it will give you information about your newly installed subversion server.

The most important info you will need is the server URL. By default this is going to be your windows machine name. If you have a domain name pointing to the server or a unique IP address we will want to change this. Follow these steps:
1.) Click on “VisualSVN Server” on the left pane.
2.) Select Action from the top menu and click Properties. (ACTION->PROPERTIES)
You should get a dialog that looks similar to this. If it looks different be sure Visual SVN Server is selected as described in step 1.

3.) Click on the Network Tab. Here is where you can specify your fully qualified domain name or unique IP addresses, if you have additional addresses and/or IP addresses you can also bind them here:

The server name field is where you will want to specify your unique IP address, fully qualified domain name or NetBios name that already has a binding to your machine.
4.) If you change your Machine name as described in the last step, you will also need to regenerate your SSL certificate. To do this click on the certificate tab.
5.) Click on Change Certificate
6.) A new dialog will open. Select “Create new self signed certificate” then click NEXT
7.) You will be asked for the Common Name this is your fully qualified domain name or NetBios name.
8.) The following steps will ask you a handful of questions about your organization for the certificate. As this is a self signed certificate you can elect to leave these blank, although I highly recommend filling out the information as you may run into problems with certain subversion clients. Click next until the new certificate is generated.Press APPLY then OK and your subversion server will restart.
CREATING YOUR FIRST REPOSITORY:
You now have a subversion server installed and configured on your windows machine. Next we will want to create our first repository and user that can access that repository.
We’ll start with creating the initial repository. To do this right click on Repositories on the left side pane, select CREATE NEW REPOSITORY.

A dialog will appear asking for the name of the repo (see below). For this tutorial we are just going to use the name ‘test’. We will also check the box to create the default repository structure.

Once you click OK you will see your repository appear in the left side pane. We now have our first (empty) repository on our new server. It’s time to create a user that can access that repository.
CREATING A USER:Your repository is useless until you (or someone) can access it. During the installation earlier in this tutorial we specified that we wanted to use Subversion authentication. This section of the tutorial assumes you are using Subversion authentication.
1.) To create a new subversion user right click USERS in the left pane and click CREATE USER.
2.) You will be prompted for the username and asked to specify and confirm a password.
3.) The new user should appear under users in the management console. Right clicking the user will allow you to delete or change the password if/when needed.
Now that you have created the user, you will want to be sure your new user has access to the test repository we created earlier.
On the left pane you will want to right click on your test repository and click properties.

The Security tab should pop up. Click the ADD button and add the user you just created. You will also want to click on that user and select the permissions the new user should have. In this example I’ve selected READ/WRITE. (see below)

Press APPLY then OK.
You are now ready to use your first subversion repository. The next part of the tutorial explains using TortoiseSVN on the client machine, which is typically the development machine that needs access to the source code on the server you have just setup.
INSTALLING AND USING TORTISESVN
The first thing you will want to do is head over to the Tortisesvn homepage and download the client:
http://tortoisesvn.net/downloads
The installer is pretty straight forward and all of the defaults should be just fine for our purposes.
You will typically be asked to reboot after installation. Go ahead and reboot and then we’ll get started.
ACCESSING OUR TEST REPOSITORY
Once your machine has rebooted it’s time to make use of our test repository. For this example I’m going to download our first repository in an empty folder that I’ve called source.
Open up Windows explorer by going to MY COMPUTER->C:\ create a new folder called SOURCE and navigate into your new folder.
You should now be looking at an empty folder. Right click and select SVN Checkout.

You will want to fill in the details of your new subversion repository. The most important thing here is the URL of your repository. All of your repositories will be accessed with a url that is formulated like this:
https://DOMAIN/IP ADDRESS.COM/svn/test/trunk/
https – be sure you have the s so that you are using a secure connection.
DOMAIN/IP ADDRESS.COM – this is the fully qualified domain name, IP Address or NetBios address you configured during the CONFIGURING THE SERVER section of this tutorial.
/svn/ -- all of your repositories will live under the svn folder.
/test/trunk – test is the name of the repository we created and we want to work with the trunk of the repository.
So all together my checkout url looks like:
https://127.0.0.1/svn/test/trunk/

You may want to adjust the checkout directory to meet your needs, for this example we are downloading the repository directly into the folder named source that we created. If you specify a folder that does not exist, it will be created during the checkout process.
The remainder of the options on this page should typically be fine at their defaults. If you have special needs when working with a project you may need to change some of these.
Once you are satisfied with the selection press OK.
Since we are using a self signed SSL certificate. The first time we access the repository, we will be warned that the issuer of our SSL certificate is unknown. This is fine and won’t cause any problems. By pressing Accept Permanently you will never get this warning again. This message can be eliminated by purchasing an SSL certificate from a trusted source such as GoDaddy.

Once you choose to accept our unsigned certificate you will be prompted for your login credentials. This is where you enter the username/password you created earlier in this tutorial.
If all goes well you should have checked out revision 1 of our empty repository called test.
Adding A File To The Repository And Committing It
For this example we’ll create a simple text file, add some content, commit it, make some changes, commit again and view the differences between versions.
Right click in the Windows Explorer window you have just performed your checkout to and select NEW->TEXT DOCUMENT. For this tutorial we are just going to name it sample.txt.
I’m going to populate our sample.txt file with a bit of PHP code as seen in the below screenshot.

I’ll save the code I’ve put into the file and now I’m ready to commit my changes.
Since the file called sample.txt doesn’t actually exist in the repository yet, we’ll first add it, then commit it.
To add the file, right click on the sample.txt file and select TortoiseSVN->Add…

We are now ready to commit the file to the repository. Right click our file again and you should now see a new option titled SVN Commit.

The commit dialog will appear (see below). Here is where you enter in what you have done so that other developers can see your comments and notes about changes. This is where you will also see what files are to be committed and the statuses of these files.

Enter your comments and press ok. You should get a dialog letting you know that revision 2 was committed to our test repository.
Next, lets make a few changes to the file and repeat the commit process. I wont go through the commit process again. Just follow the steps above each time you wish to commit a change.
At this point I’ve made two sets of changes, and committed my changes for each one. Let’s have a look.
GETTING THE DIFFERENCE BETWEEN REVISIONS:For this tutorial let’s say I wish to find out what has changed in this file. I’m going to right click on the file once again, but this time select TortoiseSVN->Diff with Previous Version.

This may take a few seconds depending on the extent of the changes. Once processing is done, you will get a split screen of the two versions with any changes highlighted. In my case it looks like this:

If you where to click on Show log instead, you would get a list of all revisions, who made the revisions, and the comments the developer entered about that particular revision.

Right clicking on any of these revisions gives you a myriad of options to view the differences with previous revisions, your working copy and more.
I hope this was helpful in getting you started with a full windows based subversion solution.
- Brian
Installing A Subversion Server On WindowsTop offbeat vacation spots for 2010 Part 2 of 2
This is part 2 of a 2 part series. If you missed part one. Check it out: Top offbeat vacation spots for 2010 Part 1 of 3
Anyone else in desprate need of a vacation? I know I could always use a break from the stresses of work and household responsibilities. Being who I am, I typically don't go for your usual vacation spots.
Chernobyl
In April on 1986 the worst nuclear disaster that has ever hit planet earth took place at the Chernobyle nuclear power plan in the Ukraine. Rating a 'Level 7 ' on the Internation Nuclear Event Scale. The accident sent 400 times more fallout than was released by the atomic bombing of Hiroshima. 336,000 people had to be resettled. The hardest hit by the disaster was the nearby city of Pripyat. Pripyat had a population of around 50,000.
While long term exposure isn't recommended, it is considered safe to visit.
From Wikipedia:
There is a 17-mile Exclusion Zone around Chernobyl where officially nobody is allowed to live, but people do. These "resettlers" are elderly people who lived in the region prior to the disaster. Today there are approximately 10,000 people between the ages of 60 and 90 living within the Zone around Chernobyl. Younger families are allowed to visit, but only for brief periods of time.
Eventually the land could be utilized for some sort of industrial purpose that would involve concrete sites. But estimates range from 60 – 200 years before this would be allowed. Farming or any other type of agricultural industry would be dangerous and completely inappropriate for at least 200 years. It will be at least two centuries before there is any chance the situation can change within the 1.5-mile Exclusion Zone. As for the #4 reactor where the meltdown occurred, we estimate it will be 20,000 years before the real estate will be fully safe.
24 years later, you can now visit and get a healthy dose of reality (and radiation). Tours will run you around $500 for a single person, with the price going down for groups of more than 2. Get the full scoop on their offerings here:
http://tourkiev.com/chernobyltour/
One of my favorite photo journals of the area is Elena's Motorcycle Ride through Chernobyl. Here commentary adds so much to her solo visit to the area. Check it out here:
http://www.kiddofspeed.com/default.htm
Cinci Subway
Cincinatti, Ohio began building a subway system between 1920 through 1925. The $6 million bond issue in 1916 was exhausted in 1925, no further money was obtained, and construction never resumed. The incomplete subway system still lays below the city. As I lived 30 minutes from Cincinatti, I'm a bit dissappointed that I never got to go explore it.. It is the largest abandoned subway tunnel in the United States.
In the 1980s the city pitched the tunnels to Hollywood as an ideal location to shoot Batman Forever, To date though, the tunnels have not been used in any feature films.
Twice a year, tours are given, which is why it made it on my list. The Cincinnati Museum Center Heritage Programs provides a "Talk & Walk Tour," which lasts approximately two hours. It begins with a presentation about the history of the subway and continues with a five-block walk underground. A lot of new interest has been generated of this long abandoned failure of the city. In fact this June an hour long documentary about the history and current state of the subway will be released. Be sure to have a look at the trailer.
Here are some links with some great pics of what it looks like now.. as well as construction pics and a ton more info...

http://www.forgottenoh.com/subway.html
Even more detailed info here:
http://www.cincinnati-transit.net/subway.html
Any places that you would like to add?
Also See: My Trip To Bohemia Ghost TownTune in next Tuesday for Part 2 of my 2 part series.
Top offbeat vacation spots for 2010 Part 2 of 2Top offbeat vacation spots for 2010 Part 1 of 2
Anyone else in desprate need of a vacation? I know I could always use a break from the stresses of work and household responsibilities. Being who I am, I typically don't go for your usual vacation spots. I'm happy to announce my part 1 of a 2 part series of my Top Offbeat Vacation Spots for 2010.
Centralia, PA

If your heading out east be sure to make a quick stop in Centralia, PA. This is the town that the Silent Hill movie was loosely based off of. The ruins of Centralia Pennsylvania no longer exists on some maps. In 1962 someone decided to burn some trash in the pit of an abandoned strip mine which connected to a coal vein running near the surface. The result was one of the longest running underground fires in history.
For the next 20 years workers fought the fire by digging trenches and flushing the mines with water and ash. All efforts to extinguish the fire failed and government officials didn't make any serious attempts to save the town. By the early 80s the fire affected a majority of the town and homes had to be abandoned due to fire hazards and toxic levels of carbon monoxide.
One study that concluded in 1983 determined that the fire could burn for another century or more and could possibly spread over an area of 3700 acres.
As time passed, each feeble attempt to do anything to stop the fire or help the residents of Centralia would cost more and more due to the fires progression. Over 47 years and 40 million dollars later the fire still burns through old coal mines and veins under the town and the surrounding hillsides on several fronts. The fire, smoke, fumes and toxic gases that
came up through the back yards, basements and streets of Centralia literally ripped the town apart. Most of the homes were condemned and residents were relocated over the years with grants from the federal government although some die-hards refused to be bought out and some still remain in the town. Today Centralia is a virtual ghost town with only a few remaining residents. As they continue to live in their beloved homes now owned by the federal government, people pass every day along Route 61, most totally unaware of the history surrounding them and the sad story of Centralia.
Studies have shown that if the fire is not contained it will continue to spread following the rich coal deposits and eventually threaten the neighboring town of Ashland, less that two miles away. Many people including former (and current) residents of Centralia insist that there is more to this story than meets the eye. Some believe that the rich deposits of coal beneath the town itself is the reason for the forced relocation of the towns people and to force the town to go defunct, giving up its mineral rights. The stories around what is happening here vary depending on who you talk to or what you read. What is certain is what has happened to this small community and the fact that Centralia as it once was, will never be again.
Thinking of visiting or just want a lot more info with a lot of pictures? Check this site out: http://www.offroaders.com/album/centralia/centralia.htm
Seattle Underground
Being in the Pacific Northwest and living so near to Seattle, I can't believe I haven't done this yet. The story goes something like: June 6th 1889, Seattle's central business district was destroyed by a massive fire. The fire destroyed 33 city blocks. The fire crews made the mistake of turning on too many hoses at once to fight the massive fire, thus causing a massive loss in water pressure, which severely hindered their efforts. To counter these issues in the future the the city decided to regrade the streets one to two stories higher than the original street grade. The regrade would prevent common flooding of many areas of the city and the new street level would also help ensure that toilets did not back up at high tide.
During the regrade, the original sidewalks and roads where 12-30 feet below ground level. Ladders where placed so that people could climb from the sidewalks to the new entrances to the buildings. Many a drunk met their demise navigating these ladders. The ground floors of all of the buildings in the area became the basement, while the second floors became the ground level floor.
In 1907 the city condemned the Underground for fear of pneumonic plague. The basements were left to deteriorate or were used as storage. Some became illegal flophouses for the homeless, gambling halls, speakeasies, and opium dens.
Here is a quick little video with a short tour of the underground:
If your interested in visiting, a guided tour is going to run you about $15 per person. More info on tours here: http://www.undergroundtour.com/
There is a similar yet less interesting underground in portland: http://en.wikipedia.org/wiki/Shanghai_tunnels
Any places that you would like to add?
Also See: My Trip To Bohemia Ghost Town
Tune in next Tuesday for Part 2 of my 2 part series.
Top offbeat vacation spots for 2010 Part 1 of 2





