You will need:

• WSL2 setup with Firefox installed (mine uses Ubuntu 20.04)
• VcXsrv
• geckodriver

How it works

VcXsrv starts up an X server on the Windows host machine, and what WSL will do is connect to this server to pass on the details of what programs need to be displayed (in this case, the browser window). Geckodriver is there purely as a middle layer for Selenium to be able to interact with Firefox.

VcXsrv setup

This setups the X server so that Windows can display graphical data coming from the Ubuntu instance.

1. Download and install
2. Start it up with the the command line parameter “-ac”. This flag removes access control restrictions for connecting clients (which is okay as long as this server isn’t exposed on the open Internet and that the only client connecting is the Ubuntu instance)
3. Allow connections to VcXsrv on Windows Firewall

The “-ac” flag and allowing the program through Windows Firewall is pretty important. When I didn’t do this, Ubuntu would give me cryptic error messages like “Broadway display type not supported”, but once I set up these access controls, everything was fine.

Bash setup

Install firefox

sudo apt install firefox

Export DISPLAY variable in .bashrc (or for whatever terminal you use, maybe .zshrc, etc.)

export DISPLAY=$(ip route | awk '{print $3; exit}'):0

This will configure your DISPLAY variable to use the IP address listed in the resolv.conf file. The IP address listed there is the IP address of the X server that will be used for displaying the browser window.

Start up VcXsrv as described in the above and then try to open Firefox. The Firefox window should open.

Geckodriver setup

This acts purely as the API interface that allows Selenium to interact with Firefox. Selenium looks for this executable when controlling the web browser.

1. Download geckodriver (make sure to get the Linux one and not the Windows one)
2. Put it in /usr/bin (or alternatively some other folder in your PATH)

Selenium sample on Python

I tend to use Python when running Selenium code, and I haven’t tried it on another language (I imagine the principles are similar). Here is a piece of sample code for starting up the browser and opening up a website, but really any Selenium code can be used.

import time

from selenium import webdriver
from selenium.webdriver import DesiredCapabilities

def execute_with_retry(method, max_attempts):
    e = None
    for i in range(0, max_attempts):
        try:
            return method()
        except Exception as e:
            print(e)
            time.sleep(1)
    if e is not None:
        raise e

capabilities = DesiredCapabilities.FIREFOX
capabilities["marionette"] = True
firefox_bin = "/usr/bin/firefox"
browser = execute_with_retry(lambda: webdriver.Firefox(
    firefox_binary=firefox_bin, capabilities=capabilities), 10)

browser.get("https://www.google.com")

time.sleep(10)

browser.close()

I always thought that Petra was just a single structure – the same one that gets shown everywhere, but that structure is just The Treasury that’s a part of an entire city built in the rocks.

From the entrance, we walked 30 minutes through a winding gorge formed by a fault line that tectonic forces split apart until we reached The Treasury. Stray dogs followed us every step of the way hoping for scraps of food. Leaving at 6:00 didn’t help because the only people that the dogs could beg from was us.

We arrived so early we were practically the only people there. We admired Petra on our own without the large crowds of tourists everywhere. We took our time walking up to it, all around it, up the slope to get a better view (nobody is allowed inside it though). We did all of this before the crowds showed up.

Petra was the capital of a kingdom of the Nabataean, a group of nomadic Arabs who established the city as a major trading hub. The Nabataeans constructed massive structures by carving it all out of the sandstone. Although it’s called The Treasury, the building is believed to have been the mausoleum of the Nabataean King Aretas IV.

The area around Petra is also home to the Bedouin people, a group of nomadic Arab people who inhabit the desert regions in northern Africa and the Arabian Peninsula. In the modern times, many have abandoned their nomadic lifestyle and many Bedouin around Petra work as tour guides, offer camel rides, among other things. One of the Bedouin people there is actually the descendent of a woman from New Zealand who married a Bedouin man and wrote about it, called Married to a Bedouin.

