Skip to content

Linux

  • in Linux
  • 1 min read

Passed RHCE!

I’ve intentionally been waiting to write this post, as I’ve not been so sure of what to write. I guess it all depended on the outcome of my RHCE-exam that I had yesterday. The results? Well, see for yourself.

SECTION I:    TROUBLESHOOTING AND SYSTEM MAINTENANCE
RHCE requirements:  completion of compulsory items (50 points)
overall section score of 80 or higher
RHCT requirements:  completion of compulsory items (50 points)

Compulsory Section I score:                        50.0
Non-compulsory Section I score:                    50.0
Overall Section I score:                           100

SECTION II:  INSTALLATION AND CONFIGURATION
RHCE requirements: score of 70 or higher on RHCT components (100 points)
score of 70 or higher on RHCE components (100 points)

RHCT requirement:  score of 70 or higher on RHCT components (100 points)

RHCT components score:                             100.0
RHCE components score:                             100.0

RHCE Certification:                                PASS

I just can’t believe that I aced the test! 100% correct, god! I have to tell you, I never ever thought this was possible, but the countless hours I spent studying and practicing for the test was well worth it. :)

I’ll be posting some tips and tricks concerning the RHCE-exam soon, so stay tuned.

  • in Linux
  • 2 min read

Creating, bridging and using host networking in Fedora 8/9 (VirtualBox)

As I’ve mentioned in previous posts, I’m quite fond of VirtualBox, and thus we write some more about it! A default installation will give every virtual machine you create an ip of 10.0.2.15, but what if you’d like to enable your virtual machines to be able to interact with each other, each of them having their own ip? Here’s where bridging comes into play. As I’m using Fedora 8, this little section is for – that’s right – Fedora 8 (works in Fedora 9 as well). I’ll be assuming that your host-machine is getting its ip from a DHCP-server.

Add the following line to the bottom of /etc/sysconfig/network-scripts/ifcfg-eth0:

BRIDGE=br0

Then create the file /etc/sysconfig/network-scripts/ifcfg-br0, and add the following:

DEVICE=br0
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes

Once you’ve done that, restart the network:

# service network restart

Now that we have that finished, you can create a virtual ethernet interface for VirtualBox like this:

# VBoxAddIF vbox0 USERNAME br0

Replace USERNAME with the username of the user you’ll be running VirtualBox as (the user michael would have put the username michael there).

Give all users write access to the device used by VirtualBox to communicate with the host network (/dev/net/tun in this case).

# chmod 0666 /dev/net/tun

Now, start VirtualBox and select your virtual machine, then go to Settings.

Then change Attached to to Host Interface, and type vbox0 into the field Interface Name.

And that’s basically it! If you’d like to create another virtual interface for VirtualBox, just run the line above again, only replace vbox0 with vbox1, vbox2, and so on. All depends on how many virtual machines you’re planning on running simultaneously.

Oh, if your virtual machine seems to stop at boot, when trying to get hold of the network information, it might be your firewall that’s causing the problem. So on the host-machine, disabling the firewall might do the trick:

# service iptables stop

Good luck!

How to display UTF-8 in your Putty bash shell

My girlfriend was having some problems displaying the correct characters while talking on IRC through irssi, and putty. Eventually I came to the conclusion that it wasn’t my server or irssi that was configured badly. Searching the internet I found this:

echo -ne 'e%Ge[?47he%Ge[?47l'

Simply put that into your .bash_profile or .bashrc and relog to your server. It’s a collection of terminal escape codes that together means ESC %G – “switch to UTF-8”.

  • in Linux
  • 2 min read

Quake Wars and switchscreen

Still being thrilled about having gotten my 22” monitor, after 2 years of nagging (I need to emphasize that I’ve spent TWO years nagging my better half about a damn monitor. Did I mention I spent 2 years?), I briefly spoke to a co-worker of mine about having nothing to play after I quit World of Warcraft. He said that he’d heard about a game called Quake Wars, and that it had a Linux-client. So I took a look at it, downloaded the demo, and now I’m hooked! Not as much as before, but it’s fun nonetheless. Anyway – playing the game with a 1680×1050 monitor resolution is INSANE! I can just about feel a grenade blowing up in my face. We’re about 3 people at work planning on making a clan, so we just need a few more to make it work. And I am definitely going to buy the full game tomorrow! For more information about Quake Wars, take a look at http://community.enemyterritory.com/.

Right, that was that about Quake Wars. Now to my next subject – a nifty little program named switchscreen. A quote from the website:

switchscreen is a command-line utility that moves the X mouse cursor to a given point on a given screen. I wrote it because I could find no other program that can define both the mouse position and screen number.

In other words – you can use your keyboard to navigate between your two monitors instead of your mouse! I find it to be a wicked program that I just had to mention. ;)

Update: I forgot to mention yesterday (as I’m typing it’s the 29th) that I nearly got bald and (even more) nuts by not being able to find the “x-devel-” package for SuSe, being that we need libx.h to make switchscreen work. Just fire up YaST and search for xorg-x11-devel, and there you go!