Uncategorized

locate (slocate) on openSUSE

The Beagle indexing program doesn’t find things outside my home directory. I was looking for good old locate, but it’s not there. This SUSE Forums thread had the answer–it’s in the findutils-locate package.

Uncategorized

Comments (0)

Permalink

openSUSE Setup

Start with ThinkWiki for basic installation and TrackPoint setup.

Next is Multimedia setup. After setting up the distribution software sources, Install mplayer and acroread with Yast.

Things will look a little nicer if you set up TrueType fonts.

Uncategorized

Comments (0)

Permalink

Fluxbox Windows Key

I have some keyboard shortcuts set up in Fluxbox to use the Windows key. For instance <Win>+x opens an xterm. This stopped working recently (probably after the upgrade to FC6). I found the answer was the keyboard selected by Xorg. Commenting out the line Option "XkbModel" "pc105" re-enabled the Windows key (Mod4).

Uncategorized

Comments (0)

Permalink

Repartitioning

On Pinto, the ThinkPad T60, I needed to make room to try openSUSE (hibernation supposedly works better than on Fedora). The first step is to start up QTParted. On selecting the disk, QTParted reports Error: File system has an incompatible feature enabled. Resize and move commands were disabled for the ext3 partitions.

I found instructions that supposedly fix this:
umount /dev/xxx
tune2fs -O^dir_index /dev/xxx
parted
tune2fs -O dir_index /dev/xxx

But they didn’t.

From Bugzilla:

Currently the _only_ tool that can resize ext3 filesystems is resize2fs available in e2fsprogs. While annoying, you can use resize2fs to resize the filesystem and then use fdisk or parted to resize the partition boundary to match the new filesystem size. With parted 2.0, we’ll be able to do this in one step.

resize2fs -p /dev/sda6 7500M (resize2fs won’t take fractional units like 7.5G) will work, then you have to delete and recreating the partition to the correct size. This got a little tedious, so I started my GParted Live CD version 0.2.5, though the latest is 0.3.3. It was able to resize the partitions. I shrunk my two 14 GB Fedora Core 5 and 6 partitions to 10 GB each and consolidated some unused space to make room for a new 10 GB partition. Some important tips:

  • You can’t move the start of an ext filesystem partition, but you can shrink and grow it. Shrinking a parition as small as it can go can give you enough room to copy and paste it to unallocated space, then delete the original. Using this “Tower of Hanoi” technique, you can effectively move partitions if you have enough space.
  • Creating and deleting a partition changes its device name, e.g., /dev/sda6 becomes /dev/sda7. If you aren’t using disk labels in GRUB (/boot/grub/grub.conf), your system won’t boot. Either use disk labels (see the tune2fs man page for the -L option) or update your grub.conf after you move the partitions.


Uncategorized

Comments (0)

Permalink

Sound on Upgraded Fedora Core 6

Most everything is working on my Fedora Core 6 upgrade. MPEG sound doesn’t however. Running a test video shows the picture, but sound is a distorted white noise. Thinking I might have some cruft left over from the prior installation, I loaded a fresh copy of Fedora Core 6 to see if it worked:

  • Create new partition of 10 GB (it could be smaller, but I have the space :-))
  • Install Fedora Core 6 on it, being careful to not take the default of “wipe everything out and install” and not installing the boot loader
  • After the installation, boot back into my existing FC6 upgrade
  • Add the new installation to /boot/grub/grub.conf:
    title Fedora Core 6 clean (2.6.18-1.2798.fc6)
    root (hd1,9)
    kernel /boot/vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/hdb10
    initrd /boot/initrd-2.6.18-1.2798.fc6.img
  • Boot the fresh copy of FC6
  • Install the media packages from Fedora Core 6 Tips and Tricks.

The test video was fine, so I knew there wasn’t a problem with FC6 and my hardware. Next, find out what:

  • Save a copy of rpm -qa | sort
  • Save a copy of /sbin/lsmod
  • Boot back to the FC6 upgrade
  • Compare the RPM lists

Immediately (well, it was at the top of the list) I saw that the upgrade had a52dec-0.7.4-8.fc6 and the clean install had a52dec-0.7.4-10.lvn6. I ran yum remove a52dec and 15 packages went with it. At that point, I started with the Tips and Tricks instructions to replace all the media packages.

One problem during the MP3 plugin step was the dependency of xmms-faad on faad2. This was solved with
yum remove faad2
yum install --enablerepo=livna --disablerepo=freshrpms faad2
The key is to get the package that ends in “lvn6”.

The rest went pretty smoothly and now mplayer sounds fine again!

Uncategorized

Comments (0)

Permalink

Thinkpad T60 Upgrade to Fedora Core 6

Upgraded as below (see FC4 upgrade). After upgrade, manually ran yum update for all *fc5 and *lvn5 RPMs.

The 586 kernel was installed rather than the 686. A Redhat bug explains this. The 686 kernel is needed for the Intel wireless drivers as mentioned in the Fedora Core 6 on a ThinkPad T60 wiki. Here’s what I did (based on the discussion in the Bugzilla forum).

Save a copy of /boot/grub/grub.conf
yum remove kernel kernel-devel
yum install kernel.i686 kernel-devel.i686

There’s grubby error about not finding a suitable template. We’ll fix that later
yum install gnome-session gnome-volume-manager pcmciautils systemtap
(The last command is a list of the depencies removed in step 1)

Edit grub.conf and make an entry for the new kernel. I copied over my saved grub.conf and updated the version numbers for the new FC6 kernel. You might also need to update the default (zero-based) to select your new 686 kernel.

reboot

yum update and proceed with the wiki instructions. Don’t forget to remove the old wireless script in /etc/init.d:
chkconfig --levels 23456 wireless off
chmod -x /etc/init.d/wireless

