Carter in 1976, Moyers today.

http://www.pbs.org/moyers/journal/08152008/watch.html
http://www.pbs.org/wgbh/amex/carter/filmmore/ps_crisis.html

OK, so many folks have issues with gallery2 / drupal5 integration. My symptom was 404s on images and white screens on many pages. Some will recommend turning off gallery's clean urls implementation. That is a fine solution if it works for you. It didn't work well for me. So here's what I figured out after scouring everywhere for error messages.

An answer that works without turning off clean urls is to make sure that your gallery url is properly set under "Show Item " on this gallery config page:

http://yoursite.com/index.php?q=gallery&g2_view=core.SiteAdmin&g2_subView=rewrite.AdminRewrite

for instance, my gallery installation "embed URI" (find it under the gallery2 drupal settings screen >> install tab >> step2 fieldset, is
/index.php?q=gallery

so my "Show Item" rewrite rule should be:
gallery/v/%path%

The /v/%path% part is in there already, so just add whatver you have after the q= from the page above.

There is even an almost invisible warning to do this that shows up on the gallery2 integration module install page :), but alas, it's almost invisible. No idea why it isn't done for you on install!

HR-6304 Grouped By Vote Position

YEAs ---69
Alexander (R-TN)
Allard (R-CO)
Barrasso (R-WY)
Baucus (D-MT)
Bayh (D-IN)
Bennett (R-UT)
Bond (R-MO)
Brownback (R-KS)
Bunning (R-KY)
Burr (R-NC)
Carper (D-DE)
Casey (D-PA)
Chambliss (R-GA)
Coburn (R-OK)
Cochran (R-MS)
Coleman (R-MN)
Collins (R-ME)
Conrad (D-ND)
Corker (R-TN)
Cornyn (R-TX)
Craig (R-ID)
Crapo (R-ID)
DeMint (R-SC)
Dole (R-NC)
Domenici (R-NM)
Ensign (R-NV)
Enzi (R-WY)
Feinstein (D-CA)
Graham (R-SC)
Grassley (R-IA)
Gregg (R-NH)
Hagel (R-NE)
Hatch (R-UT)
Hutchison (R-TX)
Inhofe (R-OK)
Inouye (D-HI)
Isakson (R-GA)
Johnson (D-SD)
Kohl (D-WI)
Kyl (R-AZ)
Landrieu (D-LA)
Lieberman (ID-CT)
Lincoln (D-AR)
Lugar (R-IN)
Martinez (R-FL)
McCaskill (D-MO)
McConnell (R-KY)
Mikulski (D-MD)
Murkowski (R-AK)
Nelson (D-FL)
Nelson (D-NE)
Obama (D-IL)
Pryor (D-AR)
Roberts (R-KS)
Rockefeller (D-WV)
Salazar (D-CO)
Shelby (R-AL)
Smith (R-OR)
Snowe (R-ME)
Specter (R-PA)
Stevens (R-AK)
Sununu (R-NH)
Thune (R-SD)
Vitter (R-LA)
Voinovich (R-OH)
Warner (R-VA)
Webb (D-VA)
Whitehouse (D-RI)
Wicker (R-MS)

NAYs ---28
Akaka (D-HI)
Biden (D-DE)
Bingaman (D-NM)
Boxer (D-CA)
Brown (D-OH)
Byrd (D-WV)
Cantwell (D-WA)
Cardin (D-MD)
Clinton (D-NY)
Dodd (D-CT)
Dorgan (D-ND)
Durbin (D-IL)
Feingold (D-WI)
Harkin (D-IA)
Kerry (D-MA)
Klobuchar (D-MN)
Lautenberg (D-NJ)
Leahy (D-VT)
Levin (D-MI)
Menendez (D-NJ)
Murray (D-WA)
Reed (D-RI)
Reid (D-NV)
Sanders (I-VT)
Schumer (D-NY)
Stabenow (D-MI)
Tester (D-MT)
Wyden (D-OR)

Not Voting - 3
Kennedy (D-MA)
McCain (R-AZ)
Sessions (R-AL)

Editing document..... what's this bubble in the upper right corner of the screen? "There is a new version of Openoffice.org Available, would you like to install it? 2.4.0 -> 2.4.1" Look openoffice now updates itself, how convenient, I'll just let that run in the backround while I work. click.

Downloading 137MB (?!)......

Suddenly Firefox opens (Thank you for downloading openoffice.org) OK, Sure anytime.

