Robotech_Master writes, "Long-time Slashdot veterans will remember Jon Katz, the editorial writer whose Slashdot articles invariably generated heated controversy. It appears he may have the last laugh; how many of the Slashdot posters who ridiculed him went on to be played by Jeff Bridges in a movie? From the article: 'In his new book, "A Good Dog: The Story of Orson," Katz chronicles the life and death of the lovable but troubled border collie that transformed his life. It continues the story begun in Katz's last book, "A Dog Year," now being made into a movie starring Jeff Bridges as Katz.' Katz critics may get a chuckle out of the plot synopsis for the film: 'A man having a mid-life crisis has his life turned upside down when he takes in a border collie crazier than he is.'" The film should be released in late 2007.

plasmacutter writes to let us know about the new article by Robert F. Kennedy Jr. in Rolling Stone, following up on his "Was the 2004 Election Stolen?" (slashdotted here). Kennedy recounts the sorry history of electronic voting so far in this country — and some of the incidents will be new even to this clued-in crowd. (Had you heard about the CERT advisory on an undocumented backdoor account in a Diebold vote-tabulating database — crediting Black Box Voting?) Kennedy's reporting is bolstered by the accounts of a Diebold insider who has gone on record with his concerns. From the article: 'Chris Hood remembers the day in August 2002 that he began to question what was really going on in Georgia... "It was an unauthorized patch, and they were trying to keep it secret from the state," Hood told me. "We were told not to talk to county personnel about it. I received instructions directly from [president of Diebold election unit Bob] Urosevich...' According to Hood, Diebold employees altered software in some 5,000 machines in DeKalb and Fulton counties, the state's largest Democratic strongholds. The tally in Georgia that November surprised even the most seasoned political observers. (Hint: Republicans won.)

linuxbeta writes "DistroWatch reports that the development process for Slackware Linux 11.0 is almost over. OSDir has some sweet shots of Slackware 11.0 RC1 in the Slackware 11.0 RC1 Screenshot Tour." From the article: "'There are still a few changes yet to happen, but let's call this Slackware 11.0 release candidate 1.' Other recent changes include upgrade to stable kernel 2.4.33; upgrade to udev 097, and rebuild of glibc 2.3.6 for both 2.4.33 and 2.6.16.27 kernels. The new release will ship with X.Org 6.9.0 and KDE 3.5.4, and will provide SeaMonkey instead of Mozilla."

Darlok asks: "One of our clients recently purchased a new financial software package from a major vendor for their industry. This is not a small mom-and-pop software house. The problem is, like a lot of industry-specific software, there are a considerable number of bugs. What's shocking is that to work around a problem preventing users from logging on, the manufacturer's recommended solution is to grant -Domain Administrator- privileges to all users, and they refuse (or are is unable) to explain that need further (it's bad enough that an increasing amount software seems to require local administrator privileges). Considering the enormous costs involved, how do you explain to Management that they shouldn't run this software until the problem is resolved -- which could be a long time, costing even more money? How do you balance productivity versus security when ANY productivity would give away the keys to the city? What can make an industry-specific software manufacturer pay attention to larger issues when they already have something of a captive audience?"