Slashdot Mirror

An anonymous reader writes "As covered earlier on Slashdot, Amit Singh had shown how to access and use the motion sensor feature in the late model PowerBooks for innovative things, which created quite a buzz in the Mac community. In an ingenius new article, Singh has taken the idea all the way and released software which lets you use a PowerBook with a motion sensor as a general purpose input device which works with existing apps. IMHO the coolest use of this is for playing games: be sure to check out the video footage in the article. For instance, in a car racing game, you steer by tilting the PowerBook left and right, go faster by tilting it forward, brake by tilting it backwards! You can also scroll in apps. Google Map scrolling with my PowerBook feels like flying in an aiprlane over the terrain. I must say you have to try this in real life to appreciate the experience ... go to the Apple store or something if you don't have the hardware ;-) Before this my girlfriend (who uses a Dell notebook) has never called anything computer related "jawdropping"! Wouldn't it be nice to have a gaming motion sensor be standard issue in all future laptops?"

indiejade writes "Yahoo! recently launched its take on the virtual fantasy-prediction game market. The Tech Buzz Game allows players to invest in what they think will be the "next big thing" RE high-tech products, trends, or concepts. CNet reported that the game was announced at the now-in-progress Emerging Technologies Conference in San Diego. The players with the three highest scores accumulated in the game between now and July 29th will win one of various Apple products."

Christopher Reimer writes "O'Reilly Policy DevCenter has a nice overview concerning the legalizing software patents in the European Union. From the article: 'The Computer Implemented Inventions Directive (CIID), which seeks to clarify the issue, is still being fought over in the EU and may or may not result in legalizing them. For small and medium enterprises (SMEs) and in particular, free software projects, there is much to lose.'"

tres3 writes "In an interview with the O'Reilly Network Mr. Lessig discusses many current issues that may have future legal implications. He starts with MGM's request for Certiorari in the Grokster case. His conclusion is that ReplayTV was forced out of business by a legal challenge, not a legal victory. Lessig continues on to discuss, among other things, The Creative Commons and their new Sampling License and how it may affect the way that some movies and music, that contain samples from other sources, are made in the future. From the article: 'So the same act of creativity in some sense, you know, taking, creating, mixing out of what other people do, is legal in the text world and illegal in the digital media world.'"

TivoLee writes "If you were worried that courts have been cracking down too much on Internet miscreants lately, think again. Sure, virus writers and spammers have been hit with some tough sentences in recent months. But what about this: the U.S. govt. has dropped charges against a group of four guys known as the DDOS Mafia. Two of the men admitted to releasing viruses so they could create botnets to launch DDOS attacks for hire. Their boss is accused of causing $2Mil in damage to victim sites. Yet prosecutors are dropping charges, so they can get the criminals to snitch on other criminals. Oi vey."

barryhawkins writes "When sharing with others that I was reviewing an O'Reilly book through their User Group & Professional Association Program, the first question was always the same: 'What book are you reviewing?' After saying the title was Understanding Open Source & Free Software Licensing, responses ranged from 'What's that?' to 'Well, you won't have any trouble sleeping!' One might think that this list of people included relatives and coworkers who were not attuned to the open source community and its issues. On the contrary, the responses came from those within my circle of acquaintances, which includes software developers, system administrators, and even an intellectual property lawyer. Licensing is not exactly the sort of topic where people slide forward in their seats and ask to be told more. Such is the appeal of software licensing; however, the importance of understanding licensing, particularly within the context of open source development, cannot be overstated." Read on for Hawkins' review. Understanding Open Source & Free Software Licensing author Andrew M. St. Laurent pages 208 publisher O'Reilly rating 8 reviewer Barry Hawkins ISBN 0596005814 summary A worthwhile introduction to open source licensing

Those familiar with the O'Reilly product offerings have no doubt seen or purchased one or more their Pocket Reference series. These are not comprehensive references, but rather convenient guides for a specific topic to provide the sort of information one is not likely to have committed to memory, particularly as the trend of having cross-disciplined technologists continues. This book could be considered the analog of such pocket guides for open source and free software licensing. Open source licenses and their legal interpretation, though, easily warrant a "pocket reference" that is a full-sized book of nearly 200 pages.

Frankly, reading through a software license and maintaining a reasonable level of comprehension is a rather tough job. The author manages to make the task far more bearable and fruitful at the same time; a difficult balance to strike. The pace of the annotation works well to break up the various licenses (twelve in total) into bite-sized chunks. Chapters 2 and 3, which address the Apache/BSD/MIT family of licenses and the GPL/LGPL/MPL family of licenses respectively, each end with a section titled "Application and Philosophy" that serves as a sort of reward for making it through the license and establishes a touchstone to summarize and provide meaningful context for what has been covered.

