Slashdot Mirror

Digana writes "GNU Octave is a free numerical computing environment highly compatible with the MATLAB language. After 11 years of development since version 2.0, stable version 3.0 released yesterday. This version is interesting because unlike other free or semi-free MATLAB competitors like Scilab, specific compatibility with MATLAB code is a design goal. This has manifested itself in goodies like better support for MATLAB's Handle Graphics, a syntax closer to MATLAB's own for many functions, and many functions from the sister project Octave-Forge ported to the core Octave project for an enriched functionality closer to the toolboxes provided by MATLAB. GUI development is underway, but still no JIT compiling, which is a show-stopper for Octave newbies coming from MATLAB with unvectorized code."

Digana writes "GNU Octave is a free numerical computing environment highly compatible with the MATLAB language. After 11 years of development since version 2.0, stable version 3.0 released yesterday. This version is interesting because unlike other free or semi-free MATLAB competitors like Scilab, specific compatibility with MATLAB code is a design goal. This has manifested itself in goodies like better support for MATLAB's Handle Graphics, a syntax closer to MATLAB's own for many functions, and many functions from the sister project Octave-Forge ported to the core Octave project for an enriched functionality closer to the toolboxes provided by MATLAB. GUI development is underway, but still no JIT compiling, which is a show-stopper for Octave newbies coming from MATLAB with unvectorized code."

I Don't Believe in Imaginary Property writes "The term NSFW is about to join the :( emoticon, going from a generic, oft-used internet abbreviation, to one company's exclusive trademark. Fark is seeking a trademark on the use of NSFW to describe naughty online content. Of course, they may face a bit of a battle because more than a few other people are already using the term NSFW to describe their products and services. Not that that's stopped anyone in the past." And, of course, the whole thing could be a big practical joke.

An anonymous reader writes "After a long process of review and polishing, the win32 loader from goodbye-microsoft.com has finally made its way to official Debian CDs. Latest daily builds of lenny (the development version) are including it, making starting Debian Installer as simple as just a few clicks (OGG). The win32-loader version, now based on GRUB 2, includes new features such as detection and pre-seeding of Windows settings, and is translated to 20 languages."

larry bagina writes "GCC 4.2.1 was released 4 days ago. Although this minor update would otherwise be insignificant, it will be the final GPL v2 release; all future releases will be GPL v3. Some key contributors are grumbling over this change and have privately discussed a fork to stay as GPL v2. The last time GCC forked (EGCS), the FSF conceded defeat. How will the FSF/GNU handle the GPL 3 revolt?"

A GNU Dawn writes "The GPL v3 has just been released. Among other things, the released version grandfathers in the Novell deal so that Microsoft's SLES coupons will undermine their patent threats, replaces references to the Magnusson-Moss Warranty Act with more specific language, and clarifies that using BitTorrent to convey a GPLed work is not a breach of the license (it might be one, technically, in GPLv2). The GPL FAQ has been updated to cover the new changes." Commentary is available over at Linux.com (which is owned, along with Slashdot, by Sourceforge).

Joe Blakesley writes "Today, the Free Software Foundation announced that version 3 of the GNU General Public License will be released on Friday, June 29 at noon (EDT). Live video footage of the GPL's unveiling by Richard M. Stallman will be available as a stream on the FSF's website."

TimHunter writes "I was skeptical when I first saw the title of David Berube's new book, Practical Ruby Gems, from Apress. Do Ruby programmers really need a book devoted entirely to add-on libraries? Most Ruby programmers already know about the RubyGems package management system, and most already have their set of favorite gems. About a third of the way through the book I grudgingly admitted that Rubyists might be able to use this book. After all, even long-time Ruby programmers are unlikely to know about all the gems covered in this book. So then I had a new question. Would I find something in this book that made me say 'I didn't know you can do that with Ruby!'" Read on for the rest of Tim's review. Practical Ruby Gems author David Berube pages 271 publisher Apress rating 8 reviewer Tim Hunter ISBN 1-59059-811-3 summary A survey of useful and interesting Ruby libraries Ruby is an object-oriented programming language in the same family as Perl and Python. The programming language used by Ruby on Rails, Ruby is very popular for writing web applications but also widely used for general-purpose programming tasks. Ruby is open source with a commercially friendly license, and is available for Linux, Mac OS X, and Microsoft Windows. RubyGems is Ruby's system for managing, delivering, and installing third-party libraries and applications. It is similar to Perl's CPAN or the Python Package Manager.

Libraries distributed by RubyGems are called "gems." RubyForge is the central Ruby software repository and the primary distributor of gems. According to sysadmin Tom Copeland, RubyForge currently hosts about 1400 different gems. Of that number, Berube selected 29 useful and interesting libraries for his survey of "practical" gems. All of the gems described in this book work the same on Linux, OS X, and Windows.

