Tag Archives: devops

Missing man pages on CentOS, or reason № INT_OVERFLOW why I hate CentOS/RHEL sofa king much.

I can’t remember all of find’s arcane incantations. Nobody can.

$ man find
No manual entry for find

wat. find is clearly installed, of course. man pages? nope.

Search search search. Searchity search. Horrible relevancy because what are you gonna get when you think you’re smart, do rpm -ql findutils and note that /usr/share/man/man1/find.1.gz doesn’t exist, and then start searching for how to find packages with missing files using Red Hat’s primitive yum and rpm commands.

It was only when I gave up and searched on “centos missing man pages” that I found the answer.

# yum install man-pages

Yes, seriously.

$ cat /etc/redhat-release
CentOS release 6.5 (Final)

Released 1 December 2013. So I guess I can’t ask what fucking year it is.

Installing the Heroku Toolbelt on a PowerPC Mac running OS X

So you’re still using a PowerPC Mac, and you need to deploy some stuff on Heroku. (Yes, that combination of traits exists, I’m living proof.) Tigerbrew is a lovely PowerPC port of Homebrew for OS X (and it mostly works on Leopard, despite the name). PPC holdouts cannot thank Misty De Meo enough for all her work on it, but as of this writing, heroku-toolbelt doesn’t work out of the box.

Actually, because of this writing and because of Misty De Meo’s awesome bug-squashing prowess, this now does work out of the box, and automatically compiles the necessary version of Ruby for you as well; be prepared for a long wait while it builds, at least on slower Macs, but it works!

Here’s how to install heroku-toolbelt on your old PPC Mac running OS X 10.4 or 10.5.  You will need to be comfortable with the terminal, of course.

The build infrastructure

This post assumes that you are familiar with Homebrew and that you can get Tigerbrew installed on your Mac on your own.  It’s not too bad.

Install heroku-toolbelt

$ brew update     # do not skip this esp in Tigerbrew
$ brew install heroku-toolbelt

Sweet, after like 2 hours on a 1.25GHz G4, we’re done!  Run heroku and make sure that it prints some useful output, and not the following.

$ heroku
-bash: /usr/local/heroku/bin/heroku: /usr/local/heroku/ruby/bin/ruby: bad interpreter: Bad CPU type in executable

If the above does happen, you may have a rogue installation of heroku.  Do a which heroku, find it, and delicately delete it, then try again.

Organizing institutional knowledge is high-value work. Neglect it at your peril.

I’m quite the wiki enthusiast.  I was an early editor on Wikipedia; I created several articles on really common topics, I got Featured Picture on a few photos I plucked from free sources, and so forth.  I’ve run my own wikis since 2005.  The biggest, at its prime, got a couple hundred thousand hits a month and had periods with 25-30 concurrent users; it was used by students in a classroom environment.

So, at my software development jobs, tending the wiki – or creating it, if it doesn’t yet exist – is a natural fit for me.

And at each job, I’ve heard comments which suggest that maintaining the wiki is low-value work, akin to picking vegetables or something.  Allow me to exercise that analogy a bit: people who pick vegetables feed all of us, and there are racist undertones to presuming that picking vegetables is low value work.

Here are a few paraphrased comments: Continue reading