KerbyServer

I recently found a useful tool for cleaning up unneeded RPMs and finding problems in the RPM database of installed packages. Just install yum-utils and then you can use the package-cleanup command with its various options.

With openvpn already installed via yum:

su -
cp -a /usr/share/openvpn/easy-rsa /etc/openvpn/
cd /etc/openvpn/easy-rsa/2.0
vim vars

Edit the following:
export KEY_COUNTRY="US"
export KEY_PROVINCE="VA"
export KEY_CITY="Chesapeake"
export KEY_ORG="KerbyServer"
export KEY_EMAIL="admin@kerbyserver.net"

Save the file, and more commands:

./vars
source vars
./clean-all
./build-ca
./build-key-server server

Go with all the default entries.

./build-key kerbspb

Again, go with the defaults.

./build-dh

Steps used to setup an OpenLDAP server on KerbsFedora (based on walkthrough at http://www.linux.com/articles/114010 ):

sudo yum install openldap-servers openldap-clients

Generate the admin user's password (enter it twice when asked):
/usr/sbin/slappasswd

Edit /etc/openldap/slapd.conf:
(most comments trimmed)
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema

As much as I love Fedora, occasionally I find myself wishing it would do a certain thing like Debian or Ubuntu. A while ago, I posted a way to sort the ps command like Debian in Fedora. This time, I found out how to transplant another of Debian's defaults to Fedora.

Since I keep having to refer to the BackupPC FAQ for these steps, here is a concise list of steps to configure ssh keys on the client and server BackupPC systems:

On the client:
Log in as root
Generate the ssh key (remember to NOT set a password):
ssh-keygen -t rsa
touch ~/.ssh/authorized_keys2
Edit ~/.ssh/authorized_keys2 and add the BackupPC public key.
Pre-pend the key with from="kerbsfedora.kerbyserver.net" to restrict access.

On the BackupPC server:
Log in as backuppc

I just upgraded my Ubuntu MythTV system from Edgy to Feisty. The MythTV components seem to work fine, but the video out on the ATI card and the remote control do not work properly.

It should be somewhat straightforward to get this system running properly again. I'll try to document the steps here for posterity...

UPDATE:

ATI TV Output Instructions

I have been holding back on doing a kernel upgrade for some time on my Ubuntu system that runs a MythTV front and back end. To the best of my knowledge :) I have a patched ATI driver, Hauppauge itv driver, and possibly lirc that were compiled against the current kernel. I have a hunch that I replaced the compiled lirc with a proper package install during the edgy upgrade, but I'm not sure.

I performed a full backup of the system with backuppc and am going ahead with the installation of:

When using ps with Ubuntu and Debian, the output is organized by the start time of the process. On Fedora, the output defaults to sorting by PID. This approach differs because PIDs eventually wrap around and no longer represent the processes in chronological order.

I finally found that the following ps command on Fedora systems will sort the same as Ubuntu/Debian:

ps -e --sort=start_time


Well, this little gem just wasted several hours of my life. For future reference, if a strange problem occurs that involves file or network access or modification, be sure to consider SELinux as the source of the issue.

With the recent upgrades to Fedora 7 I have done on several systems, I have become more aware of the terrible state of VNC clients on Mac OS X. The issue arose when I set up Remote Desktop (vino) preferences on the Fedora 7 systems. The VNC client on other Fedora 7 systems and the Tight VNC viewer on Windows have no problem connecting to Fedora 7's vino server. I have found that the VNC viewer in Fedora Core 6 and any VNC client on Mac OS X throw back an "Authentication failure" when connecting. After typing in the target computer's hostname, the password prompt appears as usual.