AM DX'ing from Winnipeg

For about the past 30 years (this month) on and off I have been into AM DX'ing, which is the hobby of receiving non-local AM radio stations.

The first non-Winnipeg station I used to listen to was Newsradio 78 WBBM Chicago back in late Summer of 1978.

Some of the radios I have had access to have had good sensitivity, while others are just good for local reception.

This time around, I've created an OpenOffice spreadsheet that lists the station callsign, city,

Here's the spreadsheet in PDF format.

And another version, that I've created in MySQL:

mysql> select frequency, callsign, city, state, network from radio_receivable order by frequency;
+-----------+----------+--------------------+-------+------------------+
| frequency | callsign | city | state | network |
+-----------+----------+--------------------+-------+------------------+
| 540 | CBK | Watrous | SK | CBC Radio One |
| 610 | KDAL | Duluth | MN | CBS Radio |
| 660 | CFFR | Calgary | AB | CORUS |
| 680 | CJOB | Winnipeg | MB | CORUS |
| 700 | WLW | Cincinatti | OH | ABC Radio |
| 710 | KXMR | Bismark | ND | ESPN Radio |
| 720 | WGN | Chicago | IL | ABC Radio |
| 730 | CKDM | Dauphin | MB | Ind. |
| 740 | KVOX | Fargo | ND | Fox Sports Radio |
| 760 | WJR | Detroit | MI | ABC |
| 780 | WBBM | Chicago | IL | CBS Radio |
| 790 | KFGO | Fargo | ND | CBS Radio |
| 810 | CKJS | Winnipeg | MB | Ind. |
| 830 | WCCO | Minneapolis | MN | CBS Radio |
| 850 | KOA | Denver | CO | Fox News Radio |
| 860 | CJBC | Toronto | ON | Radio-Canada |
| 880 | CKLQ | Brandon | MB | Ind. |
| 920 | CFRY | Portage la Prairie | MB | Ind. |
| 950 | CFAM | Altona | MB | Ind. |
| 990 | CBW | Winnipeg | MB | CBC Radio One |
| 1050 | CKSB | St Boniface | MB | Radio-Canada |
| 1100 | KZFG | Fargo | ND | Fox News Radio |
| 1110 | KFAB | Omaha | NE | Fox News Radio |
| 1150 | CKOC | Hamilton | ON | Astral |
| 1200 | KFNW | West Fargo | ND | Ind. |
| 1250 | CHSM | Steinbach | MB | Ind. |
| 1290 | CFRW | Fort Garry | MB | CHUM |
| 1330 | WLOL | Minneapolis | MN | Relevant Radio |
| 1430 | CHKT | Toronto | ON | Ind. |
| 1500 | KSTP | St Paul | MN | ABC Radio |
| 1540 | KTGG | Spring Arbor | MI | Ind. |
| 1540 | KXEL | Cedar Rapids | IA | ABC Radio |
| 1550 | CBE | Windsor | ON | CBC Radio One |
| 1630 | KCJj | Iowa City | IA | Ind |
| 1670 | WTDY | Madison | WI | ABC Radio |
+-----------+----------+--------------------+-------+------------------+
35 rows in set (0.00 sec)

Turboprint for Linux

I just bought myself a neat little Linux printer driver, Turboprint.

It can display the amounts of ink left, and has the printer utility programs like cleaning the nozzles, aligning the print heads, printing a test page etc...

However, since I have the Fedora version of Linux installed I must deal with SELinux from time to time. The printer doesn't print from my non-root username. I get the following error in SELinux:

su -

and enter your password, then it prints just fine.

This is just a workaround until I find out how to fix this in SELinux. Apparently it works fine in Fedora 9, but 9 I've heard is kinda buggy... I'm waiting for 10 or 11.
Summary:

SELinux is preventing tpstdin (cupsd_t) "write" to ./print.log (var_log_t).

Detailed Description:

[SELinux is in permissive mode, the operation would have been denied but was
permitted due to permissive mode.]

SELinux is preventing tpstdin (cupsd_t) "write" to ./print.log (var_log_t). The
SELinux type var_log_t, is a generic type for all files in the directory and
very few processes (SELinux Domains) are allowed to write to this SELinux type.
This type of denial usual indicates a mislabeled file. By default a file created
in a directory has the gets the context of the parent directory, but SELinux
policy has rules about the creation of directories, that say if a process
running in one SELinux Domain (D1) creates a file in a directory with a
particular SELinux File Context (F1) the file gets a different File Context
(F2). The policy usually allows the SELinux Domain (D1) the ability to write,
unlink, and append on (F2). But if for some reason a file (./print.log) was
created with the wrong context, this domain will be denied. The usual solution
to this problem is to reset the file context on the target file, restorecon -v
'./print.log'. If the file context does not change from var_log_t, then this is
probably a bug in policy. Please file a bug report
(http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against the selinux-policy
package. If it does change, you can try your application again to see if it
works. The file context could have been mislabeled by editing the file or moving
the file from a different directory, if the file keeps getting mislabeled, check
the init scripts to see if they are doing something to mislabel the file.

Allowing Access:

You can attempt to fix file context by executing restorecon -v './print.log'

The following command will allow this access:

restorecon './print.log'

Additional Information: