It took a little effort to get this done because Fedora Core 3 is not a supported version of Linux for Domino according to IBM. I suspect others may see similar problems in other Linux distributions so let me document what I did other than the normal install stuff.

Keep in mind, you should never run Domino on an unusupported operating system just because I'm showing you how I did it. If you care about the stability of your server, you should always use whatever IBM tells you to use for a server. I'm a risk taker by nature I guess. You wouldn't follow me into a burning building, would you?

I should note -- the server came up and ran correctly in almost all respects. What breaks is the built in JVM. Here's the error it generates when you try:

HTTP JVM: java.lang.UnsatisfiedLinkError: /opt/ibm/lotus/notes/70000/linux/jvm/bin/libawt.so: libXmu.so.6: cannot open shared object file: No such file or directory

After wasting rediculous amounts of time trying to find the issues with epoll() and libevent() which are supposed to be the big problems, I installed libevent-1.1a-2.fc3.i386.rpm -- to be honest, I doubt it was needed. I'm putting the information here because I did install it and I'm not 100% sure that it isn't required.

More important, I went looking for libXmu.so.6 I found it. In my case, I found a copy in /usr/X11R6/lib. The file /usr/X11R6/lib/libXmu.so.6 was a link to /usr/X11R6/lib/libXmu.so.6.2 so I just created the same link in the /opt/bin/lotus/notes/7000/jvm/bin directory.

After that, I restartd HTTP (it wasn't necessary to restart Domino), and the error changed slightly. It became this one:

HTTP JVM: java.lang.UnsatisfiedLinkError: /opt/ibm/lotus/notes/70000/linux/jvm/bin/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory

A small difference, but key. It told me two things. First, that at least it was seeing the first file link I made. Second, that this could be a long day if there were a lot of them missing. Fortunately, there weren't. My Fedora Core 3 box from ServerBeach didn't have a copy of libXp.so.6 on it, but my Fedora Core 4 box at home did. I just copied the missing library into the jvm where I made the other link, and again restarted Domino.

No more problems.