The area is over 250 square kilometers, something I totally didn’t expect (because I totally did not do my research before I went). I’m not too big on hiking and I was totally not prepared for a hike that day – I would have totally brought more water, and more food along with me that day. Despite that, I hiked up the 900 or so steps to the monastery anyway, while getting hassled by vendors trying to sell me their junk. Temperature-wise, the temperature shot up to a whopping 20 degrees Celsius from the 0 degrees Celsius just two days before. My body did not like that.

We spent about 8 hours in Petra, walking along the rock faces, seeing the ancient ruins, hiking up the hill, but if I had more energy I totally would have hiked up the other trials for even better views of the area.

For dinner we had mansaf, probably the national dish of Jordan. It’s a delicious dish made with lamb and rice dish mixed with a yogurt sauce! This tasted even better than the chicken rice dish we had the day before. I had no idea that lamb and yogurt was such a great combination. It was a great meal to refuel after such a long day.

More photos of Petra here

Originally, we had planned on visiting Sedan too. This was where the Germans made their initial breakthrough into France that eventually led to the French surrender. We intended to go to the Museum of the Last Cartridge, the local museum there, thinking that it was about the World War II battle, but actually it was about the Battle of Bazeilles during the Franco Prussian War (which I had never heard of before). In the end, we didn’t have time for it anyway so it was okay that we didn’t go.

The Maginot Line

Not far from Sedan, was a preserved portion of the Maginot Line in northeastern France, known as the Ouvrage La Ferté. The Maginot Line was a series of defensive fortifications stretching along the French border from Luxembourg to Italy built after World War I to protect France from a future German invasion. The location at the Ouvrage La Ferté saw the heaviest fighting during the Battle of France in World War II. It eventually was overwhelmed by German forces and its entire garrison was killed.

It’s exterior still shows the damage from the battle and grass has grown over the craters that were once there. It is possible to tour the inside of the bunker, but it is only available to large group tours.

Driving through the area, it’s pretty common to still see bunkers on the side of the road.

The Ouvrage La Ferté is in a pretty remote location, which makes sense considering it’s a defensive fortification, and because of the rain the night before, we ended up driving on some flooded roads, and even narrow farm roads that even Google Maps didn’t have a name for.

Verdun

From Ouvrage La Ferté, we drove to Verdun. Verdun was the site of another major battle in World War I, and to remember the fallen soldiers, a memorial containing their skeletal remains was constructed.

Unbeknownst to us, the ossuary was actually closed when we arrived, so we never got to go inside. We could only peek through the windows and see was a blurry view of stacks of bones. In front of the monument lies a military cemetery.

Nearby the ossuary is the actual fort that played a role in the Battle of Verdun. The fort fell to the Germans without a fight since the French had abandoned the fort thinking that the fort would have been ineffective against the heavy artillery that the Germans were using. Eventually, the fort was recaptured.

The road leading up to the fort was interesting too because some of the old trenches were preserved. The zig zag of the trenches can still be seen. Its purpose was to ensure that shrapnel exploding inside the trench would be contained. A straight trench would have allowed a clear path for the shrapnel to fly through more of the trench.

From there we drove three and a half hours to Strasbourg, where we’d start our fourth day of our road trip. That’s all for now!

• Maginot Line
• Verdun

The flight was to arrive in Kuala Lumpur at around 13:00 and we would depart for Bali at 21:50. Arriving at 13:00, we should have been able to arrive in the city via Grab between 14:30 – 15:00, but it took at least an hour at the immigration line so we didn’t get to the city until after 16:00. This would leave us around 5 hours in Kuala Lumpur, which is not great, but not terrible.

We had only eaten breakfast, so by this time, we were starving. So we went to Lot 10. Everything looks super good, but in actually only tasted okay. I thought it’d be on par with my trip to Singapore.

Next, we visited a nearby street market. The market reminded me a lot of Singapore – similar food options (bak kut teh, chili crab, stingray, etc.), which makes sense since Singapore used to be a part of Malaysia.