Installer: This will update your version of Openoffice, would you like to Continue? Uh, yes. click.

This will extract the update files to this location, is that ok? click.

Click to proceed with the update. click.

Verifying update (90 seconds)....

Verify successful. Click next to proceed with installation. Click.

Please close the following programs to allow the installer to continue: "Mozilla Firefox - Thank you for downloading openoffice.org") (you need to close the web browser window that the installer just opened a few steps ago in order to upgrade my office suite....sounds like a bad joke.) Ok, closing firefox. Click, click.

Should we associate the following progs with OOo? >> Yes. They already are though. click.

Please click eleven times to scroll down and accept the Eula. Looks like the same one. click * 11.

Installing (3-4 minutes)....

What is your Name and initials? Prefilled thanks, click.

Would you like to register? >> have already registered thanks.

Thank you for using openoffice.org. Are we done?! Praise Jesus. I don't think I would have survived the less "automatic" version of the update. click OK.

Of course the installer doesn't bother to reopen openoffice, so I go off in search of the document that I was working on (if I can even remember what it was). Oh, and have to reopen my web browsing session as well.

Ah, the perils of building your "automatic" update as a crappy wrapper around your regular installer.

Yet another reason to stick with linux: apt-get upgrade
and you're done for every prog on your entire system. You can even do it without restarting your apps most of the time. They just launch as the new versions on next use.

Even installing a service pack to Microsoft Office is better than the "automatic update" feature in OOo. For instance installing Office 2k3 SP3 took about 4 clicks at work. Oh, and a system reboot, but old habits die hard :)

Fonts on the olpc under a non-Sugar window manager are kind of messed up. Under xfce I had to go through multiple hoops to get them to work look the right relative sizes. The second time I have to do this is as good a time as any to document this.

First of all, starting with xfce on ubuntu as prepared by mocapean, most things work ok. When you install gdm though, stuff gets crazy. Font size doubles in gtk apps.

Xfce system font sizes

Just go through the menu settings for xfce control panels. Go to Settings>User Interface first and set to sans 6. Then go to Settings>Window Manager and set window title fonts to sans bold 7
Done.

Gtk apps

put following in .gtkrc-2.0 file in homedir

style "user-font"
{
    font_name="DejaVu Sans 6"
}
gtk-font-name="DejaVu Sans 6"

KDE apps

Create or edit the file ~/.kde/share/config/kdeglobals

[General]
 StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0
 activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0
 fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0
 font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0
 menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0
 taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0
 toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0

Other stuff

On the ubuntu image I am using, this is done for us. However, if we're going to monkey around a bit with the system's dpi settings

$ xdpyinfo | grep resol

Comes back with the dpi of your screen. The olpc is 201x201 dots per inch.

xdpyinfo | grep dimen

Comes back with

dimensions:    1200x900 pixels (152x114 millimeters)

on the olpc. Incidently, millimeters is pixels/length * 25.4.

If you can't figure out why your hfs filesystem keeps getting set back to journaled...

Apple's Time Machine backup program enables journaling on the filesystem of the backup drive. Probably a good move for data integrity purposes, but it forces it back to read only under linux.

Disk Utility in Leopard no longer allows you to disable journaling through the interface on a drive. The menu where it used to be only says "Enable Journaling" but it's grayed out (cause your drive is probably journaling already).

Political Rant (feel free to scroll on by)

So, someone at apple is making it harder and harder to run non-journaled hfs+ filesystems, even for external drives. Is this someone responsibly looking out for data integrity of their users, or deviously making it harder to use the disks crossplatform? Seems like removing this option is going to inconvenience more people than it helps. I hope this is an oversight that gets fixed at some point, cause HFS+ isn't that bad of a platform for moving data if you don't care about Windows clients. Ubuntu and Debian Linux now ship with HFS+ support by default - probably because of the rise of the iPod.

Apple should make non-journaled HFS+ disks the standard for moving data between Linux and Mac and help us get away from the horrible FAT32. How hard is it to leave in the option to disable journaling - or even to point out that linux computers can read non-journaled hfs+? The CD burning system advises you how to make windows friendly disks, and mail.app offers to send windows friendly attachments! Apparently the days of Apple being the most compatible platform - a platform that went out of its way to interoperate with what the other systems were doing to minimize pain for its small user base - is now over. Of maybe Apple is fine with interoperating with the ubiquitous, expensive and inconsistent windows world, but is pretty scared to invite the rapidly maturing and totally free Linux platform to the party? Unfortunately, too many steps down that road and microsoft's NTFS will solidify into the default crossplatform filesystem now that linux has read/write support for it. With all the patents on NTFS being held in Redmond, that's not good for anyone long-term.

