In udev rules, the %k, %b, %n variables are nice and all, but you can also use the variables you’re comparing and setting such as ID_FS_TYPE, KERNEL, SUBSYSTEM, PHYSDEVPATH, etc. When you run a command in a udev rule, there’s nothing stopping you from calling a shell and executing a few commands without actually calling a standalone script to do the dirty work. If you write out the array of environment variables from inside an external program, you can get a better understanding of just which part of the device discovery is matching your rule and getting processed.

#!/usr/bin/perl -w
# For each tab (worksheet) in a file (workbook),
# spit out columns separated by “,”,
# and rows separated by c/r.
use Spreadsheet::ParseExcel;
use strict;
my $filename = shift || “Book1.xls”;
my $e = new Spreadsheet::ParseExcel;
my $eBook = $e->Parse($filename);
my $sheets = $eBook->{SheetCount};
my ($eSheet, $sheetName);
foreach my $sheet (0 .. $sheets - 1) {
…

This howto will get bugzilla with ALL of the optional modules installed on Fedora 10. If you just want a barebones bugzilla up and running, you might want to read the whole thing and then just look for the required parts. Otherwise, you can follow me through the install and end up with all the bells and whistles.

The checksetup.pl script will tell you what you’re missing and what you need to install to get bugzilla up and running. But the problem is it pushes you to use perl’s package management to build the perl modules which may or may not work. I think it’s best to use YUM to install and manage all of your packages and not to mix and match both. This will help to avoid conflicting packages and seemingly random complaints of a package missing when it’s not.

Here’s a bunch of ways to get the ip addresses for all your network interfaces using ifconfig.