Our next destination was the iconic Petronas Twin Towers, but all of a sudden out of nowhere, it started pouring with thunder and lightning. At first the thunder was a few kilometers away judging but how long it took to hear the sound, but not long after it was right on top of us.

We got on a Grab to head over there, but the sudden rainstorm brought traffic to a complete stop and it was barely moving. After being in the car for 30 mins and having gone less than a kilometer, the driver advised that we head to the airport directly as there wouldn’t be enough time to hit up the twin towers and make our flight. We reluctantly agreed.

During the car ride, I chatted with the driver about living in Kuala Lumpur. The driver was Cantonese in enthnicity but was born and raised in Kuala Lumpur, which I didn’t expect at all. I had forgotten about how stuck we were in traffic while chatting with the driver (at one point the driver took a bathroom break and left the keys in the ignition).

Eventually, I looked on Google Maps, and saw there was no way we’d make it to the airport by car. We decided to get dropped off at the metro station in the pouring rain and we’d take public transit the rest of the way. Check it out in Mike’s video (the raining part starts at ~5:10).

That was pretty much our trip to Kuala Lumpur. After a big delay at the airport and the freak rainstorm, we really only had 3 hours in the city to do stuff, which was too bad. See the rest of the photos here.

Bash for Windows has been working pretty great for me until I needed to run Selenium Webdriver on it. I quickly learned that it wouldn’t work just work right out of the box, and the set up for it is quite convoluted.

You will need

• Bash for Windows
• Xming – This will actually allow the Window to appear on the screen
• geckodriver – Selenium now needs this to run Firefox

Bash setup

Install Firefox:

sudo apt-get install firefox

Export DISPLAY variable in ~/.bashrc. Just add this to the ~/.bashrc:

export DISPLAY=:0

Xming setup

Just download it from the link above and run it.

Download geckodriver

Download geckodriver from the link above and put in the /usr/bin/ folder in Bash for Windows.

Running Selenium

Here is a piece of sample Python code I used to setup the web browser. It will setup the browser, open Google, sit there for 10 seconds and then quit.  Make sure to have Xming running otherwise the browser isn’t going to start.

import time

from selenium import webdriver
from selenium.webdriver import DesiredCapabilities

def execute_with_retry(method, max_attempts):
    e = None
    for i in range(0, max_attempts):
        try:
            return method()
        except Exception as e:
            print(e)
            time.sleep(1)
    if e is not None:
        raise e

capabilities = DesiredCapabilities.FIREFOX
capabilities["marionette"] = True
firefox_bin = "/usr/bin/firefox"
browser = execute_with_retry(lambda: webdriver.Firefox(
    firefox_binary=firefox_bin, capabilities=capabilities), 10)

browser.get("https://www.google.com")

time.sleep(10)

browser.close()

The nice thing about all of this is that I can push a code change to git, and Jenkins can build it, run through all the tests and then deploy to production automatically.

Layout of a pipeline script

Pipeline scripts are written in Groovy, which is a variant of Java. In general, a pipeline script is laid out like this:

node {
    def SOME_CONSTANT = "whatever"
    ...

    stage('some stage name like Build') {
        // Stuff to do as a part of this stage
    }

    stage('another stage') {
        // More stuff
    }

    ...
}

Each stage represents a stage in the pipeline (e.g. building, beta deployment, prod deployment etc.)

Defining some constants

First, a list of constants can be defined that can be used throughout the pipeline so that if the pipeline script gets reused somewhere, only these constants have to be changed. I’m not aware of anything that lets me reuse a pipeline in Jenkins without copying and pasting the code somewhere else so for now I’ll have to live with copying and pasting.

My project uses Maven so I got Jenkins to download its own copy of Maven that it can use to execute builds and have defined it as a constant. The name I’ve given it in the Jenkins Global Tool Configuration is “Maven 3.3.9” exactly. My project also uses Tomcat so there are some Tomcat specific things in there that may or may not be relevant to your use case.

