2014/03/27

And now for something completely different : Dave Brubeck Quartet's Time Out album is currently on heavy play.  I know I'm late to the party.  In fact, I was born to late for this party.  But I really really digging the combination of mellow, swing and exotica on this album. 

2014/03/20

In short, people were installing WordPress badly (friends don't let friends use PHP).  They were allowing password authenticated ssh login over the internet.  They were doing chmod 0777 ~apache/html_docs.  They were doing other highly unsafe things. 

If you can't see the problem with these things, then you need to talk to a professional sysadmin. 

2014/03/18

Nothing is beyond me.  When it comes to computers, I am all conquering. 

That actually might be an exaggeration.  But I just pulled off a stunt that really impressed me. 

I'm moving all my systems from CentOS 5 to CentOS 6. ( Why so soon?  Shut up) In the process, I need to move my VMs from VMware Server 1 (Seriously?  Shut up) to KVM (libvirt specificly).  For the most part, I'm actually starting up whole new VMs and reconfiging them.  But I still might want to look at my old data, fetch old files, and what not.  This means being able to read VMware's vmdk files.  This is "easy":

First, you can't have multiple VGs with the same name active at once.  Work around is to only mount one at a time.  You can renamed VGs with vgrename but that's a job for another day. 

Next off, I chose to have my vmdk split into multiple 2GB files.  This makes copying them around so much more fun.  But qemu only understands monolithic files, so you need vmware-vdiskmanager to convert them.  Specificly

Lastly (and this is the main point of this post) CENTOS 6 DOESN'T SHIP WITH NBD!  After WTFing about as hard as I could, I googled around for one.  Someone must have needed nbd at some point, surely.  The only solution I found was to recompile the kernel from scratch.  Which is stupid.  As a work around, I used the kernel-lt from elrepo.  But the real solution would be a kmod.  I thought doing a kmod would be hard, so I set aside a few hours.  Turns out, it's really easy and I got it right on the first try. 

Edit nbd-kmod.spec.  You have to change kmod_name and the %changelog section.  You might also want to change kversion to your current kernel (uname -r).  If not, you need to add --define "kversion $(uname -r)" when running rpmbuild;

The hard part (of course) is that I wasn't sure what to put in nbd-0.0.tar.bz2.  The contents of jfs-0.0.tar.bz2 just look like the files from drivers/jfs in the kernel tree with Kconfig and Makefile added on.  So I pull down the kernel SRPM, did a rpmbuild -bp on that (just commend out all the BuildRequires that give you grief.  You aren't doing a full build.)  Then I poked around for nbd in ~/rpmbuild/BUILD/vanilla-2.6.32-431.5.1.el6/. Turns out there's only nbd.c and nbd.h.  So that goes in the pot.  I copied over the Makefile from jfs, modifying it slightly because jfs is spread over multiple source files.  Kconfig looked like kernel configuration vars.  I just copied BLK_DEV_NBD out of vanilla-2.6.32-431.5.1.el6/drivers/block/Kconfig. 

This entire process took roughly 1 hours.  It worked on the first try.  Of course, all the magic is in kmodtool-nbd-el6.sh.  But I was expecting a lot of pain.  Instead it worked on the first try.  I was so surprised I did modprobe -r nbd ; ls -l /dev/nbd* just to make sure I wasn't getting a false positive. 

The second to last command will open a browser to get an OAuth token.  This means you need htmlview and a valid DISPLAY.  The token is only good for 30 days.  This is something that needs to be better automated. 

2014/03/12

I was working on a CentOS 6 install for work and figured "hey, I should upgrade Mustang to the latest version."  Normally this means

yum upgrade
shutdown -r now

Of course that didn't work; Mustang has an APU and uses a proprietary driver from AMD for X.org.  I pretty much never use Mustang's console so I didn't notice this for 2 days, when my wife complained about not being able to watch Lost. 

After much futzing, I find the error message: symbol lookup error: /usr/lib64/xorg/modules/drivers/fglrx_drv.so: undefined symbol: GlxInitVisuals2D. This means AMD's driver is doing something stupid.  I of course can't compile it nor fix it.  I tried to download the latest driver, but that refused to install.  Curse swear, google google and then I found it. 

First line installs ELRepo, which you might already have.  Second line removes the previous drivers, which conflict with the new ones.  The --nodeps is because Adobe really wants OpenGL installed.  Third line is the important one, it installs the new drivers and does all the magic to get them working.  Yes, the X.org driver needs to install a kernel module.  Last line just makes sure that Xorg.conf is set up properly.  I'd been playing around in it to try to get it to work. 

About Me

I am a self-employed programmer.  I program computers for a living.  This also means I spend half my time as a sysadmin.  The annoying half.  I work nearly exclusively with Linux and Perl. 
All this goes to say that NO, I WILL NOT HELP YOU FIX YOUR COMPUTER.