Practical Ruby Gems is divided into three parts. Part 1 describes the RubyGems system itself. This part explains how to install the RubyGems software and then use RubyGems to install and manage individual gems. (RubyGems is not part of Ruby's standard distribution, except in the "one-click installer" for Microsoft Windows.) The section entitled "What is require_gem?" in Chapter 3 demonstrates one of the problems with writing technical documentation for a moving target like RubyGems. Practical Ruby Gems describes RubyGems 0.9.0. After the book went to press the RubyGems team released a new version that replaced the 'require_gem' method with a method called simply 'gem'. Currently all uses of 'require_gem' generate a warning message. (The remedy for this mistake is simple: attach a yellow sticky with the words "s/require_gem/gem/g" to page 20.) This is really a nitpick, though. Generally the text and examples in the book work as well for the new release as they did for 0.9.0.

Part 2 is by far the largest and has a chapter devoted to each of the 29 gems. The chapters in this part share a common structure. After a short introduction to the gem, there is a section entitled "How Does It Work?" which explains the purpose of the gem and how it's used. Frequently this section includes a small example. "How Does It Work?" is followed by a complete example script. Then, "Dissecting the Example" steps through each part of the example, explaining how it works and pointing out important classes and methods. The examples frequently combine two or more gems, such as the example for pdf-writer, which also uses the net-sftp gem, and the example for the mongrel web server gem, which also uses the Camping web micro-framework gem.

The examples — always practical, frequently interesting, at least to a geek like me — are the heart of the book. Berube said that "no one wants to pay to read a chapter that regurgitates [the gem's built-in documentation]....I wanted to write a book that you could take the examples and actually be interested in what they accomplished." For instance, Chapter 6 describes the BlueCloth text-to-HTML conversion gem. The example in this chapter is a script that converts lightly marked-up text to PDF by combining BlueCloth with html2ps and ghostscript. Chapter 12 describes the yahoofinance gem, a library for retrieving stock quotes using the Yahoo! Finance API. The example for this library combines yahoofinance with the fxruby GUI library to produce a rudimentary stock ticker in less than 100 lines of code. (The source code for all of the examples in the book can be downloaded from the Apress web site.)

But not every example is perfect. Several of the examples rely on MySQL, which I found a chore to install. I wish Berube had chosen a simpler data base for these examples. I never did get the Camping example to run successfully. I suspect the problem was caused by some change to a gem introduced after the book went to press.

In Chapter 22 I got my "you can do that with Ruby?" moment. This chapter explains runt, a Ruby library for creating "temporal expressions," objects that describe dates that reoccur, such as "every Thursday" or "the last Thursday of every month." The example combines runt with linguistics, a small gem that extends some of the Ruby core classes with methods that support such things as pluralization and conversion from numbers to words. The result is a program that lists a set of dates expressed as "the 3rd Mondays of 2026." I was impressed by both gems, not only for the functionality they provide but by their natural and elegant interfaces as expressed in the example script. I not only learned about two very practical Ruby gems, but something about Ruby programming itself. This particular example may not strike everybody the way it did me, but I believe that most readers will find an equally pleasant surprise.

Part 3 is a tiny, advanced topics section which describes how to create and distribute your own Ruby gems and how to run a private gem server on a local network.

Practical Ruby Gems is not for the novice. Berube assumes that his reader is familiar with programming in general and Ruby specifically, and is also familiar with the operating system in which Ruby is running. This is an appropriate assumption because Practical Ruby Gems will be most useful to readers who are serious about programming Ruby, such as professionals or serious amateurs, or those would like to become professionals or serious amateurs.

Practical Ruby Gems is available in PDF format from the Apress web site at about half the price of the paper book.

I have been programming Ruby as a hobby for over 5 years. I am the maintainer of RMagick, one of the gems reviewed in this book. Apress gave me a review copy of Practical Ruby Gems, but otherwise I have no connection to the author or publisher.

You can purchase Practical Ruby Gems from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

H4x0r Jim Duggan writes "The first recorded talk by Richard Stallman on free software was in 1986, so I've picked from the 2006 recordings and have made a transcript of a recent talk: The Free Software Movement and the Future of Freedom. Those two are the only transcripts of his general free software talk. Others that exist are on specific topics such as patents, GPLv3, copyright, etc. For those who've been reading Slashdot during the gradual evolution of Stallman's pronouncements, it's interesting to see what has changed over 20 years."

kmaclean writes, "VoxForge collects free GPL Transcribed Speech Audio that can be used in the creation of Acoustic Models for use with Open Source Speech Recognition Engines. We are essentially creating a user-submitted repository of the 'source' speech audio for the creation of Acoustic Models to be used by Speech Recognition Engines. The Speech Audio files will then be 'compiled' into Acoustic Models for use with Open Source Speech Recognition engines such as Sphinx, HTK, CAVS and Julius." Read on for why we need free GPL speech audio.

Why free GPL Speech Audio?

Speech Recognition Engines require two types of files to recognize speech. The first is an Acoustic Model, which is created by taking a very large number of audio recordings of speech and their transcriptions (called Speech Corpus or Corpora) and 'compiling' them into statistical representations of the sounds that make up each word. The second is a Language Model or Grammar file. A Language Model is a very large file containing the probabilities of certain sequences of words. A Grammar is a much smaller file containing sets of predefined combinations of words.

Most Acoustic Models used by 'Open Source' Speech Recognition engines are 'closed source'. They do not give you access to the speech audio (the 'source') used to create the acoustic model, or if they do, there are licensing restrictions on the distribution of the 'source' (i.e. you can only use it for personal or research purposes). The reason for this is because there is no free Speech Corpora in a form that can readily be used to create Acoustic Models for Speech Recognition Engines. Open Source projects are required to purchase Speech Copora which has restrictive licensing — i.e. they are not permitted to distribute the 'source' speech audio, but they are permitted them to distributed the 'compiled' Acoustic Model.

Why GPL?

A GPL-style license will ensure that user contributions will always benefit the open source community, since it requires any distribution of derivative Acoustic Models to include access to the 'source' speech audio.

An anonymous reader writes "Debian's cdrecord maintainers announced that they have had enough of Jörg Schilling and kicked his program suite cdrtools out of Debian, introducing a free fork of his no longer free cdrtools." I've put the message below, along with some other links. So, why the fork? CD/DVD burning is a complicated business that needs a lot of knowledge, so forking such a big collection isn't a step to be taken lightly. It requires a lot of development effort that could be put to better use elsewhere.

In the past, we, the Debian maintainers of cdrtools, had a good and mutually cooperative relationship with Jörg Schilling. He even commented on Debian bug reports, which is one of the best things an upstream maintainer can do. Naturally, there were occasionally disagreements, but this is normal.

Unfortunately Sun then developed the CDDL and Jörg Schilling released parts of recent versions of cdrtools under this license. The CDDL is incompatible with the GPL. The FSF itself says that this is the case as do people who helped draft the CDDL. One current and one former Sun employee visited the annual Debian conference in Mexico in 2006. Danese Cooper clearly stated there that the CDDL was intentionally modelled on the MPL in order to make it GPL- incompatible. For everyone who wants to hear this first-hand, we have video from that talk available.

Here is the FSF position about the CDDL. This thread contains statements on the issue made by Debian people; for more context also see the other mails in that thread. In short -- the CDDL has extra restrictions, which the GPL does not allow. Jörg has a different opinion about this and has repeatedly stated that the CDDL is not incompatible, interpreting a facial expression in the above-mentioned video, calling us liars and generally appearing unwilling to consider our concerns (he never replied to the parts where we explained why it is incompatible). As he has basically ignored what we have said, we have no choice but to fork. While the CDDL *may* be a free license, we never questioned if it is free or not, as it is not our place to decide this as the Debian cdrtools maintainers. However, having been approved by OSI doesn't mean it's ok for any usage, as Jörg unfortunately seems to assume. There are several OSI-approved licenses that are GPL-incompatible and CDDL is one of them. That is and always was our point.

For our fork we used the last GPL-licensed version of the program code and killed the incompatibly licensed build system. It is now replaced by a cmake system, and the whole source we distribute should be free of other incompatibilities, as to the best of our current knowledge.

Anyone who wants to help with this fork, particularly developers of other distributions, is welcome to join our efforts. You can contact us on IRC, server irc.oftc.net, channel #debburn, or via mail at debburn-devel@lists.alioth.debian.org. Here is our svn repository.

A reader writes:"The Official Ubuntu, Kubuntu and Xubuntu 6.06 Desktop Guides, the Official Ubuntu Server 6.06 Guide and the Official Ubuntu Packaging Guide are all now available in print from on-line publisher Lulu. The best part? All of these guide are cheap, in fact the only cost is that of manufacture and shipping, both Canonical and Lulu do not make any profit on the books at all. The Official Ubuntu Desktop Guide for example only costs $6.49 plus postage and contains 98 pages in total. Free downloadable PDF files are available for download on the Ubuntu Documentation Project Lulu website as well as on-line copies at http://help.ubuntu.com. All of the guides are available in many different languages thanks to the Ubuntu Translation Teams. Currently there are about 10 different languages available, more translations will be added to the store as they are compleated in Canonical's on-line project management web site Launchpad. All the guides are dual licenced under the GFDL and Creative Commons Attribution-ShareAlike licences. This is a really good idea to give Linux users cheap and reliable printed Linux manuals. Lets hope other distributions follow Ubuntu's lead on this one, some of the Gentoo manuals for example available in print this cheap would be really great to see."

bcrowell writes "The New York Times reports that textbook publishers are backing off somewhat on the level of DRM used in the electronic editions of their textbooks. They no longer become unreadable after a certain amount of time, as in RMS's famous essay The Right to Read. Even so, most students aren't interested, because the books can't be sold back; the solution, however, may be to make it impossible to return printed books either. No mention in the NYT article of the steady progress being made by free books."

An anonymous reader writes "If you've not heard much about Emacs development in recent years, you might be surprised to find that it is has been very active. Emacs 22 will have many new features such as support for Mac OS X and Cygwin; mouse wheel support and many new modes and packages. It can also be built with Gtk+ widgets and supports drag and drop for X. The NEWS file details all the changes. Although its very stable, don't expect to see it released any time shortly because according to RMS, the Emacs developers haven't been fixing bugs quickly enough. Those who have followed Emacs for long enough might see a different pattern."

An anonymous reader writes "If you've not heard much about Emacs development in recent years, you might be surprised to find that it is has been very active. Emacs 22 will have many new features such as support for Mac OS X and Cygwin; mouse wheel support and many new modes and packages. It can also be built with Gtk+ widgets and supports drag and drop for X. The NEWS file details all the changes. Although its very stable, don't expect to see it released any time shortly because according to RMS, the Emacs developers haven't been fixing bugs quickly enough. Those who have followed Emacs for long enough might see a different pattern."

Justin Baugh writes "The Free Software Foundation and the Software Freedom Law Center have released a document detailing the guidelines and the process that will be used for revising the GNU GPL, and have launched a new website related to the V3 process. It was announced in a press release this morning that the FSF will be releasing the first discussion draft of the new license for comments at the International Public Conference for GPLv3 at MIT on January 16 and 17, 2006."

Luineancaion writes "Looks like GCC 4.1 has been released. From what I know this includes the GNU Classpath merge and means that Azureus can now be used in a 100% Free-Software system. Thanks to everyone that worked on it, and keep up the good work!"

bluefoxlucid writes "Security has been a hot topic lately, and we've seen everything from changes to how memory is managed to compiler hardening to "secure" programming languages. Java is considered more secure than C in general; but this guy seems to disagree, and thinks hardening the system itself is the way to go. Are we really approaching the problem the wrong way, or is he just insane?"

barryhawkins writes "It's safe to assume that people who are thinking of learning GNU Emacs or improving their Emacs skills are motivated. These people probably know their way around a command prompt, and likely know that Lisp is more than just a speech impediment. They need a book that offers expert advice without wasting time or insulting the intelligence of the reader: Learning GNU Emacs, 3rd Edition is that book." Read on for the rest of Hawkins' review. Learning GNU Emacs, 3rd Edition author Debra Cameron, James Elliott, Marc Loy, Eric Raymond & Bill Rosenblatt pages 534 publisher O'Reilly Publishing rating 9 reviewer Barry Hawkins ISBN 0596006489 summary An intelligent, graded treatment of the landscape of useful Emacs skills and how to internalize them

For a programmer, it is reasonable to question whether or not a word processor or graphical IDE is the right tool to edit a simple script or properties file. IDEs like Eclipse have become universals hammers, and to some of their users, any file containing text looks like a nail. Specific tasks are rarely handled well by universal tools, and text editing is no exception. Dave Thomas and Andy Hunt, authors of The Pragmatic Programmer and founders of the Pragmatic Bookshelf series, recommend that programmers adopt a text editor as an essential utility in their collection of appropriately-suited tools. The tried-and-true text editor is enjoying a renaissance of sorts, and one of the most extensible and customizable applications among text editors is the venerable GNU Emacs.

Tutorials and documentation for Emacs are abundant, but they often prove time-consuming and ineffective for actually learning Emacs. The printed version of the official GNU Emacs manual reads more like an application programming interface (API) document than an instructional guide. This book is a refreshing break from the documentation many have come to expect. Imagine having a group of leading experts on Emacs at your disposal to teach you how to use it in a conversational, consultative style. That is what has been bundled into this book.

The extensibility of Emacs is considered both a key strength and a confusing weakness of the application. The Emacs community has created all sorts of additional capabilities for Emacs, ranging from the impressive to the absurd. The authors have done well to judiciously select which Emacs capabilities to cover. For example, while Emacs does have the capability to function as an email client, other applications have long superseded its ability. The authors have chosen not to cover this topic, and instead devote the available space to learning Emacs' core functionality -- powerful, efficient text editing.

This edition of the book uses the space gained by the removal of esoteric topics to flesh out areas of more common interest. Peripheral areas of Emacs, such as compatibility modes for programming languages (other than Java and Perl), have been left for the user to research after gaining a solid foundation on Emacs as editor and work environment. Integration with the major version control systems has been expanded to include Subversion alongside the age-old standards CVS, RCS, and SCCS. Coverage of support for Java and Perl has also improved, as well as sections for editing HTML and XML. Users wanting to tap into the power of Lisp programming for Emacs should find the coverage satisfying as well.

The pace of the material is comfortable, and the order in which topics are introduced allows the user to progress smoothly through the book. Users with some experience can skip past the first three chapters, but would be advised to read through them, particularly those who are self-taught (which applies to most Emacs users). Given the amount of time the average user spends in Emacs, picking up one or two time-saving shortcuts would be well worth an investment of a few hours. Instructions are given in a way that reflects the fact that there are multiple ways to achieve the same outcome; the authors do not attempt to foist "the only way" to accomplish something upon the reader. Some readers will find that bothersome, desiring instead a simple, straightforward heuristic for performing a task. However, the typical users of Emacs tend to be people who embrace the fact that the world is not a simple, straightforward abstraction. The book reflects the authors' awareness of this nuance.

Perhaps the most distinguishing feature of this book is the chapter devoted to the use of Emacs on different platforms. Unix, Windows and Mac OS X users receive equal acknowledgment. The precautions and insights regarding subtle differences in Emacs when used on particular platforms can reduce users' frustration when getting started.

The mnemonic devices and conventions used in the book allow users to commit useful keyboard commands to memory. The memorization is further solidified by the exercises sprinkled appropriately through each chapter. Readers do not go for very many pages before it is time to be at the keyboard again, harnessing the power of muscle memory to reinforce the material presented. Those who spend any time at a shell prompt or in console applications will find that their new mastery of Emacs keyboard shortcuts translates into increased proficiency with command-line operations as well.

You can purchase Learning GNU Emacs, 3rd Edition from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Phil Shapiro writes "The popular open source content management system named Mambo has changed its name to Joomla! -- released under the GNU Public License. Some of the reasons for the name change are explained at MamboPortal.com. Joomla! is used by a very wide array of organizations and companies."

You may recognize the name Jonathan Zdziarski from a recent Slashdot book review of his book Ending Spam. Aside from his DSPAM spam filter Jonathan has also contributed several other projects to the open source community under the GNU General Public License. These projects include Verizon-Compatible SMIL Multimedia Gateway, The Reactive Automated Blackhole List Server, Apache DoS Evasive Maneuvers Module, and several others. Want to know how to effectively contribute projects to the open source community? Curious to ask another programmer about his history? Now is the time to ask. Moderators will select the top few questions that we will forward on to Jonathan sometime tomorrow. The answers to the questions will be displayed next Tuesday when we will encourage Jonathan to participate in the discussion as time permits.

jakobgrimstveit asks: "At work I've been developing an intranet/extranet portal framework in PHP based on many other peoples work, including quite a few PEAR modules. I've always wanted to release the coding framework as GPL and publish it on SourceForge, and my boss has - impressively enough - not been too negative about this. This has been going around in the organization for quite a while now, and finally the reply from the company's president was (not surprisingly): 'Why should we do so?' I now have the task of writing a document listing the main reasons for GPLing the code, and this is where I turn to the highly competent Slashdot crowd: How do I convince my bosses to GPL the code I've written? I assume many other developers have the same problems trying to convince their bosses to open up their code."

The Free Software Foundation has posted a call for nominations for their 2005 Award for the Advancement of Free Software. Last year's winner was Theo de Raadt. Previous winners are ineligible, so who's left who hasn't already won?

pankaj_kumar writes "Apache Ant, the Java replacement for make , belongs to the rare breed of category killer software for automating Java software development tasks. It is an Apache open source project, has won numerous awards, boasts comprehensive online documentation and is used by most Java developers. So, what could a book say that is already not available online?" Read on for Kumar's review of Ant: The Definitive Guide. Ant The Definitive Guide author Steve Holzner pages 316 publisher O'Reilly rating 8 reviewer Pankaj Kumar ISBN 0596006098 summary Complete Build Management for Java with Ant

As a long time Ant user, I have written many Ant build scripts, automating my builds and speeding up the overall development cycle, mostly relying on its excellent online documentation. As a Java developer, I have admired its simple and intuitive interface and the modular design. So on getting Ant: The Definitive Guide in my hands I wasn't expecting a whole lot new to learn, and thought of using it only as a reference book.

After having the book on my desk for more than a month, though, and occasionally flipping through its pages whenever I would otherwise have consulted the online documentation, I must say that I had been missing out on some very important things: tasks like ftp and war deployment that I was simply not aware of and had never felt the need to look up, but could very well use. The other interesting thing I noticed was that my build scripts became smaller, more modular and easier to read.

Like most books in the The Definitive Guide series, Ant The Definitive Guide assumes a certain level of familiarity with underlying technologies such as Java and XML and focuses on providing complete, reference like details of Ant features and tasks. These description are generously supplemented with examples and code fragments.

But so is the the online documentation for Ant! Will someone gain additional insight in using Ant, or be able to work faster, or make better use of Ant capabilities, by consulting this book, instead of the online documentation for a particular Ant task? To find the answer, I randomly picked two topics -- filesets, an important and oft-used Ant datatype, and javac, a core Ant task -- and compared their online description with the one in the book. Here is what I found.

Besides the datatype definition, explanation of various attributes, sub-elements, and the examples, the book also covers how to specify conditional inclusion or exclusion of certain filename patterns when a property is set (or unset). Though this can be inferred from online documentation by a determined user, this particular use is far from obvious. The coverage in the book also talks about the relationship of the fileset datatype with the javac task, pointing out that the fileset attribute dir is equivalent of javac attribute srcdir, as attribute dir will be confusing in javac: is it referring to source directory or destination directory. This is the kind of insight that really helps a user.

The treatment of the javac task in the book is not much different from the one in the online documentation. Both have almost the same material, though the information in the book is better organized for new users. On the other hand, I found the online documentation to be more complete, especially with respect to the compiler specific options and behavior idiosyncrasies.

Here is a rundown on what the book covers: Chapter 1, Getting Started is a quick primer on Ant, with sufficient details for a new user to start using Ant for very simple build tasks. Chapter 2, Using Properties and Types introduces the building block tasks and datatypes, such as property, condition, fileset, path like structures, selectors and so on, used in other Ant tasks. Chapter 3, Building Java Code covers the tasks and activities around compiling Java source files (ie; javac), organizing the build steps in various targets within a single build scripts and/or across multiple scripts, generating documentation using javadoc and creating distribution jars and zip files. The rest of the chapters are devoted to tasks for specific purposes, such as launching external programs (Chapter 7, Executing External Programs), copying files and manipulating directories either on the same machine or over the network (Chapter 4, Deploying Builds), running JUnit tests (Chapter 5, Testing Builds with JUnit) and so on. There are also separate chapters covering interaction of Ant with XML and XDoclet (Chapter 9, XML and XDoclet) and with Eclipse (Chapter 11, Integrating Ant with Eclipse). The last chapter, Chapter 12, Extending Ant, talks about extending Ant by doing things like adding your own tasks, creating custom filters, writing your own build listeners and loggers etc. This chapter also has a small section on how to embed a script written in one of the supported scripting languages within an Ant script.

As you can see from this outline, the book covers almost everything that is to know about Ant and other related software.

So, what is not so good about this book? Well, I didn't find anything wrong with the topics which are actually covered by the book. Of course, there are additional things that I would have liked to see in the book: (a) A good sample Ant script which could be used as the starting point for most small to medium-sized projects; (b) A more thorough explanation of how dependencies among targets determine the execution sequence and how this fits in with explicit invocation of targets; and (c) pictures to illustrate some of the concepts such as life cycle of an Ant task, selection of files in a fileset and the dependency tree of targets.

Overall, I found the book to be comprehensive, well organized, easy to read and good value for money.

You can purchase Ant: The Definitive Guide from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

martin-boundary writes "The typical Bayesian spam filters learn to distinguish ham from spam just by reading thousands of emails, but is this all they can do? This essay shows step by step how to teach a Bayesian filter to play chess against a human, on Linux, with XBoard."

caseykoons writes "While I understand the /. crowd is likely to be biased, I am curious. Has Apple's decision to switch to Intel Chips lost the company some of its old supporters? I have used Macs since I grew up, was a loyal 'Mac Evangelist' back in the '90's, but the company's decision and the recent connection to Trust Computing have had me wondering if I will stick with the old Apple from now on. What are your thoughts?"

Slashback tonight brings some corrections, clarifications and updates to previous Slashdot stories, including word from the worlds of corporate patent lawsuits, secretive publishers vs. inquisitive readers in Canada, and the pitiful teachers versus the splendid kids in Pennsylvania. Read on for the details. Sir, this sentence mangling machine is Pl88^74djliivc33mq again! I posted a story earlier this week which scrambled in its summary the facts of the matter. My post, as reader Raymond Fingas points out, said that the "Internet archive ... has been sued by the firm Harding Earley Follmer & Frailey." Fingas was one of several readers (thanks to all!) to correct me on this, writing "According to the linked article that isn't the case; instead they are being sued by Healthcare Advocates, represented by the firm McCarter & English. Further, the article says that Harding Earley Follmer & Frailey is actually being sued along with the Internet Archive.."

Alacritech settles litigation with MSFT and BRCM An anonymous reader writes "Alacritech, Microsoft Corporation and Broadcom Corporation today announced that they have entered into agreements that settle all outstanding disputes between Alacritech and Microsoft, as well as provide Microsoft and Broadcom access to Alacritech's patent portfolio relating to scalable networking. (Previously mentioned on Slashdot here and here.)"

Sir, you have no right to read about your rights. Hobart writes "Richard Stallman has just posted on his personal website a request for his readers to 'Don't Buy Harry Potter Books,' and offered to leak the plot - in protest of the Canadian Supreme Court ruling forbidding the purchasers from reading the books they paid for. A memorable quote in the Times article says '...There is no human right to read.'"

Don'tcha think felony is a bit strong for a few button presses? ZombyHero writes "In a follow-up to a previous story, the 13 high school students from Kutztown, PA charged with felony computer trespassing for violating district usage policy are fighting back. They've hired lawyers have begun talking with the Assistant DA. As a former student of the school, I know that the district is used to getting its way. Hopefully this will knock them down a few notches."

Starship Exeter flies again! An anonymous reader writes "There's a new episode of Starship Exeter, a fan-made feature set in the original series Star Trek universe. The new episode, The Tressaurian Intersection, follows on from The Savage Empire, which was featured on Slashdot before. This time it's better than ever... better than the original series, in fact! You can watch the entire episode online."

Treasure hunts, commence. We've posted quite a few interesting applications for Google's mapping service; now phauly writes "I created an Animated Google Map (with some gnus and mozillas attacking Microsoft office) using Google Maps API. I think it would be easy to create real playable Games on Google Maps. For sharing ideas (and implementations!) I created the Games on Google Maps wiki page. For now some ideas are: risk, freeciv, freecraft, car races on real maps! Feel free to edit the page suggesting/revising/implementing ideas."

RMX writes "The Telegraph has a nice article about the steps that Scholastic is taking to protect the content of the print version of Harry Potter and the Half-Blood Prince. They're delivering 10.8 million copies and need to ensure that this content isn't accessable by anyone before midnight. Technology includes high-tech (GPS to monitor delivery trucks progress and check that they did not deviate or stop.), low-tech (steel boxes & locks), social engineering notes (crates stacked up in the warehouses of delivery companies across America are marked: Please Do Not Open Before Midnight), and legal threats (As a final layer of security, booksellers have been forced to sign legal forms acknowledging that if they break the embargo, they will never again be supplied with a book by Scholastic). Think how much cheaper and easier it would be if they just used an E-book s with DRM. I'm all for Harry Potter protecting his rights; but it seems we keep getting closer and closer to the world described in Stallman's visionary The Right To Read article."

mopslik writes "Amazon.com is nearing its 10-year anniversary. "Soon after Amazon.com Inc. debuted 10 years ago, Jeff Bezos and his handful of employees spent late summer nights packing books in a tiny warehouse, scrambling to ship a growing gush of orders. Today, the man who has grown accustomed to being hailed the king of Internet commerce runs a global powerhouse that did nearly $7 billion in sales last year, dealing in everything from banjo cases to wild boar baby back ribs." Although Bezos has drawn some ire from his collection of patents, there's no arguing that his company is one of the most successful online sites today."

Software Illustrated asks: "When publishing books on how to use Linux desktop software, the legal/IP review process to make sure we aren't infringing on the property rights of 3rd party sources should be easier than for books about proprietary/closed source software, right? Microsoft makes it easy as long as you comply with their guideline. I didn't think it would be necessary to get permission to publish a screenshot of, for instance, the GNOME gconf-editor. But that is just what our legal/IP review team is pursuing. Is this necessary?" "If not, then how do you explain to a by-the-book contract administrator that the rules are different with GNOME? I find myself dealing with exactly this problem right now, resulting in a book ready for publication being put on hold. Is the solution here to get GNOME (and KDE for that matter) to publish their own permission guidelines ala Microsoft? Seems counterintuitive to the spirit of the F/OSS movement. But doing this sure would grease the skids for publishers. Has anyone else dealt with this issue?"

busfahrer writes "Version 4.0.0 of the GNU Compiler Collection has been released. You can read the changelog or you can download the source tarball. The new version finally features SSA for trees, allowing for a completely new optimization framework." The changelog is pretty lengthy, and there's updates for every language supported from Ada to Java in addition to the usual flavors of C.

busfahrer writes "Version 4.0.0 of the GNU Compiler Collection has been released. You can read the changelog or you can download the source tarball. The new version finally features SSA for trees, allowing for a completely new optimization framework." The changelog is pretty lengthy, and there's updates for every language supported from Ada to Java in addition to the usual flavors of C.

busfahrer writes "Version 4.0.0 of the GNU Compiler Collection has been released. You can read the changelog or you can download the source tarball. The new version finally features SSA for trees, allowing for a completely new optimization framework." The changelog is pretty lengthy, and there's updates for every language supported from Ada to Java in addition to the usual flavors of C.

Alexis Boulva writes "Tonight, Ole André Vadla Ravnås of the Farsight project (LGPL), which 'is an audio/video conferencing framework specifically designed for Instant Messengers' for the GNU Linux operating system, finished coding a release candidate of libmimic, 'an open source video encoding/decoding library for Mimic V2.x-encoded content (fourCC: ML20), which is the encoding used by MSN Messenger for webcam conversations.' Ole, on the libmimic site, remarks that 'It should be noted that reverse-engineering for interoperability is 100% legal here in Norway (and in most European countries).' Looks like the Free/Open Source Software movement is very close to closing up one of the most noticeable software gaps remaining from its glorious efforts."

wikinerd writes "A few years ago when the GNU OS was almost complete, the kernel was the last missing piece, and most distributors combined GNU with the Linux kernel. But the GNU developers continued their efforts and unveiled the Hurd in 1990s, which is currently a functioning prototype. After the Mach microkernel was considered insufficient, some developers decided to start a new project porting the Hurd on the more advanced L4 microkernel using cutting-edge operating system design, thus creating the Hurd/L4. Last February one of the main developers, Marcus Brinkmann, completed the process initialization code and showed a screenshot of the first program executed on Hurd/L4 saying 'The dinner is prepared!' Now he has granted an interview about Hurd/L4, explaining the advantages of microkernels, the Hurd/L4 architecture, the project's goals and how he started the Debian port to Hurd."

wikinerd writes "A few years ago when the GNU OS was almost complete, the kernel was the last missing piece, and most distributors combined GNU with the Linux kernel. But the GNU developers continued their efforts and unveiled the Hurd in 1990s, which is currently a functioning prototype. After the Mach microkernel was considered insufficient, some developers decided to start a new project porting the Hurd on the more advanced L4 microkernel using cutting-edge operating system design, thus creating the Hurd/L4. Last February one of the main developers, Marcus Brinkmann, completed the process initialization code and showed a screenshot of the first program executed on Hurd/L4 saying 'The dinner is prepared!' Now he has granted an interview about Hurd/L4, explaining the advantages of microkernels, the Hurd/L4 architecture, the project's goals and how he started the Debian port to Hurd."

Meostro asks: "I'm looking for the best format to use to distribute arbitrary datasets. Tarballs compressed with gzip seem to be the most common thing out there, with zip coming in a close second. What advanced compression packages are the most widely recognized or available on the widest array of systems? Cross-platform compatibility is my most important goal, followed by compression ratio, decompression time, compression time and extra features (solid archives, support for multiple files, etc.). I'm starting up a free data site to provide test data for anything you can imagine: images for compression and format interpretation, text and audio for language processing, programming language examples to test parsing, and more. I hope this will grow to be a significant (read: multi-gigabyte) archive, so I want to start off right with my distribution format. Right now the plan is data.tar.bz2, but i'm open to anything that will give me better compression as long as it's available for Linux, Windows and Mac."

flyboy writes "In a similar vein to the remakes of the Origin's Ultima series games reported in 2001 and 2004 a group of Wing Commander fans has remade Wing Commander: Privateer. Unlike the Ultima remakes, the Privateer remake is finished at version 1.0 with 3d graphics and the whole storyline. For the new kids on the block, WC:Privateer was a much loved trading game similar to the more venerable Elite, which appears also to be in the process of a remake. As a linux fan I was most happy with the remake's use of GPL 3d engine software and release of Linux, Macintosh and Windows versions. See Screenshots here."

heretic9 writes "The European Parliament unanimously rejected the software patent bill recently put before it. Hugo Lueders of CompTIA, a pro-patent lobby group, said that the benefits of the bill had been obscured by special interest groups, which muddied debate about the rights and wrongs of software patents." Meaning, essentially, that the Conference of Presidents got its way.

Noksagt writes "Various outlets report that the OSI may cut down the increasing number of Open Source licenses. Right now there are about 50 approved licenses; incompatible licenses confuse and impede developers and end users alike. The OSDL has been pushing hard for this at LinuxWorld. Sam Greenblatt, a member of the OSDL board, said 'Eventually there should be three licenses: The GPL, a commercial version of the GPL, and, of course, there will be the BSD because you can't rid of it.'"

ndogg asks: "Many have said that there is a lack of innovation in OSS software, and tend to talk about the big projects, like Mozilla and the Linux kernel. However, I would contend that innovation is quite abound in OSS, but that the problem is the spotlight is rarely shown upon those projects that are truly innovative. For example, I would contend that Data Display Debugger (DDD) and The Boost C++ Libraries are quite unique and innovative projects. What OSS projects do you feel are innovative, but underapreciated?"

wikinerd writes "The GNU Project was working on a new OS kernel called HURD from 1990, using the GNU Mach microkernel. However, when HURD-Mach was able to run a GUI and a browser, the developers decided to start from scratch and port the project to the high-performance L4 microkernel. As a result development was slowed by years, but now HURD developer Marcus Brinkmann made a historic step and finished the process initialization code, which enabled him to execute the first software on HURD-L4. He says: 'We can now easily explore and develop the system in any way we want. The dinner is prepared!'"

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.

Roblimo writes "'There are a lot of good reasons to like the GPL: the GNU Public License. For one thing, it's a David and Goliath kind of thing. It's the little guy standing up to the corporate behemoths that run rough-shod over our daily lives by virtue of their influence, legal and otherwise, on government. For another, it's virtuous.' These are the opening words to a NewsForge article praising the GPL by Joe Barr. Now and then we forget how much of the software we use and love is made possible by the General Public License. Thanks for reminding us, Joe. (NewsForge and Slashdot are both owned by OSTG.)"

lkcl writes "The Open Group announced 12th January 2005 that they are releasing DCE/RPC 1.2.2 as a Free Software Project - under the LGPL. This is a major coup for Free Software: the Distributed Computing Environment is known to be involved in some major projects. There is a mirror at opendce.hands.com which runs rsync, ftp, and there is also a dce122.tar.bz2.torrent bittorrent running as well."

lkcl writes "The Open Group announced 12th January 2005 that they are releasing DCE/RPC 1.2.2 as a Free Software Project - under the LGPL. This is a major coup for Free Software: the Distributed Computing Environment is known to be involved in some major projects. There is a mirror at opendce.hands.com which runs rsync, ftp, and there is also a dce122.tar.bz2.torrent bittorrent running as well."

brlcad writes "After 20 years of active development under a proprietary government license agreement, the BRL-CAD solid modeling suite has just been released as Open Source software. BRL-CAD is one of the many legacies of the late Michael Muuss, author of ping. The package began on the PDP-11 and VAX 11/780--before the emergence of ANSI/ISO C language standards--and boasts one of the first parallel Ray tracers in existence. Today BRL-CAD has over 750,000 lines of source code. It incorporates both 3D modeling and rendering capabilities, and supports an API for user-developed geometric analysis applications. It continues to be developed and maintained by the U.S. Army Research Laboratory and its partners. Various portions of the package are distributed under the GPL, LGPL, GFDL, and BSD licenses."

brlcad writes "After 20 years of active development under a proprietary government license agreement, the BRL-CAD solid modeling suite has just been released as Open Source software. BRL-CAD is one of the many legacies of the late Michael Muuss, author of ping. The package began on the PDP-11 and VAX 11/780--before the emergence of ANSI/ISO C language standards--and boasts one of the first parallel Ray tracers in existence. Today BRL-CAD has over 750,000 lines of source code. It incorporates both 3D modeling and rendering capabilities, and supports an API for user-developed geometric analysis applications. It continues to be developed and maintained by the U.S. Army Research Laboratory and its partners. Various portions of the package are distributed under the GPL, LGPL, GFDL, and BSD licenses."

brlcad writes "After 20 years of active development under a proprietary government license agreement, the BRL-CAD solid modeling suite has just been released as Open Source software. BRL-CAD is one of the many legacies of the late Michael Muuss, author of ping. The package began on the PDP-11 and VAX 11/780--before the emergence of ANSI/ISO C language standards--and boasts one of the first parallel Ray tracers in existence. Today BRL-CAD has over 750,000 lines of source code. It incorporates both 3D modeling and rendering capabilities, and supports an API for user-developed geometric analysis applications. It continues to be developed and maintained by the U.S. Army Research Laboratory and its partners. Various portions of the package are distributed under the GPL, LGPL, GFDL, and BSD licenses."

chronicon writes "Knowing Knoppix is a beginner-friendly, 134 page freely downloadable book (released under the GNU Free Documentation License in PDF format) designed to familiarize new users with the Knoppix LiveCD distribution, GNU/Linux in general, and (as listed first on the description) Windows disaster recovery using Knoppix."