def MAVEN_HOME = tool 'Maven 3.3.9'
    def WORKSPACE = pwd()

    def PROJECT_NAME = "name-of-project"
    def WAR_PATH_RELATIVE = "App/target/${PROJECT_NAME}.war"
    def WAR_PATH_FULL = "${WORKSPACE}/${WAR_PATH_RELATIVE}"
    def TOMCAT_CTX_PATH_BETA = "Tomcat-context-path-for-the-beta-stage"
    def TOMCAT_CTX_PATH_PROD = "Tomcat-context-path-for-the-prod-stage"
    def GIT_REPO_URL = "URL-to-git-repo-ending-in-.git"

Preparation Stage

First, the code has to be retrieved from the repository before it gets built. Jenkins allows storing username/password pairs so that they can be referenced without having to write out the password in plaintext. Jenkins uses a “credential ID” for this.

    stage('Preparation') {
        git branch: "master",
        credentialsId: "credentials-ID-stored-in-Jenkins-that-can-access-the-git-repo",
        url: "${GIT_REPO_URL}"
    }

Build Stage

Next, the code must be built and unit tested. “mvn clean install” will do just that (depending on what you want, you can always put in a different maven goal). The junit command is just there to take the resulting XML that gets generated during the build process and posts a graph of how many tests were run for each build.

    stage('Build') {
        sh "'${MAVEN_HOME}/bin/mvn' clean install"
        junit '**/target/surefire-reports/TEST-*.xml'
    }

Beta Stage

Once the build succeeds, you’ll want to deploy it to a beta environment, so integration tests can happen. The following happens at this stage:

