Building a statically linked rsync

Install dependencies for building:

yum -y install glibc-static popt-devel popt-static

Download, then build:

tar xf rsync-3.0.9.tar.gz
cd rsync-3.0.9
./configure
make CFLAGS="-static" EXEEXT="-3.0.9-static"
strip rsync-3.0.9-static

That's what I needed to do on RHEL7. YMMV.

What packages require a given package?

How do you determine what packages require a given package?

repoquery --tree-whatrequires <package>

For example, let's say you want to find out what packages depend on rdma:

$ repoquery --tree-whatrequires rdma
rdma-1.0-14.el6.noarch [cmd line]
\_ opensm-3.3.9-1.el6.x86_64 [1: rdma = 1.0-14.el6]
$

There you have it... opensm is the only package that requires rdma.

Source: Stack Overflow

The Philosophy of Monitoring

This is a really good one too...

The Philosophy of Monitoring | League of Professional System Administrators

Cargo Cult System Administration

Great post that I had to share...

Cargo Cult System Administration

RHEL5 Interactive Startup Without Pressing "i"

This was not easy information to come by, but once I dug through RHEL5's /etc/rc.sysinit it was obvious. Instead of pressing "i" when prompted for an interactive startup (ie, asking if you want to start each service), you can add "confirm" to the kernel command line in GRUB.

Changing File Permissions

Maybe I missed the memo on this feature of chmod(1), but I really dig it.

chmod o=g foo

That sets the "other" permissions to whatever the "group" permissions are. Combine that with "-R" and you can quickly adjust the "other" permissions of a whole tree to be the same as the file/dir "group" permissions.

Of course, care should be taken so as to not grant everyone write permissions. :)

Debian pushes development of kFreeBSD port

Woohoo!!! I'll definitely be playing testing this out...

http://www.debian.org/News/2009/20091007