<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6271195465944621644</id><updated>2011-12-19T15:42:16.978-08:00</updated><category term='linux'/><category term='firefox'/><category term='printing'/><category term='javascript'/><category term='dns'/><category term='itunes autodelete auto delete'/><category term='browsers'/><category term='windows 7'/><title type='text'>Hoosier in Seattle</title><subtitle type='html'>Random bits of mostly technical stuff, usually from cases where no good search hits addressed the problem, and I feel the need to document the solution in a note to myself. I figure that if I blog it, then at least it'll be findable by others, too.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>25</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-2870544451803219828</id><published>2010-12-17T21:53:00.000-08:00</published><updated>2010-12-17T22:01:39.228-08:00</updated><title type='text'>ssh, socks, and selinux</title><content type='html'>Trying to use ssh's &lt;span style="font-family: courier new;"&gt;-D&lt;/span&gt; option to setup a SOCKS proxy and getting the error below?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family: courier new;"&gt;channel 3: open failed: administratively prohibited: open failed&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;If you are running SELinux (e.g. Fedora), you need to run:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family: courier new;"&gt;# setsebool -P sshd_forward_ports on&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-2870544451803219828?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/2870544451803219828/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=2870544451803219828' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/2870544451803219828'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/2870544451803219828'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/12/ssh-socks-and-selinux.html' title='ssh, socks, and selinux'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-493334660996096330</id><published>2010-08-02T13:58:00.000-07:00</published><updated>2010-08-02T13:59:46.474-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='dns'/><title type='text'>Confirm your dns recursive resolver</title><content type='html'>I just encountered this elegant implementation for a service that confirms what dns resolver is performing your recursive queries.  Just go to &lt;a href="http://myresolver.info"&gt;http://myresolver.info&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The implementation details are at &lt;a href="http://techblog.igwan.eu/2010/02/how-to-know-what-dns-server-your.html"&gt;http://techblog.igwan.eu/2010/02/how-to-know-what-dns-server-your.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-493334660996096330?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/493334660996096330/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=493334660996096330' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/493334660996096330'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/493334660996096330'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/08/confirm-your-dns-recursive-resolver_02.html' title='Confirm your dns recursive resolver'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8818319521724638257</id><published>2010-07-26T22:44:00.000-07:00</published><updated>2010-07-26T23:02:18.038-07:00</updated><title type='text'>VirtualBox rocks</title><content type='html'>I used VMware Server 1 for the longest time to run several Linux virts.  I needed to reinstall virtualization software on a new PC, but VMware Server version 2 is horrible, just awful.  So instead of reinstalling the old version 1, which is a dead end, I decided to try VirtualBox.   I tried it last year, but I didn't have a good experience.  This time I'm very impressed.  It has exactly the right set of features to quickly and simply create virts, without extra bloatiness.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Nice work, Sun, er, Oracle.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://www.virtualbox.org/"&gt;http://www.virtualbox.org/&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8818319521724638257?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8818319521724638257/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8818319521724638257' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8818319521724638257'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8818319521724638257'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/07/virtualbox-rocks.html' title='VirtualBox rocks'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-1948116044266601810</id><published>2010-07-03T12:39:00.001-07:00</published><updated>2010-07-03T12:41:19.722-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='windows 7'/><title type='text'>Windows 7 shortcut arrow is too big</title><content type='html'>The Windows 7 shortcut indicator arrow is way too big.  It covers a fourth of the actual icon.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Here's a procedure that worked for me to switch to the smaller XP overlay arrow:&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://www.sevenforums.com/tutorials/10945-shortcut-arrow-change.html"&gt;http://www.sevenforums.com/tutorials/10945-shortcut-arrow-change.html&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-1948116044266601810?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/1948116044266601810/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=1948116044266601810' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1948116044266601810'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1948116044266601810'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/07/windows-7-shortcut-arrow-is-too-big.html' title='Windows 7 shortcut arrow is too big'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8462958399399810452</id><published>2010-06-29T23:20:00.000-07:00</published><updated>2010-06-29T23:34:23.390-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='itunes autodelete auto delete'/><title type='text'>iTunes auto delete won't work -- fixed</title><content type='html'>&lt;span class="Apple-style-span"  style="font-family:arial;"&gt;I upgraded to a new computer with Windows 7 and moved my iTunes library to it.  Right away I noticed that podcast auto delete was not working, even when I right-clicked on specific podcasts and made sure that "Allow Auto Delete" was on.&lt;/span&gt;&lt;div&gt;&lt;span class="Apple-style-span"  style="font-family:arial;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span"  style="font-family:arial;"&gt;The fix was to open the podcast settings dialog and change the "episodes to keep" option.  The problem is that in the latest iTunes, it's not obvious where to find that dialog box.  It's not in the main preferences dialog.  Instead find it by going to the podcasts view.  Then look at the bottom of the window.  You'll find "Unsubscribe" and "Settings..." buttons.  Click "Settings...", then change the "Settings for:" field to "Podcast Defaults".  Set "Episodes to keep:" to "All unplayed episodes".&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8462958399399810452?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8462958399399810452/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8462958399399810452' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8462958399399810452'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8462958399399810452'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/06/itunes-auto-delete-wont-work-fixed.html' title='iTunes auto delete won&apos;t work -- fixed'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-1698852837172500222</id><published>2010-06-16T10:07:00.000-07:00</published><updated>2011-02-28T09:49:19.833-08:00</updated><title type='text'>Fedora, Postfix, and SELinux</title><content type='html'>Getting these types of errors in /var/log/maillog?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;Jun 16 09:47:14 myhostname postfix/local[25474]: C269521F8C: to=&lt;root@myhostname&gt;, relay=local, delay=0.07, delays=0.02/0/0/0.04, dsn=5.2.0, status=bounced (cannot update mailbox /var/mail/root for user root. unable to create lock file /var/mail/root.lock: Permission denied)&lt;/root@myhostname&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;You're running into SELinux denials for local mail delivery.  In Fedora, correct that with:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;# togglesebool allow_postfix_local_write_mail_spool&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;span style="font-weight: bold; color: rgb(255, 0, 0);"&gt;EDIT:&lt;/span&gt; I just realized that togglesebool only changes the running config and does not survive reboots.  The permanent fix is:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;# setsebool -P allow_postfix_local_write_mail_spool 1&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-1698852837172500222?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/1698852837172500222/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=1698852837172500222' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1698852837172500222'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1698852837172500222'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/06/fedora-postfix-and-selinux.html' title='Fedora, Postfix, and SELinux'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-3599060475127075123</id><published>2010-02-06T23:10:00.000-08:00</published><updated>2010-02-06T23:17:52.392-08:00</updated><title type='text'>YM845VKM3QX</title><content type='html'>YM845VKM3QX - Serial number of my son's iPod Nano stolen from Newport High School in January 2010... :(&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-3599060475127075123?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/3599060475127075123/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=3599060475127075123' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/3599060475127075123'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/3599060475127075123'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2010/02/ym845vkm3qx.html' title='YM845VKM3QX'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-4801260173636129987</id><published>2009-10-30T12:00:00.000-07:00</published><updated>2009-10-30T12:10:26.073-07:00</updated><title type='text'>Ubuntu and the Windows MBR</title><content type='html'>I installed Ubuntu 9.10 on an external usb drive yesterday, with Windows XP on the primary drive.  I forgot that Ubuntu decides by default to write grub to the primary drive in this situation, overwriting the Windows MBR.  Ergh!  Why doesn't Ubuntu warn about that first?!&lt;br /&gt;&lt;br /&gt;In addition to overwriting the Windows MBR, this grub setup also won't boot anything without the external usb drive connected.&lt;br /&gt;&lt;br /&gt;I wanted to simply put back the XP MBR, but in this case I don't have the XP Administrator password, so I couldn't boot into the Recovery Console.  Why does XP only offer this method for fixing the MBR?!&lt;br /&gt;&lt;br /&gt;Ubuntu and Windows are annoying me today.&lt;br /&gt;&lt;br /&gt;Fortunately I do have a local admin account on Windows, so I was able to use the third-party &lt;a href="http://www.sysint.no/nedlasting/mbrfix.htm"&gt;mbrfix.exe&lt;/a&gt; to rewrite the MBR.   Again, why doesn't Windows include such a utility?  *sigh*&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-4801260173636129987?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/4801260173636129987/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=4801260173636129987' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/4801260173636129987'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/4801260173636129987'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2009/10/ubuntu-and-windows-mbr.html' title='Ubuntu and the Windows MBR'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8418242502298960068</id><published>2009-08-03T21:33:00.001-07:00</published><updated>2009-08-03T21:50:24.572-07:00</updated><title type='text'>"An error occurred while querying your Garmin GPS for information. Please ensure its software is current, and retry the Setup."</title><content type='html'>I bought a map update for my Garmin StreetPilot c330 the other day.  I tried multiple troubleshooting steps, but every time I ran the map update utility, the goofy thing failed with:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;An error occurred while querying your Garmin GPS for information. Please ensure its software is current, and retry the Setup.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;There were no good google hits for this error message. And the Garmin support website was no help either.&lt;br /&gt;&lt;br /&gt;I eventually resigned myself to calling tech support.  The first-level guy didn't have any new ideas, so he passed me on to a second-level support tech.  That guy used a special utility to make sure the unlock codes were cleared, but the install still failed.  He said that the unit was hosed and had to be sent in for factory repair.  I was irritated and frustrated at the whole situation.&lt;br /&gt;&lt;br /&gt;Today I called Garmin again to demand a refund for the map update.  In the course of handling that, I got through to a support manager.  In our conversation he mentioned that norton antivirus is known to interfere with the map update process.  Sure enough, I went into symantec antivirus, chose "unload service", and then the map update succeeded.&lt;br /&gt;&lt;br /&gt;Why didn't the 1st and 2nd level support techs know to suggest disabling the antivirus?  *sigh*&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8418242502298960068?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8418242502298960068/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8418242502298960068' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8418242502298960068'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8418242502298960068'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2009/08/error-occurred-while-querying-your.html' title='&quot;An error occurred while querying your Garmin GPS for information. Please ensure its software is current, and retry the Setup.&quot;'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-324292369602585546</id><published>2009-05-26T23:41:00.000-07:00</published><updated>2009-05-26T23:46:34.606-07:00</updated><title type='text'>Pandora</title><content type='html'>A &lt;a href="http://www.spectrum.ieee.org/may09/8788/pandorasb"&gt;recent IEEE article sidebar&lt;/a&gt; discussed &lt;a href="http://www.pandora.com/"&gt;pandora.com&lt;/a&gt;.  I've been trying Pandora tonight, and I'm liking it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-324292369602585546?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/324292369602585546/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=324292369602585546' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/324292369602585546'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/324292369602585546'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2009/05/pandora.html' title='Pandora'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8451091441783206871</id><published>2009-04-26T21:25:00.001-07:00</published><updated>2009-04-26T21:33:22.592-07:00</updated><title type='text'>Coal Creek Park</title><content type='html'>I got out for the first hike of the year today.  I did a six-mile out and back that's very near the house.  It's Coal Creek Park, and the interesting thing is that it used to be a major railway and mining center, but now it's pretty much returned to nature.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://tinyurl.com/dmnnz8"&gt;map&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8451091441783206871?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8451091441783206871/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8451091441783206871' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8451091441783206871'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8451091441783206871'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2009/04/coal-creek-park.html' title='Coal Creek Park'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-5382299210619003721</id><published>2008-12-28T22:14:00.000-08:00</published><updated>2008-12-28T22:20:14.236-08:00</updated><title type='text'>Finally got some photos posted</title><content type='html'>It's been a long time since I posted new photos at Pbase.  I had a big backlog of photos, and I finally finished processing them all this weekend.  So I uploaded Seattle and Northwest photos from 2007.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.pbase.com/saalwaechter/cwb"&gt;http://www.pbase.com/saalwaechter/cwb&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.pbase.com/saalwaechter/pnw07"&gt;http://www.pbase.com/saalwaechter/pnw07&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-5382299210619003721?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/5382299210619003721/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=5382299210619003721' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5382299210619003721'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5382299210619003721'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/12/finally-got-some-photos-posted.html' title='Finally got some photos posted'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8952496688684593928</id><published>2008-12-05T23:20:00.000-08:00</published><updated>2008-12-05T23:30:48.587-08:00</updated><title type='text'>X server problem with Debian etch in VMware</title><content type='html'>When I install Debian etch in VMware, the system comes up on first boot with:&lt;br /&gt;&lt;br /&gt;"Failed to start the X server (your graphical user interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem."&lt;br /&gt;&lt;br /&gt;The log contains: "(EE) No devices detected. Fatal server error: no screens found".&lt;br /&gt;&lt;br /&gt;Fix this by editing /etc/X11/xorg.conf and change the ``Driver "apm"'' line to ``Driver "vesa"''.  Here's the diff:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;--- xorg.conf.orig      2008-12-05 15:10:43.000000000 -0800&lt;br /&gt;+++ xorg.conf   2008-12-05 15:23:59.000000000 -0800&lt;br /&gt;@@ -65,7 +65,7 @@&lt;br /&gt;&lt;br /&gt; Section "Device"&lt;br /&gt;        Identifier      "VMware Inc [VMware SVGA II] PCI Display Adapter"&lt;br /&gt;-       Driver          "apm"&lt;br /&gt;+       Driver          "vesa"&lt;br /&gt;        BusID           "PCI:0:15:0"&lt;br /&gt; EndSection&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8952496688684593928?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8952496688684593928/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8952496688684593928' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8952496688684593928'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8952496688684593928'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/12/x-server-problem-with-debian-etch-in.html' title='X server problem with Debian etch in VMware'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-7635380464935766256</id><published>2008-12-05T11:37:00.000-08:00</published><updated>2008-12-05T11:47:12.598-08:00</updated><title type='text'>Permanently ignore packages in Apple Software Update</title><content type='html'>An annoyance of using iTunes is the Apple Software Update.  At one point it forcibly pushed Safari on users.  At least now Safari is an optional package.  The problem is that Safari, and other packages, are "checked" for install by default.  I was constantly having to pay attention to make sure I didn't accidentally trigger Apple's relentless quest to get Safari on to my machine.&lt;br /&gt;&lt;br /&gt;Well, there is a solution. Under the Tools pull-down menu, there is an "Ignore Selected Updates" option.  So one can simply check Safari and other packages, then use "Ignore Selected Updates".  From then on, Apple Software Update will behave as though those packages don't exist.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-7635380464935766256?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/7635380464935766256/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=7635380464935766256' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/7635380464935766256'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/7635380464935766256'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/12/permanently-ignore-packages-in-apple.html' title='Permanently ignore packages in Apple Software Update'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-1868572315399609903</id><published>2008-11-21T09:03:00.000-08:00</published><updated>2008-11-21T09:25:49.585-08:00</updated><title type='text'>error:   install: %pre scriptlet failed (2), skipping coreutils</title><content type='html'>I've been working lately on OS installation into image files, along the lines of the process &lt;a href="http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?ami-via-loopback.html"&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The "/usr/bin/yum -c yum.conf --installroot=/mnt/foo.img -y groupinstall Base" step for me kept producing significant errors of the form: "error: install: %pre scriptlet failed (2), skipping coreutils-x.y.z".  This occurred for 16 packages in my case.&lt;br /&gt;&lt;br /&gt;Several google hits suggested problems with selinux, but that wasn't the source of the problems in my case.  After much troubleshooting I finally discovered that an RPM macro was the culprit.&lt;br /&gt;&lt;br /&gt;In my ~/.rpmmacros file I had this entry:&lt;br /&gt;&lt;br /&gt;%_tmppath %(echo $HOME)/rpmbuild/tmp&lt;br /&gt;&lt;br /&gt;That's because on some hosts the default %_tmppath of /var/tmp has insufficient space, but my home directory generally has plenty.  During install, yum/rpm writes out rpm scriptlets to %_tmppath.  Using --installroot with yum causes a chroot(), so that path is invalid within the chroot() environment, and for some reason a number of %pre scriptlets fail in a way that causes yum to not install the package.&lt;br /&gt;&lt;br /&gt;I did look through the Base package group, and it wasn't just the rpms that happen to have a %pre scriptlet that failed.  It was a subset of them, and I haven't had the time to determine what it is about those particular %pre scriptlets that invoked the error.  Regardless, removing the %_tmppath macro from my ~/.rpmmacros eliminated the error and let the yum install work properly.&lt;br /&gt;&lt;br /&gt;(Use the "rpm --showrc" command to see your current value for %_tmppath.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-1868572315399609903?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/1868572315399609903/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=1868572315399609903' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1868572315399609903'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1868572315399609903'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/11/error-install-pre-scriptlet-failed-2.html' title='error:   install: %pre scriptlet failed (2), skipping coreutils'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-5189976170734787724</id><published>2008-11-06T01:06:00.000-08:00</published><updated>2008-11-06T08:47:20.746-08:00</updated><title type='text'>ChaCha</title><content type='html'>I occasionally use &lt;a href="http://www.google.com/sms/"&gt;Google SMS&lt;/a&gt; to check sports scores or flight info, but its query ability is limited to a few topic areas that it knows how to process.  Today I checked on an Indianapolis-based startup that I've followed over the years.  It's called ChaCha and it's at &lt;a href="http://www.chacha.com/"&gt;http://www.chacha.com/&lt;/a&gt;.  ChaCha uses human guides as part of its search processing, so you can send conversational free-form questions.&lt;br /&gt;&lt;br /&gt;The interesting thing is that they now specialize in mobile searches.  You simply text your question to CHACHA (242242), and you'll get a reply.  This is much more flexible than Google SMS, because you can ask anything.  It's basically like calling a friend and asking them to quickly research a question for you.&lt;br /&gt;&lt;br /&gt;For example, you could text this to ChaCha: "Does everyone in Minnesota like chocolate pudding pops?"&lt;br /&gt;&lt;br /&gt;Anyway, give ChaCha a try.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-5189976170734787724?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/5189976170734787724/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=5189976170734787724' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5189976170734787724'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5189976170734787724'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/11/chacha.html' title='ChaCha'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8113521573436778260</id><published>2008-10-31T16:43:00.000-07:00</published><updated>2008-10-31T16:51:41.206-07:00</updated><title type='text'>Pumpkin Seeds</title><content type='html'>In recent years our family jack-o-lantern tradition has come to include roasting the pumpkin seeds.  Here's what we do:&lt;br /&gt;&lt;br /&gt;1. preheat the oven to 300 F&lt;br /&gt;&lt;br /&gt;2. Remove all the seeds, separate them from the pumpkin goo, and clean them.  This is tedious and usually takes me 20-30 minutes.&lt;br /&gt;&lt;br /&gt;3. Dry off the seeds with paper towel. They don't have to be completely dry.&lt;br /&gt;&lt;br /&gt;4. Put them in a bowl and add the following per cup of pumpkin seeds: a) tbsp olive oil, b) 1/2 tsp salt, c) tsp garlic powder. Mix and coat well.&lt;br /&gt;&lt;br /&gt;5. Spread the seeds on a cookie sheet&lt;br /&gt;&lt;br /&gt;6. Bake in oven for 45-55 minutes, stirring/flipping every 15 minutes.&lt;br /&gt;&lt;br /&gt;Mmmmmm... pumpkin seeds&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8113521573436778260?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8113521573436778260/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8113521573436778260' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8113521573436778260'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8113521573436778260'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/10/pumpkin-seeds.html' title='Pumpkin Seeds'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-5691912819781883837</id><published>2008-10-20T23:24:00.000-07:00</published><updated>2008-10-20T23:45:38.946-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='linux'/><title type='text'>request_module: runaway loop modprobe binfmt-464c</title><content type='html'>&lt;span style="font-weight:bold;"&gt;Short answer:&lt;/span&gt;  If you are getting this error right after linux kernel initialization, you are likely booting a 32-bit kernel with a 64-bit OS.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Long answer:&lt;/span&gt; If you boot a 32-bit kernel with a 64-bit OS, when the kernel tries to start /sbin/init (a 64-bit binary), it won't recognize the binary format, and it'll try to load the binfmt-464c kernel module, which is ELF support.  (ELF support is generally compiled into the kernel, not built as a module, by the way.)&lt;br /&gt;&lt;br /&gt;The reason for the loop error is that the kernel is trying to invoke modprobe to load the module, and modprobe is itself an ELF binary, resulting in a recursion loop...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-5691912819781883837?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/5691912819781883837/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=5691912819781883837' title='10 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5691912819781883837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/5691912819781883837'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/10/requestmodule-runaway-loop-modprobe.html' title='request_module: runaway loop modprobe binfmt-464c'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>10</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-6426091405817181261</id><published>2008-09-18T09:41:00.000-07:00</published><updated>2008-09-18T09:46:08.150-07:00</updated><title type='text'>Ambiguous Ad</title><content type='html'>On my way in to work this morning I noticed this ad in the bus: "Working in healthcare and love technology?"  It then went on to give information about a local community college's medical informatics program.  For 15 seconds I was wondering what "love technology" is a euphemism for...  Then I saw what the writer really intended.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-6426091405817181261?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/6426091405817181261/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=6426091405817181261' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/6426091405817181261'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/6426091405817181261'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/09/ambiguous-ad.html' title='Ambiguous Ad'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-3197214435930546060</id><published>2008-08-16T21:06:00.000-07:00</published><updated>2008-08-16T21:08:53.828-07:00</updated><title type='text'>What words cause gmail to not display any ads?</title><content type='html'>I've noticed that email messages that include the word "funeral" trigger gmail to not display any ads.  What other words result in this behavior?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-3197214435930546060?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/3197214435930546060/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=3197214435930546060' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/3197214435930546060'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/3197214435930546060'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/08/what-words-cause-gmail-to-not-display.html' title='What words cause gmail to not display any ads?'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-1751252847988443457</id><published>2008-08-10T00:18:00.000-07:00</published><updated>2008-08-10T00:31:55.744-07:00</updated><title type='text'>Fedora and xterm1 and ncurses-term</title><content type='html'>The xterm alternate screen behavior is quite annoying.  That is, programs like man or vi or less use the alternate screen, and when they exit the original screen is restored.  (See &lt;a href="http://fixlog.blogspot.com/2006/09/stop-gnome-terminal-screen-clear.html"&gt;http://fixlog.blogspot.com/2006/09/stop-gnome-terminal-screen-clear.html&lt;/a&gt; for an animated example.)&lt;br /&gt;&lt;br /&gt;I've always switched to using TERM=xterm1, which is the same as xterm, but with the alternate screen clearing disabled.&lt;br /&gt;&lt;br /&gt;Today I installed Fedora 9, and I found that xterm1 was not present in /usr/share/terminfo/x.  Searching for information about xterm1 is pretty fruitless.  In the end, I pulled down the ncurses source rpm and rebuilt it to track down xterm1.  The answer was that xterm1 got moved into a secondary package named ncurses-term, which was not installed by default.  So a "sudo yum install ncurses-term" did the trick.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-1751252847988443457?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/1751252847988443457/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=1751252847988443457' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1751252847988443457'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1751252847988443457'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/08/fedora-and-xterm1-and-ncurses-term.html' title='Fedora and xterm1 and ncurses-term'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8375187954772810381</id><published>2008-04-06T20:20:00.000-07:00</published><updated>2008-04-06T20:21:22.857-07:00</updated><title type='text'>I love you, Debbie Lieberstien...</title><content type='html'>&lt;embed allowNetworking="all" allowScriptAccess="always" src="http://widgets.nbc.com/o/4727a250e66f9723/47f992b319fcc29a" width="384" height="283" quality="high" wmode="transparent" id="W47f992b319fcc29a" pluginspage="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash"&gt; &lt;/embed&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8375187954772810381?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8375187954772810381/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8375187954772810381' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8375187954772810381'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8375187954772810381'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/04/i-love-you-debbie-lieberstien.html' title='I love you, Debbie Lieberstien...'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-1366066782594917587</id><published>2008-02-07T22:51:00.000-08:00</published><updated>2008-02-07T23:00:21.787-08:00</updated><title type='text'>Unsolved "Windows - No Disk" error with ipod nano</title><content type='html'>&lt;span style="font-family:arial;"&gt;I have an ipod problem that's been plaguing me for months, and the all-knowing Internet has failed to provide an answer!  I won't repeat all the details, because they are already well documented at &lt;a href="http://forums.ilounge.com/showthread.php?t=208152"&gt;http://forums.ilounge.com/showthread.php?t=208152&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This also reminds me that Apple is goofy about not providing detailed release notes for software and firmware updates.  Why do they do that?&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-1366066782594917587?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/1366066782594917587/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=1366066782594917587' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1366066782594917587'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/1366066782594917587'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/02/unsolved-windows-no-disk-error-with.html' title='Unsolved &quot;Windows - No Disk&quot; error with ipod nano'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-758233076213694573</id><published>2008-02-02T18:31:00.000-08:00</published><updated>2008-02-02T19:07:17.307-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='javascript'/><category scheme='http://www.blogger.com/atom/ns#' term='browsers'/><title type='text'>Javascript alert / confirm trap</title><content type='html'>&lt;span style="font-family:arial;"&gt;Yesterday I hit a web page that contained an infinite javascript loop.  That's usually not too bad, because the browser will recognize that and say something like, "A script on this page is taking too long -- stop it?"&lt;br /&gt;&lt;br /&gt;The problem this time was that this javascript infinite loop had calls to both the alert and confirm functions.  Those functions pop up modal dialog boxes.  So instead of a loop that was chewing up cpu time, this one was popping up OK and Yes/No dialog boxes as fast as one could close them.  The nasty bit is that these are both modal dialog boxes, so one cannot do anything else in the browser while they are displayed.&lt;br /&gt;&lt;br /&gt;In the old days, I would have just killed the browser and restarted it.  But these days, with tabbed browsing, I wasn't just killing that page, but all my other tabs, too.  Fortunately for me, at the time I had no unsaved state in any tabs.  If I did I would have lost it.  There's no way to even copy/paste before killing the browser, because of the modal state.&lt;br /&gt;&lt;br /&gt;Why can't a modern browser detect this situation and offer a clean escape?  For example, if a page has popped up five modal dialogs within five seconds, then offer the user something like, "This page is opening dialog boxes quickly -- stop loading?"&lt;br /&gt;&lt;br /&gt;Sample page demonstrating this trap:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;&lt;pre&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;html&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;head&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;title&amp;gt;Modal Hell&amp;lt;/title&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;script language="JavaScript"&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;!--&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;function infinite_loop(txt) {&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;    while (1) {&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;        alert(txt);&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;        txt=txt+'.';&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;    }&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;    return;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;}&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;--&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;/head&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;body&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;Can your browser break out of this?&lt;br /&gt;&lt;/span&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;p&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;a name="foo"&lt;br /&gt;onclick="infinite_loop('Now stuck')"&amp;gt;&lt;br /&gt;&amp;lt;u&amp;gt;Click me to start an infinite&lt;br /&gt;modal dialog loop&amp;lt;/u&amp;gt;&amp;lt;/a&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;/p&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;/body&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;&amp;lt;/html&amp;gt;&lt;/span&gt;&lt;br /&gt;&lt;/pre&gt;&lt;/blockquote&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-758233076213694573?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/758233076213694573/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=758233076213694573' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/758233076213694573'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/758233076213694573'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/02/javascript-alertconfirm-trap.html' title='Javascript alert / confirm trap'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6271195465944621644.post-8505942680634033442</id><published>2008-01-21T22:58:00.000-08:00</published><updated>2009-10-01T08:04:41.062-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='firefox'/><category scheme='http://www.blogger.com/atom/ns#' term='printing'/><title type='text'>Firefox and the default printer</title><content type='html'>&lt;span style="font-family:arial;"&gt;&lt;span style="font-size:100%;"&gt;Firefox printing woes...&lt;br /&gt;&lt;br /&gt;Firefox's default behavior is to remember your last printer and printer settings, and then use them indefinitely until you change them.  This seems to be controlled by the &lt;span style="font-family:courier new;"&gt;print.save_print_settings&lt;/span&gt; configuration flag, which is true by default.  You can see this in firefox by going to about:config and filtering down to the "print" settings.&lt;br /&gt;&lt;br /&gt;This behavior is counter to the expected behavior for Windows applications, which almost always revert back to the Windows system default printer and printer settings between sessions of an application.  I know firefox isn't a "Windows application", but when running on Windows, why not behave like one?  When in Rome, and all that.  It's just an annoyance to be different than a platform's typical behavior.&lt;br /&gt;&lt;br /&gt;Here are the two problems I have with this:&lt;br /&gt;&lt;br /&gt;1. On rare occasions I will print something from firefox in landscape mode.  Of course, when I print the next thing, I forget that the setting stuck, and it comes out landscape, too.&lt;br /&gt;&lt;br /&gt;2. On rare occasions my default printer near my office will be broken, and I'll print something from firefox to a secondary printer on the other side of the building.  Guess what?  The next time I print, my output goes to the other side of the building, and I have to curse firefox for it.&lt;br /&gt;&lt;br /&gt;None of my other apps running under Windows suffer from this silly need to hold onto the last printer settings.&lt;br /&gt;&lt;br /&gt;So yesterday I figured I'd do a quick web search and find the option to make firefox behave "properly" under Windows.  That is, always go back to the system default printer and settings between sessions.  Surprisingly, there was no good hit for "firefox default printer".  The main hit was this goofy thread in which most people are debating whether or not this issue really exists, but in the end nobody solves the problem:  &lt;a href="http://readlist.com/lists/lists.mozilla.org/support-firefox/0/2677.html"&gt;http://readlist.com/lists/lists.mozilla.org/support-firefox/0/2677.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I did find the &lt;/span&gt;&lt;/span&gt;&lt;span style="font-family:arial;"&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:courier new;"&gt;print.save_print_settings &lt;span style="font-family:arial;"&gt;configuration setting.  I set it to false, but for me all that did was make firefox just never change the printer settings again.  That is, whatever settings were active when I set it to false became the default settings forever.  That's still not what a regular Windows app will do.  It should track changes the system default printer.&lt;br /&gt;&lt;br /&gt;Eventually I found advice to close firefox and manually edit &lt;span style="font-family:courier new;"&gt;prefs.js&lt;/span&gt;.  I did do that, and I found a bunch of print settings for all the configured printers on my system.  I just deleted all print-related entries in &lt;span style="font-family:courier new;"&gt;prefs.js&lt;/span&gt; except this one:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;user_pref("print.save_print_settings", false);&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Now firefox behaves as I expect it.  It defaults back to the system default printer and default settings every session, and if I change the system default printer, that change is reflected in firefox, too.&lt;br /&gt;&lt;br /&gt;I'm surprised I didn't find an obvious KB article or other top web hit for "firefox default printer".&lt;br /&gt;&lt;/span&gt;&lt;/span&gt; &lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6271195465944621644-8505942680634033442?l=saalwaechter-notes.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://saalwaechter-notes.blogspot.com/feeds/8505942680634033442/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6271195465944621644&amp;postID=8505942680634033442' title='10 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8505942680634033442'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6271195465944621644/posts/default/8505942680634033442'/><link rel='alternate' type='text/html' href='http://saalwaechter-notes.blogspot.com/2008/01/firefox-and-default-printer.html' title='Firefox and the default printer'/><author><name>John Saalwaechter</name><uri>http://www.blogger.com/profile/06221937714989771136</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>10</thr:total></entry></feed>
