Given the “end of IPv4″ I decided I shouldset up IPv6 on my network and see if I can’t start doing things over that instead. Unfortunately, however, it appears that my DNS server internal to my network, maradns, sucks at IPv6 until version 2.0. Fedora has it at 1.3.something. Debian has it at 1.4. WTF Fedora?

I’ve been working on building MaraDNS 2.0 RPMs for Fedora 13 and 14, but I don’t know the RPM SPEC structure very well. The 2.0 version of MaraDNS has separated the authoritative resolver from the recursive resolver, which is wise. But it means I need to build a spec file that produces two RPMs. I suppose I could build a separate spec file for each one, but that doesn’t seem like the right way to do things.

 

There was a lot of buzz on the interblags about a 200-line kernel patch that enables per-tty cgroups automatically. Apparently, one can add them trivially to their home directory without having to patch any kernels.

This blog post talks about how to do it, but it didn’t cooperate with Fedora 14 very well. A bit of googleing later and I found this mailing list post that did it for me. Now I have userspace cgroups for each terminal I open. Handy, I suppose. Might be more useful on an SSH server to guarantee that each person logging in can’t overwhelm the system for the others.

 

To be fair, it’s not Fedora 14 that’s at fault. The 2.6.35 kernel has a regression in the e1000e driver for some Ethernet adaptors.

It was quite tricky to figure out, especially right after 14 came out, as I didn’t have an ethernet connection, and when I was able to get the connection up, and I asked on the IRC channel, no one had any insight. I let 14 stew a while, and the rest of the internet came up with similar problems. Turns out that the kernel driver included in 2.6.35 has issues. There’s some patches in the works, but I don’t know if they’ll get pulled down into 2.6.35. The fix is in 2.6.36.

Until then, you can get the latest driver directly from the e1000e’s SourceForge website here. Make, then make install it as root and you’ll be good to go. This driver version worked for me on a Intel Corporation 82566DC Gigabit Network Connection (rev 02).

 

Hooray for Logwatch.

It appears that someone['s botnet] was trying to hack my little server yesterday. I have a good portion of attempted logins as root from a slew of hosts. 194 separate hosts with multiple attempts from more than a few. This might explain the horrible internet connectivity problems I was having the other day.

Not really sure what I did to piss off some script kiddie. Perhaps I got someone’s attention? I haven’t blagged about anything controversial recently. Not even in politics. I did submit my resume to Monster.com, perhaps someone is determining if they can hire me as a Systems Administrator?

Logwatch entries follow after the break.

Continue reading »

 

Was harder than it should’ve been. I got annoyed.

You need to install openssl-devel, zlib-devel, bison, gcc, make, patch, tar, and maybe gcc-c++ (although I don’t think this one is needed).

Go get the latest ruby 1.9 source, as of this writing 1.9-p378, and extract it somewhere. Then go get the patches on this bug, at the specific comment. You will need to apply at least the openssl-build-fix patch, since fedora uses openssl 1.0 and it’s not yet into ruby 1.9. Then follow your typical ./cofnigure, make, and make install stuff. I installed mine into a prefix of /opt/ruby so that it wouldn’t affect any fedora ruby stuff that it might want. I then added ruby’s path to the end of my user’s PATH variable.

That’ll get you a working ruby 1.9 in Fedora.

© 2011 Shlrm.org Blag Suffusion theme by Sayontan Sinha