To do this I used virt-manager in Fedora 16. Initially virt manager didn’t give me an option to bridge the network interfaces, it was greyed out. I wanted to be able to ssh into these VMs inside my home network without having to go through the virt host. Turns out there’s an option to customize settings in the details panel just before you start the installation. Select it and bring up the VM’s detail panel to take advantage of MacVTap.

When the details panel comes up you can monkey with the networking of course. I selected the macvtap that my bare metal uses and set it to bridge mode.

Using this method both VM’s got a dhcp address from my home router and are able to talk to each other now.

Word of warning, don’t use VEPA mode. It’s something special that most router’s don’t haveyet that, from what I can gather, let’s the swtich do the bridging instead of the virt host.

Learned about this stuff here: http://virt.kernelnewbies.org/MacVTap

More info at
https://www.aeolusproject.org/
https://www.aeolusproject.org/audrey.html

This morning when it came on I suggested to my carpool buddy that I wished a built in feature of cars was to tell me why the light came on. Seems ridiculous to make me take it to someone to tell me what’s wrong with my car. Imagine if we had to take our computers to someone any time there was an error message in /var/log/messages. What a pain.

Ha! Take that car analogies of computers! I just made a computer analogy of cars!

I know you can buy those readers that will tell you the error codes. Although, my car is a VW that takes a non-standard reader and is more expensive than the common ones. Ah, German engineering.

(For my non-linux cohorts, /var/log/messages is the system log in linux)

Enter coverage.py: http://nedbatchelder.com/code/coverage/

I’m on fedora so $ yum install python-coverage installed it for me.
To get the details suggested above you need only run two commands.

~/git/audrey git:(oauth*)➤ coverage run audrey_start/test_audrey_startup.py
……………
Ran 15 tests in 2.601s

OK

The coverage run command executes your code just as if you had executed it without coverage.py, but has generated data about the code it’s executing as it’s running. You can see here I’ve executed this code’s unit test script. Next you display the report data:

~/git/audrey git:(oauth*)➤ coverage report audrey_start/*.py
Name                               Stmts   Miss  Cover
——————————————————
audrey_start/audrey_startup          472    270    43%
audrey_start/test_audrey_startup     217     19    91%
——————————————————
TOTAL                                689    289    58%

~/git/audrey git:(oauth*)➤ coverage report -m audrey_start/*.py
Name                               Stmts   Miss  Cover   Missing
—————————————————————-
audrey_start/audrey_startup          472    270    43%   126-132, 186-216, 237, 241-243, 247, 288, 352, 379, 382, 388, 414, 456, 544, 558-559, 585-601, 609, 630, 640, 654-689, 700-730, 739, 747, 774-794, 837-847, 854-857, 907-936, 955-957, 975-1125, 1139, 1151, 1190-1195, 1203-1229, 1264-1340, 1344
audrey_start/test_audrey_startup     217     19    91%   65, 130, 384, 420-428, 505-526
—————————————————————-
TOTAL                                689    289    58%

The coverage report command will give you the percentages missing for each script. The coverage report -m command will give you the exact lines missing from the unit test coverage. I checked a few of these lines that it reported, a quick check seems to indicate these are all actual lines of code that were not executed during the unit test run. Pretty useful data for measuring the effectiveness of your unit tests.

http://www.180movie.com/

Good stuff. Be patient through the Hitler stuff, he ties it in well.

I have great memories from that afternoon. I still have a copy of the recording and just listened to it. Thought it would be fun to post a copy of it.

Lemme see if I can remember the team that was there:
Radez: Acoustic, Vocals
Andrea: Vocals
Becca: Vocals
Brandon: Electric Guitar
Drew: Drums
Travis: Piano, Vocals
Kevin: Bass
Aaron: Violin
I think that’s everyone…

Here’s what we recorded with a 16 channel mixer, a 4 track recorder and a bunch of college students with instruments in an apartment living room.
01 You Are the One
02 God of Wonders
03 Psalm 61
04 Praise Be
05 Trust in the Lord

Work bought me a Kinesis Advantage keyboard in May. (Manufacturer’s Page) These are hard enough to get used to in a qwerty layout. It has a native Dvorak mode on it so I made the Kinesis my Dvorak keyboard and the keyboard I was using my qwerty. I had been using both since May. Unplugged the qwerty keyboard the first of September.

This pic is from before I unplugged the qwerty keyboard:

Just a fun fact to share.

… the statement “God is Love” means that his love find expressions in everything that he says and does.

The knowledge that this is so for us personally is the supreme comfort for Christians. As believers, we find in the cross of Christ assurance that we, as individuals, are beloved of God; “the Son of God…loved me and gave himself for me” (Gal 2:20). Knowing this, we are able to apply to ourselves the promise that all things work together for good to them that love God and are called according to his purpose (Rom 8:28). Not just some things, note, but all things! Every single thing that happens to us expresses God’s love for us.

Thus, so far as we are concerned, God is love to us – holy, omnipotent love – at every moment and in every event of every day’s life. Even when we cannot see the why and the wherefore of God’s dealings, we know that there is love in and behind them, and so we can rejoice always, even when, humanly speaking, things are going wrong. We know that the true story of our life, when known, will prove to be , as the hymn says, “mercy from first to last” – and we are content.

- J.I. Packer, Knowing God, Pages 122-123

This passage has blessed me as I’ve reflected on the things around me that go “humanly wrong”. Both in my and my family’s life and the life of the people around me. More often than not we do not specifically know, and may never truly know, why a particular event happened in someone’s life. Though, whether we’re glad or scared or frustrated or upset or don’t even care that some whatever has happened, we do know that it happened because our God loves us and is bringing himself glory through his creation.