norburym writes with a review of Wicked Cool Shell Scripts - 101 Scripts for Linux, Mac OS X, and UNIX Systems. "This incredibly fun book (really!), written by Dave Taylor, a veteran UNIX, Solaris and Mac OS X author, is chock full of 101 scripts to customize the UNIX (Bourne) shell." Read on for the rest.

cdlu writes "Wondering about SCO's contractor S2? They're the people that wrote Halloween II and indemnified SCO... well, here's all you want to know about them from NewsForge." (NewsForge is part of OSDN.) Maybe not all you want to know, but enough for one day. Several readers also point out Bruce Perens' column on CNET today which reiterates the difficulty SCO faces in attempting to get past the clarification of license terms AT&T offered Unix licensees in 1985.

LukePieStalker writes "TheStreet.com is running a story by Ronna Abramson that makes a case for Linux cutting into Microsoft's server business and forcing Redmond to trim margins. A particular vulnerability is seen in overseas markets, but the heat should be turned up everywhere once Unix replacements are pretty far along by then end of next year. A quote from one CTO: [Linux is] "going to force Microsoft to spend more time on security and stability, and less time on adding new features.""

Peter Wayner writes with a review of O'Reilly's Security Warrior: "Close the doors and they come in the windows. Bar the windows and they slip through some cracks in the foundation. Seal those up and the find another way in through the door. Computer security is an odd pursuit because it's just not possible to have a strong, theory of everything when cracks can appear anywhere. Into this field comes Security Warrior, a book on the topic with a wide ranging collection of tidbits and suggestions on sealing as many holes as you can find." Read on for the rest.

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."

An anonymous reader writes "News.com reports that SCO has filed the first (of two) soon to be infamous lawsuits. This one is aimed against car part retailer AutoZone, a multi-billion, Fortune 500 company according to the site. Who's next?" Another reader excerpts from SCO's posted claim: 'AutoZone violated SCO's UNIX copyrights by running versions of the Linux operating system that contain code, structure, sequence and/or organization from SCO's proprietary UNIX System V code in violation of SCO's copyrights.' Update: 03/03 16:28 GMT by T : njan writes with the news that SCO just announced during their ongoing conference call another lawsuit, this one "to be filed against Daimler-Chrysler, alleging that they are infringing SCO's copyright by using code relating to 'core operating system functionality' of SCO System 5."

zzxc writes "In a surprise turn of events, SCO says that they need more time to prepare an announcement of who they are going to sue. According to SCO, the lawsuits will be announced tomorrow morning shortly before a phone-in conference in which will be outlining their financial report. You can call 1-800-818-5264 code 141144 Wednesday at 9:00am MST to join in with your questions, or listen to the webcast. They also have said that these first two lawsuits will be against companies that hold SCO Unix licenses. (EV1.net servers or Lindows?)"

snoofy writes "Zones, as people from SUN Microsystems have talked about for some time are now available in solaris express (the pre-release of Solaris 10). This will let you virtualize Solaris so that processes run in isolation from other activity on the system... A system can then be configured to run several zones which will make it look like different systems on the network Some info from a posting to comp.unix.solaris. The cool stuff is that it works on both SPARC and x86."

slyall asks: "I work in the Network/System Admin team for an ISP. Our firm was recently bought by another company that has mandated that my team's desktops be switched over from Linux to Windows XP in the next few weeks. Some of us are have used Linux almost exclusively and going to Windows is a big change. Can people suggest any tips, books or websites to help Linux people shoved into the Windows world (especially those running lots of Linux and Cisco boxes)? We've all got years of experience on Linux but running Windows day to day is a big challenge. We don't yet know if the company will provide us with tools such as Cygwin or Windows Services for UNIX but we won't be allowed to install random programs and may not have admin access. We're not happy with the change but we're unable to stop it. What we are hoping to do is reduce the performance hit that the changeover is going to cause." This is probably one of those situations where a LiveCD-based distribution, for use in an emergency, might help.

Spencerian writes "Learning Unix for Mac OS X Panther is a good tool for those who are experienced with the original Mac OS or Mac OS X, but not the Unix command line. Most of the content would not interest the traditional programmer, Linux, BSD, or other UNIX jockey, however." For Spencerian's take on why, read on for the rest of his review.

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.

This is an unusual Slashdot Interview, since instead of using email I asked all the questions in person last week either at LinuxAsia2004 or in casual meetings with local LUG members and other techies I met during the conference. Some of your questions were answered quite well by other Slashdot readers in the original post. (Slashdot has many readers both in and from India.) I also inserted a number of personal observations, which I usually don't do in these interviews, because it seemed to be the best way to answer some of the questions. And some questions were nearly unanswerable, as you'll see when you read the rest of this article.

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.

IronBlade asks: "Hi all, I'm very interested to hear if the O'Reilly / Useractive Linux/UNIX System Administrator courses are any good. There are 4 units, and as they are offering them in a package (4 for the price of 3) until -Feb 15th-, I'm very interested in your opinion as to their worth. I have previous sysadmin experience on GNU/Linux and feel I have a reasonable grasp of things, but I don't have any proof of my skills, and certificates from the University of Illinois would be a Good Thing to add to the CV."

Bellhead ( Second-Tier Associate to the First-Tier Minion, BLU) writes "The Boston Linux & Unix User Group's 16th Linux Installfest is being held at MIT on Saturday, February 28. Linux users in and around Boston, Massachusetts will have access to expert help and tools in order to install Linux on their computers. The BLU's volunteers will help anyone who shows up and brings their computer, free of charge (they accept donations). See the BLU Website for details and directions. Information about the BLU is at http://www.blu.org."

btempleton writes "The folks at Groklaw have posted a story including a preliminary copy of Caldera/SCO's amended complaint, including lines of code they allege were improperly included in Linux. The PDF can be found at this story The file lists unix filenames with line numbers and filenames and line numbers from the Linux 2.2 and 2.4 kernels, so folks can now go into real depth."

An anonymous reader writes "News.com.com reports that the SCO Group has significantly widened its Unix and Linux lawsuit against IBM, adding a copyright infringement claim to the already complicated case." There's also another story discussing the copyright claims.

Craig Maloney writes "If you are a Windows programmer looking to create or move your stand-alone database applications away from Microsoft-specific tools such as Visual Basic, Visual C++, Access or SQL Server, MySQL: Building User Interfaces is written just for you." Read on for the rest of Craig's review.

wintermute42 writes "Simson Garfinkel, author of Practical Unix & Internet Security along with Gene Spafford and Alan Schwartz, has an article in The Nation on RFID tags. They're not just for tracking stuff. They can track you too."

An anonymous reader writes "Over on GrokLaw, PJ and others have decided to create a 'timeline' for Unix and Linux development. The plan is to recreate, as completely as possible, the history of these two operating systems '...from the perspective of tracing the code by copyright, patents, trade secret, and trademark. The idea is that the final timeline will be a publicly-available resource, released under a Creative Commons license, that will assist the community in defending against - or better yet in deterring - future lawsuits against GNU/Linux code.'"