The annotations of the different licenses are a great introduction, but the book should not be considered a complete reference for open source licensing issues. The book seems to affirm this at points where the author indicates that particular topics fall outside the book's scope, even to the point of recommending experienced legal counsel for certain issues. It also has a wonderful collection of footnotes and reference to other resources to allow the reader to flesh out topics of interest beyond the focus of this work.

One subtlety of the book that should not be missed is how the history of the open source movement is woven throughout the book to provide the context in which these licenses came into being and were modified to accommodate the vibrant, emerging world of open development models. The book's last two chapters bring that context to the foreground, fully developing the consequence of the licenses in daily development activity. It is far too easy to view these licenses and as mere legal documents that exist in and of themselves; the author reminds us that these licenses are the manifestations of a spirit of selfless contribution and work toward social good made possible by the considerable sacrifice of quite gifted individuals. For those passionate about the open source and free software movements, the section of chapter 7 titled "Models of Open Source and Free Software Development" is a poignant and stirring encapsulation of the first years of the GNU and Linux projects and the work that brought them into being. The cliché rings true; we do indeed "stand on the shoulders of giants."

The number of editorial errors involving misspelled and/or missing words seemed relatively high; this is a trend that seems to have developed in technical books in recent years, to a point that the technical community has come to accept it as some sort of side effect of the rapid pace with which books must be produced in order to keep pace with the rate of change. Given that this is an issue present in other works as well as this one, it should not particularly count as a mark against the work, but rather serve to underscore an issue publishers should consider improving.

Understanding Open Source & Free Software Licensing strikes a balance between completeness of subject matter coverage and manageability of size. Given the amount of attention the average open source user or developer has given to licensing, reading this book would be a considerable improvement. This book is recommended for a couple of audiences. First, it serves as a great foundation for developers either active in or contemplating participation in open source development. Searching most any open source mailing list for the term "license" can usually turn up some of its hottest flame wars. If most developers had this introductory level of understanding about the main open source licenses, hundreds of message threads arguing about licensing could be avoided.

A second audience for this book is the project manager and/or CTO in most corporate IT shops. Most corporate projects are making use of numerous open source libraries and frameworks. This is particularly true with J2EE, but also with .Net as a number of .Net counterparts to popular J2EE resources arise, e.g. NAnt, NUnit, etc. This book can dispel unnecessary apprehension regarding the use of these libraries that often arises from fear, uncertainty, and doubt (FUD) propagated in much of the mainstream technology media. It can also equip managers to make informed decisions about team members' potential contributions to open source projects and the potential legal implications.

You can purchase Understanding Open Source & Free Software Licensing from bn.com. (You might also be interested in Peter Wayner's review of Lawrence Rosen's book on the same topic, Open Source Licensing .) Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Noryungi writes "In this provocative article, Brian McConnell argues that Silicon Valley, instead of staying in the saturated IT field, should apply its resources (including its chip-producing plants) into Solar Power/Renewable energy. Intel branded Solar Panels, anyone?"

Trizor writes "Bloggercon III commenced today with the opening session ending in a singalong of 'This land is your land'. The sessions ranged from introductions on blogging to a comparison of bloggers and journalists. The developers at O'Reilly have provided notes, coverage, and commentary on the event."

Trizor writes "Bloggercon III commenced today with the opening session ending in a singalong of 'This land is your land'. The sessions ranged from introductions on blogging to a comparison of bloggers and journalists. The developers at O'Reilly have provided notes, coverage, and commentary on the event."

Trizor writes "Bloggercon III commenced today with the opening session ending in a singalong of 'This land is your land'. The sessions ranged from introductions on blogging to a comparison of bloggers and journalists. The developers at O'Reilly have provided notes, coverage, and commentary on the event."

IphtashuPhitz writes "The Russian spamware programmer anonymously accused eariler this week of writing the Sobig worm has responded to the accusations. Ruslan Ibragimov of Send-Safe doesn't deny that his program uses proxies to hide spammer's identities. But he totally refutes the report's technical analysis in an online interview over at OReilly Network."

grey writes "The Age has a story up about how the OpenBSD community has been contacting wireless chipset vendors to license their firmware binaries under terms that would allow for free redistribution. This is important, because even with existing GPL and BSD licensed drivers for these chipsets, the drivers don't function without first loading onerously licensed firmware binaries which can only be acquired from the vendor, not shipped by an OSS provider." (Read more, below.)