Getting started

Anyway, here's how you disable journaling on a hfs+ filesystem by using the command line tool.

diskutil is the command line tool provided by Darwin (the mac's BSD core) that does what Disk Utility does through a graphical user interface. Fortunately, it can do everything that the graphical interface can do. Parenthetically, diskutil is still capable of making partitions smaller than 1GB (another casualty of Leopard's changes to the GUI Disk Utility) check out the partitionDisk command - it's not easy, but it works.

Ok, back to our subject!

Scouting it out

Type diskutil --help to see all the associated commands. Type man diskutil to really get more information about what it can do.

First: Lets assume that you are trying to turn off journaling on a 300GB disk called "Janice" that is connected to your machine via firewire. The first thing you should do is to read the listing of disks to find out where Janice is in the system's underlying mount points.

yourcomputer:~ youruser$ diskutil list

diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *74.6 Gi    disk0
   1:        Apple_partition_map                         31.5 Ki    disk0s1
   2:            Apple_Bootstrap                         40.0 Mi    disk0s2
   3:            Apple_UNIX_SVR2                         2.0 Gi     disk0s3
   4:            Apple_UNIX_SVR2                         33.0 Gi    disk0s4
   5:                  Apple_HFS MacHD                   39.4 Gi    disk0s6
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *279.5 Gi   disk1
   1:        Apple_partition_map                         31.5 Ki    disk1s1
   2:             Apple_Driver43                         28.0 Ki    disk1s2
   3:             Apple_Driver43                         28.0 Ki    disk1s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk1s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk1s5
   6:             Apple_FWDriver                         256.0 Ki   disk1s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk1s7
   8:              Apple_Patches                         256.0 Ki   disk1s8
   9:                  Apple_HFS Janice                  279.4 Gi   disk1s10

Look for the name of your disk. The second set of lines there ends with a line that says "Janice". diskutil groups all of the logical divisions of a physical disk together in the list. Since our volume 'Janice' is listed under /dev/disk1, we can determine that /dev/disk1 is our 300 GB external firewire drive.

What is the rest of that garbage before the the Janice line? It's a series of small partitions that Apple uses to store various types of information about the disk. The very first one, disk1 itself, is a tiny area containing the map of all the other areas. Each subsequent partition has an added number s1, s2 etc appended to the disk name - disk1 in this case - to make a complete identifier for that partition on this mac system. You're going to need to note that Janice HFS partition where we want to disable journaling is disk1s10.

OK, we know what we have to target, let's do it.

Taking Action

If you read the man page for diskutil (type 'man diskutil' in your terminal) you might think that we could just type:

yourcomputer:~ youruser$ diskutil disableJournal /Volumes/Janice
An error occured journaling the filesystem: The underlying task reported failure on exit (-9972)

Hmm... what happened here.. dunno. Maybe despite me owning the disk, I need to apply a little more elbow grease by using elevated privileges. I'll use sudo.

yourcomputer:~ youruser$ sudo diskutil disableJournal /Volumes/Janice
Password:
An error occured journaling the filesystem: The underlying task reported failure on exit (-9972)

Darn it, Apple! Is this why you disabled the option in the GUI? Cause there are bugs in diskutil that you didn't bother to fix by October's Leopard ship date? Maybe I'm being cynical, but the error message sure isn't helping me at all.

Oh well... Google doesn't come to the rescue.

Reading the man page again..... what if I dismount the disk and use the [force] option that the manual page tells me can only be run on an unmounted disk?

Let's try. Unmount your drive -- "Eject" in the Leopard finder. Then form a slightly different command by inserting the term 'force' after the disableJournal command, and by replacing the mounted volume name with the partition identifyer that I had you get in the first section. Like so...

yourcomputer:~ youruser$ sudo diskutil disableJournal force /dev/disk1s10
Password:
Journaling has been disabled for volume Janice on disk1s10

Ah, that's better. I think I'll move all my media files onto this disk for editing on my inexpensive, user-friendly and powerful linux workstation. Sweet, thanks Apple!

UPDATE: A quicker solution is to hold down option when you click the menu in Disk Utility - this enables the disable journaling option. Thanks to the reader that informed me. Fortunately haven't had to struggle with either command line errors or gui obfuscation to disable journaling again as haven't booted MacOS in a while.