Monthly Archives: August 2009

Linux DVD Mounting

And sometimes it is the little things that make me batty. I haven’t been able to play back DVDs on my main computer for awhile now because… there was no “dvd” or “dvd#” directory under “/media”.

After “cd /media; sudo mkdir dvd0” suddenly DVDs that wouldn’t load now do.

Yes, this is where I say “Arg!” and shake my fist.


Bonded Networking

Sometimes things are exactly as easy as they appear to be, and sometimes moreso.

I just followed this guide and now have bonded networking.  In theory, this means I have a 200Mbps connection to my network now.

Since I don’t like it when others point to a webpage and say that all they did was what was written, I’ll be more specific.

  1. I did nothing to my switch/router
  2. I installed ifenslave per the directions
  3. I took down my ethernet connections per the directions
  4. I copyed my /etc/network/interfaces file to a backup
  5. I edited the /etc/network/interfaces file to have the bond0 connection in it  (Ha!  This font makes that look like Bond-O — as in the car-body repair goop; it should be bond[zero])
  6. I brought the bond0 interface up
  7. hooray!

I think it took me longer to type this than to actually do it.

Update:  There was one catch.  My /etc/resolv.conf file ended up blank this morning (i.e., after rebooting).  I find this  a little odd, but I was easily able to fix it by adding the entries back into it.  I now have that backed up so I don’t have to reference my router for that information.


KDE 4.3 Upgrade

I took the plunge this past weekend and upgraded.  Several bugs I filed — ultimately only was a “me too” — have been fixed.  The login screen is now an annoying sky-blue color, so I need to combat the kdm greeter again to get it to let me theme it (usually means editing a text file).

I also updated a VM and have been trying to compile Amarok 2.1.1 from source.  I will then try and compile the source from gitorious (a git-hub source control system) to see if another bug has been fixed.  There is one major outstanding issue with it that needs fixing, and then I might be convinced to move to it:  they desperately need an equalizer.

Somewhere amidst all of this, I finally tried KDE’s remote desktop again (KRDC).  My biggest complaint with it has finally been fixed:  they pass through the control keys.  As I type this, I think they may have fixed that some time ago, but it reminds me that KDE has a viable remote desktop application!  (The more I muse, I think I am thinking of NoMachine’s NXClient which doesn’t pass through things like alt+tab — very annoying…).

As I sit here writing this, my Windows laptop is hung, and I need to find a way to cleanly exit programs without simply killing them or hard-booting.  I don’t intend the aggravated bias, but I never have this problem with Linux… seriously.


Microsoft and XML Patents

This article is kind of troubling.  It troubles me because they patented the concept of putting meta-tags in XML that map to inline style changes defined in a supplemental file.  I can understand patenting the supplemental file; I can understand patenting the mapping schema; but this is patenting a concept that seems, at least on the surface, very generic in nature.

i4i LP is only targetting Microsoft at this point, but they also clearly state that the ODF 1.2 specification violates their patent.  It would be a shame is this got in the way of the innovation coming out of the OpenOffice.org project.  Even Microsoft is hopping on board to support ODF in their next service pack of Office 2007.  Believe it or not, I disagree with this law suit; their narrow focus of Microsoft makes this seem personal against Microsoft and not about the general concept.  It also took them 2 years to find this?  I hope a victory can be scored for freedom of innovation here.


UNIX find grep

I am always hunting for this, and so I’m going to put it here so I can remember!

This command is great:  find . -exec grep -l hello {} \;

Essentially, it does this:

  1. find all files starting in the current directory (“.”)
  2. for each file found execute “grep -l hello”
  3. grep -l will print file names — with full relative path — that match the grep criteria

This is great, as a programmer, to try and figure out which file had a certain word (or phrase, or Regular Expression pattern) in it.

There are also a couple of other pages with a large set of references here and here.


Static IP and VMware Workstation

So my static IP fixed my issues with VMware Workstation. I decided I’d finally post about it on their forum to see if that would motivate them into fixing the issue.  Ultimately, I am very curious why workstation isn’t working with DHCP under KDE and this Linux kernel, but it works fine with DHCP under Windows.

Rats… one good thing to say about Windows.  ;^)


Static IP Configuration

I finally figured out how to get my static IP addresses set through the system configuration files.  I had to resort to this because KDE4 doesn’t have the nice networking interface that KDE3 did — they are still working on that.

There are two key files that come into play:  (1) /etc/resolv.conf and (2) /etc/network/interfaces.

/etc/resolv.conf

me@machine:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain home
search home
nameserver 71.243.0.12
nameserver 66.237.161.12
nameserver x.x.x.1

This file is pretty simple.  It is the list of domain name servers that help resolve things like http://www.cnn.com into an IP address.  I had to find these values from my router, and thankfully it was picking them up automatically from my new ISP.  I also added my router (x.x.x.1) to the file so it would resolve the names of the machines locally on my network.  I still need to use {machine-name}.local as the syntax, but it works (e.g., ping machine.local).

/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 120.30.90.140
netmask 255.255.255.0
network 120.30.90.0
broadcast 120.30.90.255
gateway 120.30.90.1

auto eth1
iface eth1 inet static
address 120.30.90.141
netmask 255.255.255.0
network 120.30.90.0
broadcast 120.30.90.255
gateway 120.30.90.1

This file was trickier.  It started out like this:

me@machine:~/junk/config-files/etc/network$ more interfaces-20090809-1
auto lo
iface lo inet loopback

That’s not a lot of information to work with, so a fair amount of searching was required to figure out how to get what I wanted.  All of that information is pretty simple, and helped me understand how some of this works. I don’t think I really need to use the “network” and “broadcast” attributes, but I chose to mostly out of a copy-and-paste coincidence

The final step was a reboot, because just restarting networking didn’t work (sudo /etc/init.d/networking restart).  There must be something cached that needs to be flushed to get this to work while the machine is running.  Something else for me to noodle out another day.

While this was fun for curiosity, the primary motivation for doing this was to hopefully fix my VMware networking problem. I’ll have to test that out later tonight or early tomorrow.