grey continues "This means that currently, these wireless NIC's don't work out of the box on OSS install or boot media. In just the first 4 days, hundreds of users wrote and called vendors, and already 2 vendors freed their firmware, and several others are in discussions with Theo de Raadt about taking similar steps.

We need your help! TI has still not responded at all. You can call or write to Bill Carney, - Director of Business Development of TI's WNBU to add to the approximately 400 well written messages the OpenBSD community has already sent to TI. We hope that you'll help, and if you do please keep messages polite and to the point. Please remember, we are not asking for the vendors to open source their firmware under the GPL or BSD licenses (though we wouldn't complain if they did). Instead, ask if they would simply email Theo to open discussions on licensing their firmware binaries under terms that allow for free redistribution. If changed, these firmware binaries would then be able to be included with OSS software and function with existing BSD and GPL licensed device drivers from the start.

You can find other contacts for target vendors here, here, here, and here, and it can't hurt to sign this petition. These changes aide all OSS efforts, not just OpenBSD. As you can see from the OpenBSD community's results already, contacting these vendors really does make a difference. We're sure that with the numbers of OSS minded readers in the Slashdot community you can really help with the heavy lifting where fewer numbers of BSD users have already begun to succeed, and all Open Source Software users will benefit."

hanky writes "Google brings search to your very desktop with Google Desktop, a mini Google index of your own. Search your filesystem, Outlook or Outlook Express inbox, AIM instant message transcripts, and Internet Explorer cache. There's a full introduction to the Google Desktop over at the O'Reilly Network. It's Windows-only, but still cool enough for this Mac guy to find it intriguing."

Bunch2 writes "In this article at OReillynet, a 'hacker' explains why he put his superior coding skills to use by writing a spam mailer called Fahrenheit. (Hint: $$$) Turns out his little creation is also being used by criminals to 'phish' bank account information from gullible folks. The article shows how talented but morally challenged techies are becoming stooges of 'spammers, con artists, and other criminals.'"

Marc Hedlund writes "Bloglines, everyone's favorite RSS aggregator, changed the RSS world again today by releasing the Bloglines Web Services APIs. FeedDemon, NetNewsWire, and Blogbot will all be adding support for the APIs so that users can store their feed state on Bloglines, and read their feeds from any browser. I posted an article introducing the APIs, including a full three-pane desktop aggregator source code example, on the the O'Reilly site."

Marc Hedlund writes "Bloglines, everyone's favorite RSS aggregator, changed the RSS world again today by releasing the Bloglines Web Services APIs. FeedDemon, NetNewsWire, and Blogbot will all be adding support for the APIs so that users can store their feed state on Bloglines, and read their feeds from any browser. I posted an article introducing the APIs, including a full three-pane desktop aggregator source code example, on the the O'Reilly site."

WaveDave writes "I have found some really inspiring pages out there by folks who are hacking together amazingly cool low-cost hardware/software/etc projects (reminiscent of the old homebrew computer club days). With the cost of IC's, sensors, microcontrollers, and PC's falling through the floor, we've entered a time where the barriers to entry on hacking neat projects are lower than they've ever been. There are a lot of indicators of the excitement in these projects, including the recent announcement of the upcoming Make Magazine from O'Reilly. Initially blown away by Matthias Wandel's projects, I've begun to put together a small collection of links to other creative DIY-ers out there, as well as resources for finding parts, getting stuff made (like PCB's and machined stuff). My current list is here - what are some of your favorite creatives and resources?"

WaveDave writes "I have found some really inspiring pages out there by folks who are hacking together amazingly cool low-cost hardware/software/etc projects (reminiscent of the old homebrew computer club days). With the cost of IC's, sensors, microcontrollers, and PC's falling through the floor, we've entered a time where the barriers to entry on hacking neat projects are lower than they've ever been. There are a lot of indicators of the excitement in these projects, including the recent announcement of the upcoming Make Magazine from O'Reilly. Initially blown away by Matthias Wandel's projects, I've begun to put together a small collection of links to other creative DIY-ers out there, as well as resources for finding parts, getting stuff made (like PCB's and machined stuff). My current list is here - what are some of your favorite creatives and resources?"

jaaron writes "Can open source and closed standards work together? That's the question asked by Kevin Bedell in his O'Reilly weblog article. The issue springs from questions on an OSI mailing list, hinting that Sun Microsystems is looking for an open source license that would require derivatives to maintain test suite compatibility. Under such a scheme Sun could maintain control of the Java API but allow open implementations."

An anonymous reader writes "In February at the O'Reilly Digital Democracy Teach-In, technologists from the Dean, Kucinich, Clark and Kerry campaigns laid down arms to share tech plans while their respective camps were still battling it out in the primaries. A (private) list and requirements for fall campaign organizing ensued. Just six weeks ago, a few of the developers converged in San Francisco for a show and tell of their emerging free software tools. Today, the AdvoKit project was the first to tag beta, hoping to kick-start the campaign software revolution in time for November 2nd."

Krafty Koder writes "Over at Newsforge (Part of OSTG, Slashdot's Parent) there's an interesting article that attempts to dispells the myth that Linux isn't ready for the desktop or that Windows still beats Linux. Three myths are explored - that Linux is harder to use, difficult to install and that there's not enough apps ."

querencia writes "Sun has announced that Solaris 10 will comply with the Linux Standard Base specification, thus allowing Linux apps to run unchanged on Solaris. This isn't emulation -- they claim that it is 'kernel-integrated and supported as an operating system feature.' While I appreciate the benefits of the Solaris OS, I've considered them on the losing end of the battle until now. Will the power of Linux apps put Solaris back into the running?" Update: 08/04 15:50 GMT by J : At OSCON, Sun reaffirmed that Solaris 10 will be open-sourced. They said it would be one of the OSI licenses, not sure which yet; that this was approved at the highest levels of the company; and (with the expected "we're just guessing" language), it could happen as soon as year's end.

ajs writes "As you may know, there was a contest between Dan Sugalski and Guido van Rossum over the performance of Parrot running Python byte-code, and the loser was to take a pie in the face. Well, in the end it was between Dan and time and Dan lost... he was unable to get the Python bytecode translator to work sufficiently well for the contest (it was fast, but not complete), but when Dan conceded, Guido was gracious enough to decline to throw a pie, what a sport! The Perl community, however, was not quite so gracious (they wanted to see Dan take a pie for the team), and the final event ended up being a benefit for the Perl Foundation. Meanwhile, see Dan's Blog for details on what sorts of Parrot goodness came of this."

An anonymous reader writes "Reporter Jay Lyman attended the O'Reilly OSCON developers' get-together and wrote daily briefs plus a wrap-up that are all posted on NewsForge now. If you didn't make it to this excellent conference, reading Jay's reports is the next best thing." Yes, NewsForge is also part of OSTG.

GMan00 writes "A flurry of BSD UNIX-related (Berkeley Software Distribution) books have hit the bookstores during the recent past, and more are on the way. From books specific to Secure Architectures with OpenBSD in April 2004 and the reissue of The Design and Implementation of the BSD Operating System for FreeBSD 5.x (expected in August 2004), to Michael Lucas' series of BSD Books from NoStarch Press, print documentation is certainly available for those interested in learning about the free, open source UNIX system which powers operations such as Yahoo! portal and Sendmail.org website, Verio and Pair hosting, not to mention web server survey site Netcraft. Dru Lavigne's BSD Hacks (O'Reilly and Associates, May 2004), is the latest book in these releases, and is an enormously useful resource for system administrators and end-users alike." Read on for the rest of George's review. BSD Hacks author Dru Lavigne pages 427 publisher O'Reilly & Associates rating 10 reviewer George ISBN 0596006799 summary A great array of hacks you can perform on your BSD box, many applicable to all the BSDs, including FreeBSD, NetBSD, OpenBSD and Darwin/OS X.

Dru writes the BSD Basics column on O'Reilly & Associates' OnLamp. Her clarity and fluid style are perfect for those looking to understand aspects of the BSD operating systems. I have had some email communications with Dru about various New York City *BSD User Group-related activities, and managed to speak with her several times at BSDCan this past May.

Like most computer nerds, Dru has a sense of humor. Unlike most, however, she's actually funny.

BSD Hacks is the first book that is almost solely focused on hacks for sysadmins, without boring you with the details for basic operating system installation and configuration that has been so well documented elsewhere. BSD Hacks is not just for sysadmins, though. Intermediate and advanced BSD users will also find the book an excellent tool. For those who find difficulty in BSD installs and other fundamentals, on the other hand, it's best to start with the FreeBSD Handbook, the NetBSD Guide or the OpenBSD FAQ.

There's lots of good hacks buried in the various BSD books, around the internet in different HOWTOs and tutorials. But BSD hacking is the sole purpose of BSD Hacks; there's no need to browse through install screens and overviews of TCP/IP before getting to the heart of the matter.

With 100 listed hacks, multiplied by an impressive level of detailed angles for each, Dru provides an array that demands the placement of this book right in your server room, not in a pile of "must-read-at-some-distant-point-in-the-future" texts.

The majority of hacks are applicable to all the BSDs, including Darwin and OS X, although some are specific to one BSD or another.

This review obviously can't list every hack, although you would be smart to sit and work through the book yourself over a weekend or two. But it is possible to provide a good flavor of BSD Hacks in brief. O'Reilly and Associates does give a good glimpse on their Sample Hacks page, but let's do a quick work through ourselves.

The first chapter is called "Customizing the User Environment," and is probably best for end-users looking to go beyond their first steps. But it does include some useful hacks, such as "Use an Interactive Shell" that certainly fit well into the arsenal of any sysadmin, not to mention Hack #12 "Use Multiple Screens on One Terminal."

The second chapter, "Dealing with Files and Filesystems" also contains gems for both end-users and sysadmins. The use of mtree, which maps a directory hierarchy, is mentioned as a tool for recovery. Later on in chapter 6, Dru details its use for making a hacked data integrity checker, thus filling the role often played by products such as Tripwire.

Another great tool Dru covers in the second chapter is g4u, a free ghosting program that gives you the ability to perform quick restores over ftp. Ghosting a drive image is an incredibly useful tool, whether it's about replicating servers or doing a quick reinstall and configuration when a server fails in an emergency.

Chapter 3 is entitled "Boot and Login Environments." It gives some hacks that aren't just for basic system administration, but also some useful security ones including changing your /etc/passwd file to Blowfish encryption and utilizing OPIE for one-time passwords, which is built into FreeBSD.

"Backup Up" is the focus of Chapter 4. It includes some very creative methods of dealing with maintaining that necessity, and also includes an excellent primer on Bacula, which is increasingly gaining prominence as a cross-platform backup system.

Chapter 5 covers "Network Hacks," and continues on educating a sysadmin. Included in this chapter is the tcpdump program, a vital tool for watching traffic flowing by your network interfaces.

There's a strong security focus in Chapter 6, entitled "Securing the System." While security hacks are sprinkled generously throughout the book, this chapter works with firewalling with IPF and PF, in addition to covering SSH and Snort. It also includes the earlier mentioned 'intrusion detection-lite' approach with mtree.

Chapter 7, "Going Beyond the Basics" explores scripting, analyzing dreaded buffer overflows and more. Dru also includes a bit on "Creating a Trade Show Demo," not something you'd expect documented in print anywhere, but nevertheless quite useful for anyone working for the BSDs at a conference.

Dru continues with "Keeping Up-to-Date" in Chapter 8, which includes useful details on upgrading and downgrading your installed ports.

The final chapter is "Grokking BSD." "Grok," as Dru comments, refers to the science fiction writer Heinlein's Martian phrase for having a "thorough understanding." Dru covers creating your own manual pages, dealing with custom patches, playing with dictionaries and more.

Certainly there are no walls between each chapter, as many of the hacks could be shifted around. All the more reason to work your way through the book from beginning to end.

One useful addition for this book could have been somehow denoting which of the BSDs (in some cases, it's all of them) to which each listed hack can be applied. Certainly not all are available to Darwin and Apple's OS X. And certainly there's no point in making the OpenBSD /etc/passwd file encrypted in Blowfish, since that is its default.

While many of the hacks are found somewhere in the manual pages, on some useful website, buried in another book or in the minds of some developer somewhere, they're not necessarily in the annals of official documentation. But there's no single book or site that provides the depth and breadth that Dru provides. She managed to tap into the thoughts of dozens of developers and sysadmins around the world, greatly enhancing the variety of hacks in this book.

As a side note, the scope of BSD Hacks isn't limited to just the BSD family. Many of these are likely applicable to Linux and the other UNIX systems. But with recent, impressive increases in the BSD install base, there's a good chance that you can access a BSD box somewhere.

Whether you're a sysadmin managing hundreds of servers, or a power user ready to go beyond the obvious, BSD Hacks belongs next to your CRT.

You can purchase BSD Hacks from bn.com. Slashdot welcomes readers' book reviews. To see your own review here, carefully read the book review guidelines, then visit the submission page.

Robin Berjon writes "Macromedia recently announced that its latest version of Flash Lite (a limited Flash for mobile devices) was to support SVG Tiny 1.1, and support it fully (though no one has yet been able to verify that assertion). For a moment, the Web community wondered if they might be playing nice at last, after yielding to massive pressure from the mobile market to support W3C and 3GPP standards, or if they simply meant to use SVG as a trojan to get Flash into mobile devices. An article freshly published on Macromedia's web site clearly makes the case that they're after the latter, speading as much FUD as possible along the way. Thankfully, Antoine Quint decided to respond in a brief O'Reilly Net article in which he debunks Macromedia's marketing lies one by one, and expands on the wondrous features of SVG Tiny 1.1 and the shortly upcoming SVG Tiny 1.2 that make people drool before their mobile phones. "

jpkunst writes "Chris Shiflett at oreillynet.com summarizes (with lots of links) a discussion about scalability, brought about by Friendster's move from Java to PHP. Chris argues that PHP scales well, because it fits into the Web's fundamental architecture. 'I think PHP scales well because Apache scales well because the Web scales well. PHP doesn't try to reinvent the wheel; it simply tries to fit into the existing paradigm, and this is the beauty of it.' (The article is also available on Chris' own website.)"

Skapare writes "O'Reilly Network's LinuxDevCenter has a great article summarizing the indemnification possibilities for businesses considering switching to (or staying with) Linux. Author Tom Adelstein covers the business risk mitigation aspects of using Linux today, and details available indemnification offerings from Novell, HP, Red Hat, and OSRM. So why not print a copy and send it to your company CEO."

jpkunst writes "Ed Willis, over at O'Reilly's ONLamp.com, gives his varied reactions to Fred Brooks' classic The Mythical Man-Month, after 'having finally read it in its entirety'. '[...] simultaneously you can see just how much the field has changed since the original writing and just how much has stayed stubbornly the same.'"

theodp writes "While news accounts credited Tim Berners-Lee's mighty pen with triggering the USPTO reexam of the Eolas plug-in patent that could negate a $520+ million judgment against Microsoft, newly released USPTO interview notes suggest the reexam may owe more to an alliance of tech giants who appear to have quietly advanced the same arguments to the USPTO weeks prior to Berners-Lee." See also some previous coverage of the Eolas patent circus, and more below about the USPTO reexam.

theodp continues "According to a 4-27 Interview Summary, the USPTO presented Eolas with a 10-14 letter signed by in-house counsel from Microsoft, AOL and Macromedia, a 10-15 letter from Adobe, and a 10-22 letter from the law firm of Sidley Austin (aka Microsoft's lawyers) in connection with its proposed rejection of Eolas' patent claims. All predated the 10-24 letter from the W3C's counsel as well as Berners-Lee's widely-publicized 10-28 letter, which seems unlikely to have prompted the USPTO's detailed 10-30 Reexam Order. The W3C has repeatedly had no comment when asked if the 'newly cited art' provided in its 10-24 filing had already been supplied earlier to the USPTO by others. UPDATE: In response, the W3C's Danny Weitzner points out that the preceding words are mine and should not be confused with those of a distinguished journalist."

angryflute writes "'Have you played Atari today?' was an ad jingle for the Atari 2600 VCS game console during its reign in the early years of the video game industry, from the late 1970s to early 1980s. That question that could apply even now, according to an O'Reilly Network article, thanks to the passion of programmers who've continued to make new Atari 2600 games for the past few years."

fmclain writes "The Open Voting Consortium (OVC) which has already been mentioned here will be demonstrating its open source voting system, which includes a voter verifiable paper trail, at this year's OSCON in Portland. The Mercury News (free reg.) describes this as the touch-screen holy grail. Given Diebold's troubles in California this can't come too soon. The OVC has already demonstrated a working system in Sacramento."

honestpuck (Tony Williams) writes "Many years ago I bought a second hand Ford Cortina in dubious condition. I kept it running with the assistance of a marvelous volume purchased at a specialist bookstore that was referred to as "the shop manual." It wasn't much help teaching you how to drive or how to park but if you needed to know how to perform an oil change, flush the radiator or bleed the brakes it told you all the details. Now James Duncan Davidson has given me a shop manual for Macintosh OS X Panther." Read on for Williams' review of the O'Reilly published Running Mac OS X Panther. (And for the curious, here's what google has to say about "Ford Cortina.") Running Mac OS X Panther author James Duncan Davidson pages 292 publisher O'Reilly and Associates rating 8/10 - Excellent book, a little thin on details in a few places reviewer Tony Williams ISBN 0596005008 summary A good shop manual for those running Panther

This volume assumes you know how to use your Mac, how to perform all the routine changes that are easily accomplished with the GUI. Davidson also assumes you don't want to know how to get a movie running as your desktop, or get an Exposé blob floating on the screen or any of the usual sort of 'hacks' or 'hints.' What he gives is a good guide to lifting the hood and performing serious mechanical work or tweaking the performance of your Mac with enough background information so that you can feel confident taking your own steps.

It was good after a few near misses to read an O'Reilly book that was once again well written, well edited, tight and crammed full of information pitched at just the right level. Davidson has done an excellent job with this book.

Davidson starts with a little history, and from the viewpoint he presents, this is not a waste of space; he spends his time explaining exactly how we arrived at the current version of the Mac OS.

Then we have a chapter titled "Lay of the Land" that explores the file system, including both the Finder view and the view you get from the command line. It also explains the four file system domains and the 'Library' directory. The third chapter is a quick (20 pages) look at the Terminal and shell.

Then we get 'Part II: Essentials,' which is the 120-page core of the book. This starts off, logically, with system startup and the login (and log out and shutdown). This is followed by short chapters on users and groups, files and permissions, monitoring, scheduling and preferences and defaults before a marvelous long chapter on the file system. Davidson goes into great detail and closely covers each of the topics, making sure that you get all the details not just 'recipes.'

Part III ("Advanced Topics") starts with a chapter on Open Directory that I found particularly useful. It includes coverage on Kerberos and single sign-on that explains it well, as well as the command-line Open Directory tools. The chapter on printing could have had a bit more guts. It covers the obvious but leaves out such joys as CUPS apart from a half-page sidebar; since sharing printers has caused me more than a little grief I would have appreciated more detail here. The final chapter on networking is better, and provides more useful detail.

It must be said that this section concentrates more on user level detail and leaves out real information on server level software and options. Given the target group for this book, and that a book has to draw a line somewhere, this is quite fair.

Davidson has picked his topics well, almost everyone will find all of Part II useful and educational. Part III is perfect for people wanting to run Panther in a corporate environment. He has balanced the command line and GUI well, pointing out where you can do a job with both and explaining the details.

Oreilly's page for the book has a table of contents and index but no example chapter. If you go to Davidson's page at O'Reilly there is a link to a short excerpt on scheduling tasks as well as several earlier articles Davidson has written for MacDevCenter.

I would recommend this book to any Panther user with a moderate amount of experience. It is not for the newcomer to the Mac, perhaps, but everyone else will benefit from this book.

You can purchase Running Mac OS X Panther from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page

jpkunst writes "Andy Oram, who attended the MySQL Users Conference which was held April 16-18 in Orlando, Florida, attempts to explain MySQL's popularity in his weblog at oreillynet.com. (More weblogs about the 2004 MySQL Users Conference can be found at the The 2004 MySQL User's Conference & Expo Blog Collection.)"

jpkunst writes "Andy Oram, who attended the MySQL Users Conference which was held April 16-18 in Orlando, Florida, attempts to explain MySQL's popularity in his weblog at oreillynet.com. (More weblogs about the 2004 MySQL Users Conference can be found at the The 2004 MySQL User's Conference & Expo Blog Collection.)"

Phil Windley writes "In his inimitable style, Tim O'Reilly tells us why GMail matters. The piece is entitled, 'The Fuss About GMail' but that doesn't begin to properly identify the real meat of what Tim's saying. Tim does discuss some of the privacy concerns on GMail and why he's not concerned, but he also breaks new ground on why GMail is not just another free email system. For example, Tim talks about how GMail might herald an era of large centralized computing and calls for APIs to allow GMail content to be move back and forth between it and other systems." Reader chris mansley writes "Google is quietly responding all the flak being given to their new email service. They have added a statement to quell the growing list of concerns. No more keeping email forever is at the top of the list. The reviews have been sparse on details and screenshots, but now Google is providing a sneak peek here and here." The only thing I didn't like about Gmail was their apparent intention to keep your mail forever, regardless of your wishes. Since they've now clarified that they don't plan to do that, it doesn't seem like there's much of a problem any more. Yahoo and MSN already link your searches on their respective engines with your account profiles on their respective free email services, and no one seems to care (maybe because no one uses MSN or Yahoo as a search engine these days, but still).

cpfeifer asks: "Russ Miles wrote about going through the pain of setting up his own infrastructure for his OSS project, AspectXML. He asks: 'Are there tools out there that make this process much easier, and perhaps ones that I could take advantage of by moving my own open source project to? Also what experiences have people had with the different community projects?' Should you start up your own gforge server, host it on Sourceforge, or perhaps look to one of the OSS groups like Apache, Codehaus or Tigris?"

eoyount writes "Wired has an interesting story about a really simple idea I wish I had thought of. Transferring large files across the Internet isn't easy for your average joe, but a combination of RSS and BitTorrent technology might just make it easier - Slashdot ran a previous story on the theoretical blending last year." (LegalTorrents is run by the strangely familiar simoniker, who wrote a short piece on the O'Reilly Network about how it was set up, and offers observations on how well the combination fares.) Update: 03/17 21:45 GMT by T : Ernest Miller submits two related postings he's written on RSS+BitTorrent, a combination he calls "broadcatching."

techiemac writes "Dan Geer, who has been mentioned on Slashdot before due to his warnings about Microsoft's "monoculture" has just been written up by AP for his warnings about the widespread use of Microsoft products and the serious security flaws that are being discovered. This story is quickly becomming big news (Yahoo is currently carrying it on their front page). For those who don't know, Dan Greer was fired from @Stake Inc for his criticism of Microsoft (they are a big client of @Stake Inc). " Somewhat related, there has been interesting reaction pieces on ORA and OSDN to a recent, some say ill-informed article run on DevX.

dpilgrim writes "DevX's A. Russell Jones as thrown down the gauntlet, questioning the security of Open Source software. I've picked up the gauntlet and posted a response over on the O'Reilly Network. As previously discussed on /. Jones' comments are too controversial to ignore."

dpilgrim writes "DevX's A. Russell Jones as thrown down the gauntlet, questioning the security of Open Source software. I've picked up the gauntlet and posted a response over on the O'Reilly Network. As previously discussed on /. Jones' comments are too controversial to ignore."

Alexander Limi writes "Just in time for some light weekend reading, O'Reilly's OSDir.com has published a byte-sized interview with the two founders of Plone. This is a nice follow-up to the earlier discussion on Slashdot, and covers a lot of the unanswered questions people directed to us earlier as the surprise winners of the O'Reilly COMDEX competition."

Sam Hiser writes "Open source in government is getting real. Tom Adelstein, in this penetrating interview with Andy Stein, the CIO of Newport News, Virginia, gets to the heart of why the opportunity to build collaborative software pulled the former chief IT architect of Capital One into the public sector. Police, fire and EMT early responders -- and the IT systems that support them - are under Sisyphean pressure to perform, while budgets are sagging. Something's gotta give, and it's going to be the aging software infrastructure in our towns and cities. Are Open Source platforms the only economically viable alternative? Maybe not, but collaboration will have to occur if we want to build the systems to save our lives."

Veeru writes "As mentioned on Nova, my great-great-grandfather Amos Ives Root published the first eye witness account of the Wright Brothers flight almost 100 years ago. Scientific American had rejected his article as 'unbelievable' and 'having no practical application'. The secretive Wright Brothers allowed Amos to publish the article in his own Gleanings Bee magazine instead. Because of his objective account, other experimenters may not have received the credit they deserved. I recently realized that Amos was intent on investigating the highest tech advances of the day and that the airplane was the most advanced phenomenon he could find. If Amos were alive today, what obscure technology would he be pursuing?"

comforteagle writes "O'Reilly Developer News is reporting that SourceForge has begun a donations program for hosted projects in addition to the program which was for supporting the site. Apparently project admins have to opt-in to have the program setup for them, but it sounds like a pretty good idea. There's a 5% transaction fee, but that doesn't sound totally unreasonable. Perhaps a limit would be a good idea though." Sourceforge and Slashdot are both owned by VA Software Corp.

comforteagle writes "O'Reilly Developer News is reporting that SourceForge has begun a donations program for hosted projects in addition to the program which was for supporting the site. Apparently project admins have to opt-in to have the program setup for them, but it sounds like a pretty good idea. There's a 5% transaction fee, but that doesn't sound totally unreasonable. Perhaps a limit would be a good idea though." Sourceforge and Slashdot are both owned by VA Software Corp.

jpkunst writes "A thought-provoking article by chromatic on oreillynet, listing eight "myths" that Open Source developers tell themselves. For example: Myth: Publicly releasing open source code will attract flurries of patches and new contributors. Reality: You'll be lucky to hear from people merely using your code, much less those interested in modifying it."

cold_sake writes "Wireless guru Rob Flickenger details the known records for Wi-Fi link distances on his latest blog. Included is a new distance record for an un-amplified Wi-Fi link, set by the students of Utah's Weber State University. 82 miles was accomplished with 802.11b."

cold_sake writes "Wireless guru Rob Flickenger details the known records for Wi-Fi link distances on his latest blog. Included is a new distance record for an un-amplified Wi-Fi link, set by the students of Utah's Weber State University. 82 miles was accomplished with 802.11b."

theodp writes "The USPTO Director has ordered reexaminations of the infamous Eolas Distributed Hypermedia Method (discussed earlier(1) on Slashdot) and SBC Structured Document Browser (discussed earlier(2) on Slashdot) patents. Maybe this will inspire Tim O'Reilly to get that killer piece of 1-Click prior art off his bookshelf!"