Uncategorized

Comments (0)

Permalink

Upgrade to Fedora Core 6

Start with a copy of the current Fedora Core 4 system and upgrade the copy to Fedora Core 6. (These steps are easiest to do with a Knoppix live CD because none of the partitions will be in use.)

Old Fedora Core 4 Layout
Partition Label Size
/dev/hda1 boot 100MB
/dev/hdb8 fc4root2 10GB
/dev/hdb9 fc4home2 5GB

Create new partitions using QTParted:

New Fedora Core 6 Layout
Partition Label Size
/dev/hda6 fc6root 15GB
/dev/hda7 fc6home 10GB

Boot is left alone. Note the new partions are larger, so after we copy the old partition’s data to the new one, the file system will have to be resized.


# dd if=/dev/hdb8 of=/dev/hda6 bs=1024k
# tune2fs -L fc6root /dev/hda6
# resize2fs /dev/hda6
# dd if=/dev/hdb9 of=/dev/hda7 bs=1024k
# tune2fs -L fc6home /dev/hda7
# resize2fs /dev/hda7
# cd /mnt
# mkdir fc6root
# mount /dev/hda6 /mnt/fc6root

Edit /boot/grub.conf. Copy current “FC4” entry to “Test FC6” and change “root” on kernel line to point to new /dev/hda6.
Edit /mnt/fc6root/etc/fstab and change / and home to point to new partitions /dev/hda6 and /dev/hda7, respectively.

Reboot and check out Test FC6 before running the Zod (Fedora Core 6) upgrade.

Well, there’s something I overlooked. The boot partition is shared so I can run the same Grub with different versions of the OS. However, when Fedora upgrades the new FC6 partition, it has RPM remove the old versions of the kernel from /boot, which disables the old FC4 installation. I suppose the best way to handle this is to make backup copies of what’s in /boot before starting the upgrade. After the upgrade, boot into FC6 and restore the kernel(s) for the old installation and make sure the old installation still works.

Uncategorized

Comments (0)

Permalink

Recovering from the Windows Virus

I had to replace a dying hard disk. This was as easy as connecting the old (still set up as master) and new (jumpered to be slave) drives and booting Knoppix. At the command line:
# dd if=/dev/hda of=/dev/hdb

When it’s done, shut down, remove the old drive and make the new one the master. Then everybody was happy. But not really. I’m not sure if the dying drive barfed while copying part of the Windows partition or what, but WinXP failed to start complaining that <Windows root>\system32\hal.dll was corrupt. So I reloaded Windows and it wiped GRUB off the disk. This is fixed by booting Knoppix again and entering these steps (which are specific to my configuration of /boot as the first partition of my boot drive) from HOWTO Restore GRUB:
# grub
grub> root (hda0,0)
grub> setup (hd0)
grub> quit
# reboot

Uncategorized

Comments (0)

Permalink

ISA Modem on Mothball

Install old ISA modem in Mothball (Dell XP600?)
/var/log/messages:
Nov 18 17:54:25 mothball kernel: isapnp: Scanning for PnP cards…
Nov 18 17:54:25 mothball kernel: isapnp: Card ‘CPI ViVa CommCenter/SP 33.6’
Nov 18 17:54:25 mothball kernel: isapnp: 1 Plug & Play card detected total
Nov 18 20:04:02 mothball kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Nov 18 20:04:02 mothball kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Nov 18 20:04:02 mothball kernel: 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

Removing modem removes isapnp Card ‘CPI ViVa CommCenter/SP 33.6’, but not ttyS0. Modem isn’t registered with tty.

setserial -v /dev/ttyS0 autoconfig
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4

No ISAPNP support on serial driver?
From http://www.mjmwired.net/resources/mjm-fedora-fc5.html
$ yum install yum-utils
$ yumdownloader –source kernel –enablerepo core-source –enablerepo updates-source
$ rpm -ivh kernel-2.6.15-1.1955_FC5.src.rpm
$ rpmbuild -bp –target=$(uname -m) /usr/src/redhat/SPECS/kernel-2.6.spec
cd /usr/src/redhat/BUILD/kernel-2.6.15/linux-2.6.15.ARCH/

From http://www.mjmwired.net/resources/mjm-kernel-fc4.html
Get kernel source and turn on CONFIG_PNP_DEBUG CONFIG_PNPBIOS and CONFIG_PNPBIOS_PROC_FS

Uncategorized

Comments (0)

Permalink

Remote Backup Using SSH and TAR

I have one of those three-year free trial hosting accounts from 1&1. It’s coming due at the end of the year and their documents say upgrading the account (that is, actually paying for it) requires the site be backed up and restored to a new account. It’s annoying, but whether I do this or move to another host, the backup needs to be made just the same. I have been backing it up manually by logging in to the account and making a TAR of the site, then transferring it to my local computer with FTP. The problem is, the site has a 500MB limit and I’m using 400MB of it, so there isn’t room for the files and a compressed TAR backup. SSH to the rescue! I’ve found lots of sites that show you how to back up using SSH and TAR this way:
home$ ssh user@example.com
user@example.com's password:
example$ tar zcf - . | ssh user@home-machine.net "cat > example.tgz"

If you can’t SSH to your local machine, you can do it this way:
home$ (ssh user@example.com tar czf - .) > example.tgz
user@example.com's password:

The restore command is:
home$ cat example.tgz | (ssh user@example.com tar xzf -)
user@example.com's password:

or to restore to a different location:
home$ cat example.tgz | (ssh user@example.com "cd temp; tar xzf -")
user@example.com's password:

Uncategorized

Comments (0)

Permalink