The first task was to build the UFS kernel module, as my kernel did not have UFS support built-in, nor did my install have the UFS kernel module available. Already, having installed the proper kernel-devel RPM a while back, I did the following:

$ uname -r
2.6.9-34.0.2.ELsmp
$ rpm -qa | grep kernel-devel
kernel-devel-2.6.9-34.0.2.EL
$ cd ~/rpm/BUILD/kernel-2.6.9/linux-2.6.9
$ make menuconfig
$ make modules
$ make modules_install
$ depmod
$ sudo modprobe ufs

At this point, I had built the UFS kernel module and loaded it. Now it was time to mount the filesystems.

$ sudo mkdir /mnt/hdc1 /mnt/hdd1
$ sudo mount -t ufs -o ufstype=44bsd,ro /dev/hdc1 /mnt/hdc1
$ sudo mount -t ufs -o ufstype=44bsd,ro /dev/hdd1 /mnt/hdd1

That’s it! I now had read-only access to my two UFS partitions. Now I have to look through these files and see what’s worth keeping.

Warning: no scancode found for keysym 310

Strange, since xev sees the keypress just fine:

KeyPress event, serial 24, synthetic NO, window 0x1000001,
    root 0x57, subw 0x0, time 411185488, (11,-16), root:(31,48),
    state 0x0, keycode 66 (keysym 0xffe7, Meta_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

I don’t know why the keysym reported by qemu doesn’t match the keysym reported by xev. I’m guessing that it has something to do with the fact that qemu uses SDL, which probably has its own keymap routines, that are apart from the X11 routines.

Technorati tags: linux, qemu, virtualization, rhel

Binary packages:

• qemu-0.8.2-1.1.el4.marc.i386.rpm
• qemu-debuginfo-0.8.2-1.1.el4.marc.i386.rpm

Source package:

• qemu-0.8.2-1.1.el4.marc.src.rpm

Public key for checking signatures:

• rpm-gpg-key.asc

Technorati tags: linux, qemu, virtualization, rhel

Technorati tags: linux, rpm, redhat, usermodelinux

NX> 700 WARNING: Error when trying to connect to NX server, error is:
NX> 700 WARNING: NX> 203 NXSSH running with pid: 28823^M
Bad owner or permissions on /home/marca/.ssh/config^M.
NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation:
NX> 700 WARNING: the current system or NX configuration could be broken.

I tried chmodding ~/.ssh and ~/.ssh/config to be more and less restrictive and could not get the message to go away. What does work however is if I temporarily rename my config file to _config, install NX, and then rename it back.

Hopefully, NoMachine will add this to their FAQs and perhaps see if there’s a bug in the install that should be fixed.

NX is great though. You should definitely check it out if you’re into remote administration and using something like VNC, RDP, or remote X11, which are much slower than NX.

sudo /etc/init.d/courier-authlib start

Bam. Then things started working. Duh.

I also had to do two small tweaks to my .fetchmailrc – basically formail and procmail are now in /usr/bin instead of /usr/local/bin.

It’s been quite a pain as I used my FreeBSD box as an IMAP server, using courier-imap, and now I have to build courier-imap for RHEL, as it doesn’t seem to be supported by Red Hat.

This is supposed to be easy – supposedly you can just download the .tar.bz2 file and then run rpmbuild -ta on it. However, this led to a few hours of resolving dependencies, fixing the completely broken gcc and g++ that came with my image, and trying to figure out how our in-house packaging tool interacts with rpm, yum, up2date, and a bazillion scattered files and directories. I also had a few diversions where I looked into getting yum and apt-get going, with the latter now seemingly working with one repository (ATrpms), but I’m afraid to use it.

I wish I could use something like Ubuntu for my desktop machine. RHEL doesn’t have the best selection of packages and I prefer apt over rpm. Hopefully, I’ll get more comfortable with it over time, but right now I’m really wishing that I had Ubuntu or Debian or Gentoo.

And now that I’ve mentioned Gentoo, I know that I’m going to get a great rant from Chris on RHEL suckage…