Slashdot Mirror

prostoalex writes "The SCO Group reached an agreement with the lawyers to limit the litigation expenses to $31 million until the IBM lawsuit is resolved. The company already paid $12 million to Boies Schiller & Flexner LLP, Kevin McBride and Berger Singerman, which provide legal services to the company."

Richard Mathias writes "Following on from the posting a month ago, where SCO said it was going to launch a new website to counteract Groklaw and give its side of things - well, now the company looks like it's given up on the whole plan. It was originally supposed to be at Prosco.net, then SCOinfo.com, but both have holding pages and a spokeswoman has said it may never happen at all because of "legal and management concerns"." Update: 11/03 01:10 GMT by T : editingwhiz writes "Despite earlier published reports, SCO Group is indeed still planning to post a lawsuit-information Web site under a new name, SCOinfo.com, company spokesman Blake Stowell told IT Manager's Journal today. So SCO is not throwing in the proverbial towel after all. But does it really make any difference? (IT Manager's Journal is part of OSTG.)"

Simon P. Chappell writes "Linux programming is the C Programming Language. Elaborating a little, Linux programming is C, with the GLIBC library and the POSIX standard API. Even a language as powerful as C needs libraries and to get the Holy Grail of cross-platform portability, it's necessary to have them standardised. The POSIX API is that standardisation and Linux adheres to it very well (opinions from those litigious folks in Utah aside). For those of us who already know C, Linux Programming by Example sets out to teach you the rest in a step by step, helpful, relaxed and incremental manner." Linux Programming by Example author Arnold Robbins pages 687 (21 page index) publisher Prentice Hall rating 10 reviewer Simon P. Chappell ISBN 0131429647 summary An exellent tutorial for real-world Linux software development

What's To Like There are many things to like about this book (over and above the fact that page 118 has my all-time favourite UserFriendly cartoon on it :-). Linux Programming by Example (LinuxPbE hereafter) takes a steady, incremental path through the concepts required to write software that can effectively interact with the Linux environment.

It is a truism many of us have proven multiple times in our lives that one of the finest learning tools available to programmers is to read and grok good, working code, written in the language that we are learning. LinuxPbE takes this philosophy and walks you through actual example code from various Unixes and Linux. The first part of the book, specifically chapters one through six, covers all of the aspects of Linux programming necessary to understand the Unix V7 ls program in its full glory in chapter seven. I feel that this approach works very well.

Part two dives into processes, walking us through creating them, managing them, communicating with them by using pipes and sending them signals. A few other general topics are included for completeness. Part three then covers the art and tools of debugging in fairly substantial detail.

All the code in the book is very well laid out, with line numbers provided to the left, and comments (in a small sans-serif font) on the right-hand side of the code. This is a very readable combination that is enhanced further by the fact that at each logical division, an explanation is given of the design and implementation used by that section.

I can't resist admiring the addition of the essay "Teach Yourself Programming in Ten Years" by Peter Norvig. This is a classic exploration of the effort needed to attain mastery of any skill, concluding that the minimum length of time required is ten years. The inclusion of this article, to me, speaks well of the author and his understanding of the learning process. One can only hope that those learning from this book will come to the same understanding and realise that the book is the start of their journey to mastering Linux programming.

What's To Consider

Nothing notable.

Summary If you want to learn how to do this stuff for real, then this book will get you started. As "Teach Yourself Programming in Ten Years" explains, no book is going to cause you to become an expert in 24 hours, 24 days or even, perhaps, 24 months. That said, this book will be useful for many of those ten years, so run or surf to your favourite bookstore and purchase it now.

You can purchase Linux Programming by Example from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

An anonymous reader writes "A NewsForge story [part of OSDN, like Slashdot] says a court ruling by Judge Brooke C. Wells in the SCO Group vs. IBM intellectual property lawsuit amounting to 'show me the code' was released today in the form of a nine-page document [PDF link]. For a change, the SCO Group had no comment, because Judge Wells told it not to issue any. The judge said SCO is to provide and identify all specific lines of code IBM is alleged to have contributed to Linux from either AIX or Dynix, provide and identify all specific lines of code from Unix System V from which IBM's contributions from AIX or Dynix are alleged to be derived, and provide and identify all lines of code in Linux that it claims rights to."

wes33 writes "Now available at the SCO website, genuine licenses permitting you to use SCO IP that is 'necessary for you to run Linux'. And they take VISA. Looks like they're saying that any code that is similar to Unix code counts as their Unix code!? Actually, the agreement needs analysis. It looks to me that you're paying for a pig in a poke, but IANAL. Here's some of the meat: '"UNIX-based Code'" shall mean any Code or Method that: (i) in its literal or non-literal expression, structure, format, use, functionality or adaptation (ii) is based on, developed in, derived from or is similar to (iii) any Code contained in or Method devised or developed in (iv) UNIX System V or UnixWare(R), or (v) any modification or derivative work based on or licensed under UNIX System V or UnixWare. ... Provided You pay the applicable license fee and complete the required registration of the COLA, SCO grants You the right to use all, or portions of, the SCO IP only as necessary to use the Operating System on each System for which the appropriate CPUs have been licensed from SCO.'" The linked page says this so-called license applies only to commercial use.

A day with SCO is like a day without sunshine, I know that's what you're thinking. Novell is asking the court to dismiss SCO's lawsuit against them. Groklaw has taken a look at what is necessary to prove a 'slander of title' claim. And finally, reader loonix_gangsta wrote in and pointed to SCO's humorous 5 reasons to choose UNIX over Linux webpage.