1. Get the right credentials to get permissions to Tomcat
2. Call the deploy method to deploy the war file in Tomcat (more on that later)
3. If the deployment fails for whatever reason, print out the deployment log for debugging and fail the build
4. If the deployment succeeds, run the integration tests (the command to do this may differ based on use case)

    stage('Beta') {
        withCredentials([[$class: 'UsernamePasswordMultiBinding',
            credentialsId: 'credential-id-for-tomcat',
            usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
                // Password is available as an env variable, but will be masked 
                // if you try to print it out any which way
                def output = deploy(WAR_PATH_FULL, TOMCAT_CTX_PATH_BETA,
                        env.USERNAME, env.PASSWORD)
                if (output.contains("FAIL - Deployed application at context path " + 
                        "/${TOMCAT_CTX_PATH_BETA} but context failed to start")) {
                    echo "----- Beta deployment log -----"
                    echo output
                    echo "-------------------------------"
                    currentBuild.result = 'FAILURE'
                    error "Beta stage deployment failure"
                }
            }

        echo "Running integration tests"
        sh "'${MAVEN_HOME}/bin/mvn' -Dtest=*IT test"
        junit '**/target/surefire-reports/TEST-*.xml'
    }

The deploy method is what takes care of the actual deployment to Tomcat, which is how the Jenkins build tells Tomcat about the newly built war file. The deploy method is below (be sure to change the server IP and port). Alternatively, I could have built my project as an embedded jar file, but that has a different challenge in figuring out how to get Jenkins to tell the OS to execute the newly built jar file as a particular user.

1. Based on the Tomcat context path, decide whether a beta or production deployment is happening
2. Make a copy of the build war file and add .prod or .beta to the end of it so as to keep the original
3. Set the Spring profile to use on the newly copied war file (more on that later)
4. Call the curl command to do the actual deployment to Tomcat (more on that later)

def deploy(warPathFull, tomcatCtxPath, username, password) {
    def envSuffix = ""
    def isBeta = tomcatCtxPath.contains("beta")
    if (isBeta) {
        envSuffix = "beta"
    } else {
        envSuffix = "prod"
    }
    sh script: "cp ${warPathFull} ${warPathFull}.${envSuffix}" 
    setSpringProfile(warPathFull, isBeta)
    def output = sh script: "curl --upload-file '${warPathFull}.${envSuffix}' " +
            "'http://${username}:${password}@localhost:8081/manager/text/deploy" + 
            "?path=/${tomcatCtxPath}&update=true'", returnStdout: true
    return output
}

In the case of my project, I’m building a single war file that does not have a Spring profile (beta/prod) defined. This means that I have to manually define this before I deploy the app to Tomcat since there are some things that differ between beta and prod like database URL’s. To do this, I wrote a method that opens the war file like a zip (jar/war files are zip files) and adds a line to my application.properties to define a Spring profile.

Admittedly, doing this zip file manipulation seems kind of hacky. Alternatively, I could have defined my build such that I had a separate beta build and a prod build to avoid modifying the zip file, but the drawback is that I’d then have to build my code twice.

def setSpringProfile(warPathFull, isBeta) {
    def zipFileFullPath = warPathFull + "." + (isBeta ? "beta" : "prod")
    def zipIn = new File(zipFileFullPath)
    def zip = new ZipFile(zipIn)
    def zipTemp = File.createTempFile("temp_${System.nanoTime()}", 'zip')
    zipTemp.deleteOnExit()
    def zos = new ZipOutputStream(new FileOutputStream(zipTemp))
    def toModify = "WEB-INF/classes/application.properties"

    for(e in zip.entries()) {
        if(!e.name.equalsIgnoreCase(toModify)) {
            zos.putNextEntry(e)
            zos << zip.getInputStream(e).bytes
        } else {
            zos.putNextEntry(new ZipEntry(toModify))
            zos << zip.getInputStream(e).bytes
            zos << ("\nspring.profiles.active=" + (isBeta ? "beta" : "prod")).bytes
        }
        zos.closeEntry()
    }

    zos.close()
    zipIn.delete()
    zipTemp.renameTo(zipIn)
}

A curl command to Tomcat is what actually does the deployment. To deploy a file to Tomcat, do the following below. This will deploy the war file to Tomcat and instantly run it, thus it will be accessible at the given context path.

curl --upload-file 'path-to-war-file' http://username:password@server-address:port/manager/text/deploy?path=/tomcat-context-path&update=true

Prod Stage

The same kind of stuff happens in the prod stage as in the beta stage with a few exceptions. The following happens at this stage:

1. Get the right credentials to get permissions to Tomcat
2. Call the deploy method to deploy the war file in Tomcat (except this time it is prod)
3. If the deployment fails for whatever reason, print out the deployment log for debugging and roll back the deployment
4. If the deployment succeeds, save the build files, and then the pipeline is finished. Alternatively, smoke tests can be run at this point, but I did not implement this in my project

Rollback is important because if the deployment fails, you don’t want to be stuck with a broken environment. Since build artifacts are saved on successful deployments, these same artifacts can be brought back if future deployments fail. This means they can be redeployed so that the code can be fixed before another deployment happens.

    stage('Prod') {
        withCredentials([[$class: 'UsernamePasswordMultiBinding',
            credentialsId: 'credential-id-for-tomcat',
            usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
                // Password is available as an env variable, but will be masked 
                // if you try to print it out any which way
                def output = deploy(WAR_PATH_FULL, TOMCAT_CTX_PATH_PROD, env.USERNAME, env.PASSWORD)
                if (output.contains("FAIL - Deployed application at context path " + 
                        "/${TOMCAT_CTX_PATH_PROD} but context failed to start")) {
                    echo "Prod stage deployment failure, rolling back deployment"
                    echo "----- Prod deployment log -----"
                    echo output
                    echo "-------------------------------"
                    step([$class: 'CopyArtifact',
                            filter: "${WAR_PATH_RELATIVE}",
                            fingerprintArtifacts: true,
                            projectName: "${PROJECT_NAME}",
                            target: "${WAR_PATH_RELATIVE}.rollback"])
                    deploy(WAR_PATH_FULL + ".rollback/" + WAR_PATH_RELATIVE,
                            TOMCAT_CTX_PATH_PROD, env.USERNAME, env.PASSWORD)
                    currentBuild.result = 'FAILURE'
                    error "Prod deployment rolled back"
                } else {
                    archiveArtifacts artifacts: "${WAR_PATH_RELATIVE}*", fingerprint: true
                }
            }
    }

At the end you get to have something like this:

That pretty much sums up the whole Jenkins pipeline that I’ve been using lately for Spring projects!

At Frankfurt Airport, when Edward and I lined up to check in, we were the only two Chinese people in line.  We seemed very out of place.  Some of the people gave us these stares that seemed to ask “why are you flying to Kiev?” We wanted to visit Chernobyl and shoot AK-47’s.

Our experience on the plane was dreadful.  Four crying babies/toddlers plus jet lag plus one hour delay was not a good combination. No sleep for me I guess.  Worst flight ever.

Awkward Car Ride

The hostel arranged transportation for us and so when we arrived, I looked for someone holding a sign with my name on it (first time ever!).  The driver was not happy at how we were late (not that we could do anything about it).

Probably since he was late, he drove like a maniac.  He drove way faster than the posted limits and passed every car on the highway.  The expected 45 min ride was reduced to almost 20 minutes.  The driver didn’t speak English.  No one said a word during the entire ride.  Awkward.

I had read before that people sometimes get driven to random places by taxi drivers before they get mugged.  By getting the hostel transportation, we minimized that risk.  Despite that, I was at peak alertness the whole time, making sure he was going the right general direction (I vaguely remembered the directions from the airport to the hostel).

Dream House Hostel

This is by far one of the hostels I’ve ever stayed at.  The staff were extremely helpful.  We asked them like a thousand questions and they happily answered them every time.  They treated security very seriously.  Kiev might not be safe, but I felt safe leaving my passport and cash in the locker in the room.

Security Measures

During our trip planning, we had read about the potential dangers in going to Kiev from the Canadian travel report about Ukraine.

The report tells travelers to “exercise a high degree of caution”.  It warns of dangers such as pickpockets, passport scams, armed robbery, racially motivated violence, muggings, etc.

Seeing how the hostel’s security was pretty good, we left our valuables in the room.  We each carried a decoy wallet with nothing in it except a scan of our passports and the cash we needed for the day.  No credit cards, no real ID, no cards at all.

If anybody steals a wallet, no big.  Better to lose $30 than all our money.  Nobody can scam us for our passports if we aren’t carrying it.  I didn’t even put on a hidden money belt.  The less I brought the better.  We felt pretty prepared, and luckily nothing happened.

Language

People in Kiev generally speak Ukranian or Russian.  I know neither.  I also don’t know the Cryllic writing system.  Even if I wanted to ask in English how to get somewhere, I can’t even pronounce the name of the place.  When I went to Greece, I could at least pick out the greek alphabet (side effect of studying math and physics), but in Kiev, I can’t even read anything.  Too bad.

Food

The first night we arrived in Kiev, we had no idea what kind of food was around here.  We couldn’t even read the menus anyway.  Picking a restaurant was a matter of randomly walking into a restaurant.  To our surprise, our random pick turned out to be Japanese food.  Interesting.  No pictures needed.  Vancouver has an abundance of Japanese restaurants.  Beer is worth taking a picture of though.  I can’t even read the label.

One of the hostel staff had recommended to us the Golden Dukat Coffee House.  I wish I took more pictures here, but I found someone else’s travel blog with good pictures of it!  Good coffee, good dessert.  And they have an English menu!

We were told that Borscht is one of the traditional soups in Ukraine.  When I tried it, its taste was so familiar and I had to think about where I had tried it before.  It tasted a lot like the vegetable soup that people can get at Hong Kong style cafes (羅宋湯).  I Googled it later, and apparently the Hong Kong recipe (while a little bit different) is a derivative of it.  What a coincidence.

Independence Square

By far the largest city square I have been to.  For me this was the place to see in Kiev.  The pictures here don’t do justice to how epic it was.

At the square, there would always be these people carrying pigeons around.  They kept coming up to me with me and I had no idea what they wanted.  Later I found out that apparently they’re trying to get tourists to take a picture with them holding a bird.  Not sure why that’s cool but okay.

There were also people dressed up like Mickey Mouse or Shrek trying to get little kids to take pictures with them for money.  They did this even when the temperature was above 30 degrees Celsius.

St. Andrew’s Church

Nearby our hostel, there was a nice church.  It’s architecture was quite different from anything I’d seen before.

Friendship Arch

This arch was built to commemorate the unification of Ukraine and Russia when Ukraine was still part of the Soviet Union.

Street Market

On the way from our hostel to Independence Square, we walked along a long stretch of road with many street vendors selling souvenirs, trinkets and other random stuff.  People there even sold gas masks, replica German WWII medals, and fake guns.

Trip Ideas for Next Time

After we came back to Vancouver, we found out that the hostel started offering tours to abandoned missile silos, helicopter rides, and Yak plane acrobatics!  If only the hostel were offering those tours.  We would have totally gone to those.  There’s always next time.

Links to photo albums:

• Kiev
• Kiev (Edward’s Photos)

From watching the TV show Band of Brothers, I learned of the Eagle’s Nest, a surprise birthday gift for Adolf Hitler for his 50th birthday.  Situated on the ridge on the Hoher Göll (or Kehlstein Mountain) at an elevation of over 1800m in Obersalzburg, Berchtesgaden, the house served as a private retreat for Hitler.

Because this area was so remote and hard to access by train, we chose to rent a car to drive there for a day trip that Saturday.  In our group of three, only one person could legally drive.  I had lost my driver’s license and my other friend only had a learner’s license.  Our car reservation said we were supposed to get a Mercedes A Class (the cheapest car they had with automatic transmission), but we got a Renault Megane instead.  I think that worked out better for us though because I think that car was a little bit roomier.

Originally, we were supposed to leave at 9 in the morning, but we had to make a stop at our friend’s house to pick up someone, because he apparently partied too hard and crashed at another friend’s place.  He was quite hungover when he got in the car and he stayed that way for pretty much the whole trip.  I was invited to that party too, but I didn’t go precisely because I didn’t want to end up like the way he did.

I set a course to the Eagle’s Nest on the GPS and off we went.  Originally, our route involved going through Austria, but I had to modify the route such that we stayed in Germany because we didn’t want to have to purchase a vignette (it’s an identifier on the car you pay for that lets you drive in that country if the car isn’t from there). 

We all knew that some parts of the Autobahn had no speed limit, but we had yet to see this for ourselves.  Near the outskirts of the city, there were still speed limits, but as we got further, those limits disappeared.  Although for a lot of the journey there, we couldn’t really make use of that since there were traffic jams all over the place.

The drive ended up taking nearly six hours rather than the four hours that Google Maps told me.  And for the whole journey, my hungover friend slept in the back on his side while I chatted with the driver so that he wouldn’t get so bored.

When we arrived, we parked the car near the Berchtesgaden railway station and proceeded to take the bus up (the house itself is only accessible by bus).  We left Stuttgart at around 10, and reached the top of the Eagle’s Nest at around 4:30 in the evening.

As the bus went up the mountain, we began to see the view getting nicer and nicer.  I guess it was kind of like seeing an airplane lift off and watching the houses below getting smaller and smaller.

The bus dropped us off at the entrance to the elevator up to the main building and when we got out of the bus, we all felt the chilling rain that started.  I don’t know what the temperature was at the time, but it felt like it was less than five degrees.  Before leaving the house in the morning, I knew it’d be cold up there, but apparently it was colder than I thought.  For the whole time that I was up there, my extremities were super cold, but at least the rest of my body was warm enough.  Luckily the rain had stopped when we took the gold-plated elevator up to the house itself. 

After the end of the war, the house was denazified, and converted into a restaurant.  All that remains is the architecture.  The house itself isn’t really that amazing looking, but it has historical significance.  Also, the view from up there is amazing.  What surprised me was how accurate Band of Brother’s portrayed the house.  They pretty much built a set that looks exactly like the real thing and even had scenes where they tried to get up the mountain (and that mountain looked really similar too).

There was nothing on the mountain except for this one house.  And from there, we could see Salzburg (about 35 km away) and other nearby towns.  We could also see the Königssee and other mountains in the Bavarian Alps.  Because of the rain earlier, there were still some rainclouds hovering around, and with the rain, we also got to see a rainbow.  The best part about that was that we were at so high of an elevation, we got to look down at the rainbow.

We only stayed up there for less than an hour because we had to take the last bus back down, but that was okay though.  It was nice for me to be able to visit the Eagle’s Nest and enjoy the view from the mountain (even if it was damn cold).  It’s also a place where most North American tourists won’t be able to go because it’s so remote and that there are so many more popular places to go for them.

On the way home, the roads had a lot less traffic than earlier, which let us really try out the Autobahn.  My friend had reached the car’s top speed of around 190 to 195 km/h (perfectly legal by the way).  The whole time he drove, I had a really strong urge to have a try myself, but I didn’t have my driver’s license.  After we gassed up the car, I couldn’t resist the urge anymore and so I drove.  We all knew that if anything happened, we’d be pretty screwed.  Because of that, I didn’t drive for very long.  I probably only drove for about 20 minutes. 

Even though there was no speed limit, I felt quite uneasy driving at 190 km/h and it just didn’t feel right.  I didn’t really feel that I had control of the car, but that might have been because I hadn’t driven for six months.  It was fun while it lasted I guess.  Even though our car was going pretty fast, we saw a few Benz’s and Porsches go by at speeds of over 200 km/h.  They just zoomed right past us.

After three and a half hours of driving, we safely arrived back in Stuttgart.  It was great being able to see the Eagle’s Nest (even if for such a short time).  It was one of those places that I had to see before I left Europe.  Driving on the Autobahn was great too and now I can say that I’ve done that.  It was a great trip.

More photos here

Link: http://www.heerengandhi.com/2009/07/29/firefox-icon-went-missing-in-windows-7-heres-a-fix/comment-page-1/

After almost four years of using my Inspiron 1520, its age finally caught up with it and its light literally went out.  The backlight refuses to turn on now.  I came back from Berlin last Monday and found my computer in this state.  I left it off during that time too.  During this time, I had trouble doing any blogging and uploading any photos.

Google told me that the problem lay with either a loose connection, the inverter or the lamp.  I tried to check this out myself and open the computer case, but the screws refused to budge.  People online somehow got theirs open, but I couldn’t.

Unfortunately, my warranty expired so I’d have to pay to get this computer fixed.  I looked at my options on the Dell site and the North American Dell Support refused to help me and kept referring me to the European side even though I bought my computer in Canada (I really don’t know what these guys at the call centers are doing).  After about three calls to the support line, I finally found someone helpful and she told me that I had to change my laptop registration such that it showed a European location before I could get it fixed.  An alternative option would have been to send the computer back to Canada to get it fixed.

What I did instead was just buy a new laptop.  My laptop is already super old and already can’t really keep up with my tasks anyway, so I suppose it’s time for an upgrade.  What surprised me was that laptops in Germany (from their Best Buy/Future Shop equivalents anyway) cost so much more than in North America.  In fact, it was cheaper for me to buy my computer in Canada and get my parents to ship it to me rather than buying it locally.  I’m sure there are cheaper places, but I don’t exactly know how to look through all these German websites.  Another added advantage in buying from Canada is that I’d have a computer with the US Keyboard layout rather than the German one.  And in the future when my laptop needs repairs, it’ll be easy.

In the meantime, I’m using a 17 inch LCD screen that I borrowed from a friend.  This will suffice until my new computer arrives.  No more shining a lamp at my computer screen and squinting my eyes to see the screen anymore.  I also don’t need to be using my phone to go on the internet at home either.