Slashdot Mirror

They got in a free attempt at dismissing the entire case, and set themselves up so they can attack the complaint - before the trial even begins.

IANAL, but I have had scrapes with IP law in the past over some work I've done, and I had a damn fine lawyer - supposedly one of the best in the US (nothing like winning outright because of one well-written letter...). I've got to admire what IBM's doing here. That knife didn't even hurt when it went in, all nice and professional-like.

Here is some more legal commentary. It seems to dispute some of the OSDL's position - but comes up with other reasons why SCO's case may be flawed.

Here's another lawyer (Australia), saying don't "drop your pants" to SCO.

Finally, here's IBM planning a response to SCO's amended complaint. Once again SCO's web site seems to omit some important issues.

This is the title of a Knowledge@Wharton article from April 2002, still available from CNET News.com. I commented this article here. Basically, a professor of management argued that depending of your starting location on the Web, a *cheap* one or Forbes, you would obtain different prices from online travel companies. I tried it, sending identical queries *simultaneously* from different computers and browsers, but I didn't find any differences. Maybe things have changed.

"Our government is incapible of becoming like Orwell's 1984"

Nope, too many diaries

too many non-state newspapers

IBM actually has 9 different affirmative defenses against SCO in their response. The GPL issue is probably just part of 1 of these defenses (number 7th).

Even if none of these 9 were to work, the burden would still be on SCO to prove the 100+ assertions in their complaint.

Last week SCO announced acquiring the assets and technology of Vultus, a web services company, who offer web development tools called WebFace ("Runs on Internet Explorer 5 and up").

While SCO predicted that they would obtain 15%-20% of a $3.7bn Web Services market, I have to admit to being perplexed how this is supposed to happen, and also wondering how well an Internet Explorer-based product could fit into SCO's UNIX offerings.

ComputerWorld has an alternative explanation of the Vultus acquisition, they call it: "SCO's Shell Game".

One thing is for sure - it sure is lucky that Vultus was in the same (Canopy-owned) building as SCO (check the picture), even before the acquisition!

Update: More on this story at GROKLAW

Repost: Form-4 filings with the SEC reveal Executives profiting from SCO stock sales: they made $398,833.90 in June, and $781,964.70 in July (so far)!

While most everybody focuses on the merits of the SCO vs IBM (and Linux by implication) case, SCO execs have made a tidy profit (over $1,000,000 in June and July) by selling stock

Form-4 filings with the SEC reveal they made $398,833.90 in June, and $656,270.10 in July (so far)!

And there's more!

Remember that Canopy-owned company SCO just bought into, who's the leader? "Mike Meservy, CEO, Vultus, Inc"

Looks like he and Vultus, Inc. were themselves SCO shareholders even before SCO bought into Vultus. From excellent GROKLAW site about SCO v IBM: SCO has filed, on July 8, a Registration Statement on Form S-3, relating to "the public offering or distribution by selling stockholders of up to 305,274 shares of common stock, par value $0.001 per share, of The SCO Group, Inc." The shares will be sold by Vultus, Inc., The Canopy Group, Inc., Angel Partners Inc., Michael Meservy, Bruce K. Grant Jr., Ty D. Mattingly and R. Kevin Bean. Only Canopy Group, in this list, will retain any SCO stock. SCO "will not receive any proceeds from the sale or distribution of the common stock by the selling stockholders. ... On July 3, 2003, the last price for our common stock, as reported by the Nasdaq National Market, was $10.71."

A recent posting on the Groklaw blog (see "SCO Can't Go After Statutory Damages or Atty's Fees" heading in the 7/22/03 section) states the US Copyright Office claims that SCO cannot go after statutory damages or attorney fees for any copyright infringement based on the most recent filing. They can only go after actual damages, which are very hard to prove in court.

What are SCO's actual damages from someone using Linux who would never have bought any SCO product in the first place? I mean, if I downloaded my ISO and burned it myself to install on 5 machines, it seems hard to argue that had Linux not included SCO IP, I would have purchased 5 copies of SCO UnixWare. No, if there had been no Linux, I'd have gone for one of the *BSD's. So even if SCO is correct, what are the actual damanges.

Doing some more copyright law searching.

Found these points at Bromberg and Sunstein LLP

Benefits of Federal Copyright Registration

Required for Infringement Suit. Generally speaking, unless the copyrighted work has been registered (or the Copyright Office has refused registration although the required deposit, application and fee were properly filed), a court action for infringement of the copyright will be dismissed.

Required for Statutory Damages. If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits.

Now, you can go to the Library of Congress Copyright site (www.copyright.gov) and search for the newly awarded SCO copyright: TX-5-705-356.

Notice that the SCO copyright lists publication date as 27Jun91, but registration date of 30Jun03. Combine that with "If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits." from above and it does seem like SCO will have a tough case to make in any litigation relating to copyright.

Presumption of Validity. In any judicial proceeding, a certificate of registration issued within five years of the first publication of the work confers a legal presumption that the copyright is valid and that all facts stated in the copyright registration certificate are true.

Also note that the 5 year presumption of validity time limit has expired.

Protection Against Importation of Infringing Copies. A copyright owner can record the registration with the U.S. Customs Service for protection against the importation of infringing works.

Wonder how much of the alleged infringing work was done overseas? Wasn't some of it supposed to have been done by a German Caldera employee? Wonder if SCO has taken this step yet?

A recent posting on the Groklaw blog (see "SCO Can't Go After Statutory Damages or Atty's Fees" heading in the 7/22/03 section) states the US Copyright Office claims that SCO cannot go after statutory damages or attorney fees for any copyright infringement based on the most recent filing. They can only go after actual damages, which are very hard to prove in court.

What are SCO's actual damages from someone using Linux who would never have bought any SCO product in the first place? I mean, if I downloaded my ISO and burned it myself to install on 5 machines, it seems hard to argue that had Linux not included SCO IP, I would have purchased 5 copies of SCO UnixWare. No, if there had been no Linux, I'd have gone for one of the *BSD's. So even if SCO is correct, what are the actual damanges.

Doing some more copyright law searching.

Found these points at Bromberg and Sunstein LLP [bromsun.com]

Benefits of Federal Copyright Registration

Required for Infringement Suit. Generally speaking, unless the copyrighted work has been registered (or the Copyright Office has refused registration although the required deposit, application and fee were properly filed), a court action for infringement of the copyright will be dismissed.

Required for Statutory Damages. If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits.

Now, you can go to the Library of Congress Copyright site (www.copyright.gov) and search for the newly awarded SCO copyright: TX-5-705-356.

Notice that the SCO copyright lists publication date as 27Jun91, but registration date of 30Jun03. Combine that with "If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits." from above and it does seem like SCO will have a tough case to make in any litigation relating to copyright.

Presumption of Validity. In any judicial proceeding, a certificate of registration issued within five years of the first publication of the work confers a legal presumption that the copyright is valid and that all facts stated in the copyright registration certificate are true.

Also note that the 5 year presumption of validity time limit has expired.

Protection Against Importation of Infringing Copies. A copyright owner can record the registration with the U.S. Customs Service for protection against the importation of infringing works.

Wonder how much of the alleged infringing work was done overseas? Wasn't some of it supposed to have been done by a German Caldera employee? Wonder if SCO has taken this step yet?

The most recent posting on the Groklaw blog states the US Copyright Office claims that SCO cannot go after statutory damages or attorney fees for any copyright infringement based on the most recent filing. They can only go after actual damages, which are very hard to prove in court.

What are SCO's actual damages from someone using Linux who would never have bought any SCO product in the first place?

Doing some more copyright law searching.

Found these points at Bromberg and Sunstein LLP


Benefits of Federal Copyright Registration

Required for Infringement Suit. Generally speaking, unless the copyrighted work has been registered (or the Copyright Office has refused registration although the required deposit, application and fee were properly filed), a court action for infringement of the copyright will be dismissed.

Required for Statutory Damages. If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits.

Now, you can go to the Library of Congress Copyright site (www.copyright.gov) and search for the newly awarded SCO copyright: TX-5-705-356.

Notice that the SCO copyright lists publication date as 27Jun91, but registration date of 30Jun03. Combine that with "If registration is made within three months after the first publication of the work or prior to infringement, certain damages and attorneys' fees provided by law will be available, in addition to actual damages and lost profits." from above and it does seem like SCO will have a tough case to make in any litigation relating to copyright.

Presumption of Validity. In any judicial proceeding, a certificate of registration issued within five years of the first publication of the work confers a legal presumption that the copyright is valid and that all facts stated in the copyright registration certificate are true.

Also note that the 5 year presumption of validity time limit has expired.

Protection Against Importation of Infringing Copies. A copyright owner can record the registration with the U.S. Customs Service for protection against the importation of infringing works.

Wonder how much of the alleged infringing work was done overseas? Wasn't some of it supposed to have been done by a German Caldera employee? Wonder if SCO has taken this step yet?

I work as a programmer (and software architect), so I have lots of compassion for IT people who will loose their jobs in this country. I lost my job a few years ago when my dot.com went out of business.

That said, except for environmental concerns, I think that globalization makes a lot of sense: perform work and manufacturing where it can be done most cost effectively.

Since I work as an independent consultant who mostly telecommutes, I have long considered cheaper overseas IT folks to be the competition. The question is, how to compete?

For starters, I try to constantly educate myself. Secondly, I believe in Joseph Campbell's teachings: "follow your bliss": do the work that you love to do. Just like a lot of people 'here' on Slashdot, I love what I do and I could not imagine working in another field. So, I compete with foreign workers with passion for what I do, constant education, and many years of diverse experience.

I know that this might sound callous, but I just believe that protectionism is a mistake.

-Mark

I also found that SCO donated Unixware and System V code to IBM's AIX 5L project. This was the successor to Project Monterey. See evidence on this page. The SCO page has disappeared from their site, but I was able to retrieve it elsewhere.

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

Roland Piquepaille: "This column details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. In this longer column, you'll find a selection of stories, including links, abstracts and illustrations."

TRANSLATION:
"I am a shameless karma-whore and copyright violator... OK, I'm just dancing around what I really mean: thief! This column [IT'S MY BLOG! AGAIN! DID I FOOL YOU THIS TIME?] details the special constraints applying to the design of these applications: special interfaces, lack of power and memory, and interoperability between heterogeneous networks. I STOLE all of it directly from the articles -- that's right, I plagiarized it as if it was my own work and added no value or original thought. In this longer column [MY BLOG YET AGAIN! DID I FOOL YOU THIS TIME?], you'll find a selection of stories, including links, abstracts and illustrations. All of that is stolen, too! The images, the text... copyright infringement is what I do best! Then I post it to Slashdot to build myself up as a technology pundit!

Somehow, I don't think the first part of "Liberte, egalite, fraternite" meant freedom to steal intellectual content that isn't yours. It's free as in speech, not free as in beer. As this poster (whose highlighting/linking of the issues has inspired me to do the same) pointed out, plagiarism and copyright infringement are serious matters that end up hurting us all. Rule one of trying to become an authority on anything is not to deceive, steal or otherwise break laws. Doing so ensures you have no credibility.

OH, THE HUMANITY! ;)

(I joke, but it really is a serious issue.)

This sidebar contains a photograph of a student waltzing with the robot

First off, it's not a sidebar to either of the articles linked. It's a link to Roland's weblog.

Roland: Don't be a weblog spammer -- that's what it is you're doing -- by telling us the link is one thing (a sidebar to an article) when it's actually another (your weblog).

Copyright infringement like what Roland did by stealing this photo for his blog is a big reason why we're seeing much more aggressive actions by copyright holders. Couldnt he just have linked to the Ananova story and told us there is a picture there? Or if he was really desperate to get traffic to his weblog (although I'm not sure why -- Blogdex / Daypop / Google rankings? A paid gig like Salman Pax?) he could have easily linked to the image at Ananova or any other site thats carrying the AP photo.

Since Roland is from France, a country with a long history of respecting artistic works (even quasi-artistic commercial ones like the AP photo), I would have expected that he would have the decency not to rip the photo off. I'm sure the photographer would appreciate getting credited with his own work.

A completely separate piece of advice: the best way to get people to read your weblog is to add something of value such as insightful commentary - I don't see any of that on your weblog.

Stealing someone else's content and tricking the Slashdot crowd into clicking on the link is a great way to get a bad reputation as someone who is sleazy and manipulative.

This sidebar contains a photograph of a student waltzing with the robot

First off, it's not a sidebar to either of the articles linked. It's a link to Roland's weblog.

Roland: Don't be a weblog spammer -- that's what it is you're doing -- by telling us the link is one thing (a sidebar to an article) when it's actually another (your weblog).

Copyright infringement like what Roland did by stealing this photo for his blog is a big reason why we're seeing much more aggressive actions by copyright holders. Couldnt he just have linked to the Ananova story and told us there is a picture there? Or if he was really desperate to get traffic to his weblog (although I'm not sure why -- Blogdex / Daypop / Google rankings? A paid gig like Salman Pax?) he could have easily linked to the image at Ananova or any other site thats carrying the AP photo.

Since Roland is from France, a country with a long history of respecting artistic works (even quasi-artistic commercial ones like the AP photo), I would have expected that he would have the decency not to rip the photo off. I'm sure the photographer would appreciate getting credited with his own work.

A completely separate piece of advice: the best way to get people to read your weblog is to add something of value such as insightful commentary - I don't see any of that on your weblog.

Stealing someone else's content and tricking the Slashdot crowd into clicking on the link is a great way to get a bad reputation as someone who is sleazy and manipulative.

This sidebar contains a photograph of a student waltzing with the robot

First off, it's not a sidebar to either of the articles linked. It's a link to Roland's weblog.

Roland: Don't be a weblog spammer -- that's what it is you're doing -- by telling us the link is one thing (a sidebar to an article) when it's actually another (your weblog).

Copyright infringement like what Roland did by stealing this photo for his blog is a big reason why we're seeing much more aggressive actions by copyright holders. Couldnt he just have linked to the Ananova story and told us there is a picture there? Or if he was really desperate to get traffic to his weblog (although I'm not sure why -- Blogdex / Daypop / Google rankings? A paid gig like Salman Pax?) he could have easily linked to the image at Ananova or any other site thats carrying the AP photo.

Since Roland is from France, a country with a long history of respecting artistic works (even quasi-artistic commercial ones like the AP photo), I would have expected that he would have the decency not to rip the photo off. I'm sure the photographer would appreciate getting credited with his own work.

A completely separate piece of advice: the best way to get people to read your weblog is to add something of value such as insightful commentary - I don't see any of that on your weblog.

Stealing someone else's content and tricking the Slashdot crowd into clicking on the link is a great way to get a bad reputation as someone who is sleazy and manipulative.

This sidebar contains a photograph of a student waltzing with the robot

First off, it's not a sidebar to either of the articles linked. It's a link to Roland's weblog.

Roland: Don't be a weblog spammer -- that's what it is you're doing -- by telling us the link is one thing (a sidebar to an article) when it's actually another (your weblog).

Copyright infringement like what Roland did by stealing this photo for his blog is a big reason why we're seeing much more aggressive actions by copyright holders. Couldnt he just have linked to the Ananova story and told us there is a picture there? Or if he was really desperate to get traffic to his weblog (although I'm not sure why -- Blogdex / Daypop / Google rankings? A paid gig like Salman Pax?) he could have easily linked to the image at Ananova or any other site thats carrying the AP photo.

Since Roland is from France, a country with a long history of respecting artistic works (even quasi-artistic commercial ones like the AP photo), I would have expected that he would have the decency not to rip the photo off. I'm sure the photographer would appreciate getting credited with his own work.

A completely separate piece of advice: the best way to get people to read your weblog is to add something of value such as insightful commentary - I don't see any of that on your weblog.

Stealing someone else's content and tricking the Slashdot crowd into clicking on the link is a great way to get a bad reputation as someone who is sleazy and manipulative.

This sidebar contains a photograph of a student waltzing with the robot

First off, it's not a sidebar to either of the articles linked. It's a link to Roland's weblog.

Roland: Don't be a weblog spammer -- that's what it is you're doing -- by telling us the link is one thing (a sidebar to an article) when it's actually another (your weblog).

Copyright infringement like what Roland did by stealing this photo for his blog is a big reason why we're seeing much more aggressive actions by copyright holders. Couldnt he just have linked to the Ananova story and told us there is a picture there? Or if he was really desperate to get traffic to his weblog (although I'm not sure why -- Blogdex / Daypop / Google rankings? A paid gig like Salman Pax?) he could have easily linked to the image at Ananova or any other site thats carrying the AP photo.

Since Roland is from France, a country with a long history of respecting artistic works (even quasi-artistic commercial ones like the AP photo), I would have expected that he would have the decency not to rip the photo off. I'm sure the photographer would appreciate getting credited with his own work.

A completely separate piece of advice: the best way to get people to read your weblog is to add something of value such as insightful commentary - I don't see any of that on your weblog.

Stealing someone else's content and tricking the Slashdot crowd into clicking on the link is a great way to get a bad reputation as someone who is sleazy and manipulative.

Furthermore, SCO's claims are bunk as this entry shows, for what SCO is complaining about is the inclusions of pieces of code in IBM's distro, such as JFS. But a Caldera employee at the time was contributing to this process and they didn't complain at the time!

SCO is sunk.

Furthermore, SCO's claims are bunk as this entry shows, for what SCO is complaining about is the inclusions of pieces of code in IBM's distro, such as JFS. But a Caldera employee at the time was contributing to this process and they didn't complain at the time!

SCO is sunk.

there seems to be a bug with slashdot (GASP)

click 'reply to this' to read all of the post, or here is from where I see it get cut off from:

It is similarly possible to write some or all code in a C++ class in the header file itself, though it is usually considered bad practice due to recompile issues. Java has done away with both the issues and the notion of separate header files.

More specifically:
http://radio.weblogs.com/0122027/2003/04/07.html#a 12
answering this question in relation to each point:
A) this is no different than creating a C++ class from a LGPL library. Your code is yours, you are simply using the interfaces/accessors provided by the library.
answer A - unrestricted
B) this is touchier. by extending a class, you are basically creating a class that is equivalant to the original, with possible additions and modifications. However, this is being done without actually using any of the original code, so you are not actually modifying any LGPL source, and are not 'based on', but rather 'use' the original library/class. Also of note, after extending the class, the original class file can be swapped as explained above with the beginning of section 5. Java does not include any of the original 'portions' of the LGPL library in the object code compiled for an extended class, thus again, it falls in the class of code 'using' the library rather than 'based on' or containing portions of it.
answer B - unrestricted
C) in my professional (programmer) opinion, the rest of the options are merely obfuscations around the point, in case the answer to A was restricted.. again, ProxyBar is merely using the object provided and its accessors.
answer C - unrestricted
D) more obfuscation, but rather than the usage, the obfuscation here is how they retrieved the object. This concerns the distribution method, again, and thus it is not nescessary to do this. However, since the question is not whether this is needed, but if it's okay to do it, I'll answer anyway. The process used here is equivalant to the pseudo code:

org.gnu.foo.Bar obj = new org.gnu.foo.Bar();
obj.someMethod(args[0]);

which is nearly the same as A. The classes are loaded using the same class loader in both cases, because the system loader is searching for org.gnu.foo.Bar in the same places whether the import statement is used, or the Class.forName().
The only difference is that this is done at runtime -only- for this version, while the import looks up the class at compile time, as well. This means that for the import statement, insteading of assuming that your functions will exist when getMethod() returns, or that the class will even be there (notice no error checking in this and the next question), will actually check the code and ensure proper usage of functions. No actual information is stored when the compiled object/bytecode is output.
answer D - unrestricted
E) whee, more obfuscation! Same as above, except the strings are taken via the command line. The name of the class was not in question or copyrighted (maybe trademarked, but that doesn't matter in this discussion). If it were, there would be larger issues with that library than just the LGPL's interaction with Java. This question in fact has absolutely no knowledge of the LGPL'd library, and could be used to run any library, any class, any function. So it is not at all effected by the LGPL.
answer E - unrestricted
F) the org.gnu.foo.Bar in question has suddenly become an executable, not a library, and as such the license no longer has any bearing. remember from section 0: "The act of running a program using the Library is not restricted" The library has becoming it's own program using the library.
answer F - unrestricted.

That's my interpretation, and line of reasoning. Feel free to nitpick or argue against my points, I will gladly view others' reasoning.

Nature also wrote an article about the American Solar Challenge 2003. This summary of Nature's story contains photographs coming from the ASC Photo Library, but read Nature's article for more technical details.

Well, because it is a new idea. Diaries were kept for private viewing, a few notable exceptions notwithstanding. The idea of being able to post your "diary" globally is certainly empowering. Yeah, yeah, we're /. and we look down on anyone who cannot do HTML. Fine, be elitist, but most of the world is not, and never will be, programmers, or even scripters. And blogging software has given the rest of the world a simple tool that enables them to do what we have been able to do for years.

Blogs are more than the sum of their parts, furthermore. It's not just that these "diaries" are online. The blog phenomenom is based on the mutual linking that goes on. It's a community -- that hardly describes a diary or a journal -- of users connecting to each other. Does that sound familiar? Sure, it's the promise of the web, only now accessible to a lot more people.

Finally blogs are not just "diaries." For example, I have my web site where I have fun with the wording of headlines. In order to see how the power of blogging works, I recently created a blog of my site in order to see if the connectivity of the blog community would increase awareness. I'm playing with the blog phenemenon, in other words. Yet there is nothing about me at my blog, no diary entries, nothing. It's all about the humor.

Blogging is about the community, not just a diary.

It's a freaking diary, keep it under your bed. What makes you thing the rest of the world gives a damn.

See, there's lots of reasons for blogging. As for the term, the beauty of it or the need for a new term: it's discussible, naturally, but I believe weblogs differ from journals enough to deserve a new term. They're more like open letters than diaries.

The Ransom Love Linuxworld speech where Caldera explicitly states that it is donating code to Linux so that it can scale for high-end business uses and that Caldera was committed with IBM to making Linux scale to 64-bit as part of Project Monterey and IA-64 Linux is evidence where I come from. It's evidence that SCO has filed legal documents that it knows explicitly are false.

The SCO group, and both Old SCO and Caldera before it, directly acknowledged and assisted IBM with the scalablity of Linux

In August 2000, just days after Caldera purchased the Old SCO server division, the then CEO of Caldera, Ransom Love, made a keynote speech at LinuxWorld 2000. A RealPlayer video stream of the event can be found at DrDobbs Journal's Technetcast

In the question and answer session at the end of the keynote, Love was asked about the possible conflict over Monterey and Linux IA-64

A mp3 capture of the following transcribed portion

Q: What happens about Project Monterey, because that conflicts with the AI-64 Linux, 64-bit Linux?

Love: OK. I don't -- if we do our job right in making Linux scale over like UnixWare to the degree that everybody, that we know we can... May I ask, some people have said, "Well, people have tried this in the past, but they haven't been that successful," may I suggest: we don't have any ulterior motives for not making it successful. Technologically has not been the reason why it hasn't done it before. There's always some other motive, right? And so to talk about Monterey, clearly we want to make sure we have the same level of Linux integration on Monterey that we would have in our Unixware product. Now, we don't control, I mean, we have a great relationship... it's a joint development relationship with IBM which we intend to preserve ... but they have similar interests and so this is really a very synergistic, uh, this transaction is great for all of the major partners as they have already wanted to embrace Linux moving forward.

Now, let me address one other aspect of your question, which is that the Monterey Project is in conflict with the IA-64 Linux Project. I don't believe it's in conflict at all. Now, clearly, we have tremendous vested interest in the IA-64 Linux Project and with the acquisition of SCO, they've been doing a lot, so you combine those, and we've got one of the more comprehensive offerings, I believe, on the IA-64 Linux. So that's clearly an area that we're very committed to. But like Unixware, there's elements of the Monterey kernel that are more scalable, OK? Now, on the IA-64 platform, I don't know how long of window that is, but today, it's a little bit more robust and more scalable than the IA-64 Linux is today. Now, I'm not saying that over time that won't change.

But, and let me address one other thing. Sorry, (laughs) you're getting all of it through one question. But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms. We'll work with Linus and everyone in order to make that available. That will take some time. And as I mentioned earlier, I don't know that over time you can have a single kernel -- in fact I know you can't -- that will scale, you know, the breadth of IT technology needs. So I think we're looking, in the Linux community, at having multiple kernels, so...

Q: Multiple Linux kernels? Or multiple UNIX kernels?

Love: Multiple Linux kernels as well, over time.

Q: Thank you.

Love: You bet.

It's about time to reexamine the recent claims of The SCO group and call in the lawyers and maybe the authorities

In "Poker playing computer will take on the best," the Edmonton Journal wrote last June (the article is no longer available for free) that there was a new poker player in town "that never sweats, never gets tired, never tips a hand and can still bluff with the best of them.

University of Alberta artificial intelligence researchers bet their new poker computer program will be the best player in the world, perhaps within a year." And why will it the best player? Because it bluffs.

"You have to bluff," says Jonathan Schaeffer, who heads up the university's Games Research Group and who already has a world-champion checkers computer program under his belt. "If you do not bluff, you're predictable. If you're predictable, you can be exploited."

This kind of program could be used whenever you have to deal with imperfect information, like buying a new car. You can find more details and references in this summary.

I think, maybe SCO don't care what happened with BSD.

Perhaps I am totally misunderstanding their comments but I get the impression SCO seems to think they own C++ programming languages anyway.

As to this case, SCO now allege that IBM's support for Linux is killing Unix, but not too long ago, SCO discussed Unix's feature in their SEC filings.

Meanwhile, definitely worth checking out, there's a new S-3 filing by SCO

In August 2000, just days after Caldera purchased the Old SCO server division, the then CEO of Caldera, Ransom Love, made a keynote speech at LinuxWorld 2000. A RealPlayer video stream of the event can be found at DrDobbs Journal's Technetcast

In the question and answer session at the end of the keynote, Love was asked about the possible conflict over Monterey and Linux AI-64

A mp3 capture of the following transcribed portion

Q: What happens about Project Monterey, because that conflicts with the IA-64 Linux, 64-bit Linux?

Love: OK. I don't -- if we do our job right in making Linux scale over like UnixWare to the degree that everybody, that we know we can... May I ask, some people have said, "Well, people have tried this in the past, but they haven't been that successful," may I suggest: we don't have any ulterior motives for not making it successful. Technologically has not been the reason why it hasn't done it before. There's always some other motive, right? And so to talk about Monterey, clearly we want to make sure we have the same level of Linux integration on Monterey that we would have in our Unixware product. Now, we don't control, I mean, we have a great relationship... it's a joint development relationship with IBM which we intend to preserve ... but they have similar interests and so this is really a very synergistic, uh, this transaction is great for all of the major partners as they have already wanted to embrace Linux moving forward.

Now, let me address one other aspect of your question, which is that the Monterey Project is in conflict with the IA-64 Linux Project. I don't believe it's in conflict at all. Now, clearly, we have tremendous vested interest in the IA-64 Linux Project and with the acquisition of SCO, they've been doing a lot, so you combine those, and we've got one of the more comprehensive offerings, I believe, on the IA-64 Linux. So that's clearly an area that we're very committed to. But like Unixware, there's elements of the Monterey kernel that are more scalable, OK? Now, on the IA-64 platform, I don't know how long of window that is, but today, it's a little bit more robust and more scalable than the IA-64 Linux is today. Now, I'm not saying that over time that won't change.

But, and let me address one other thing. Sorry, (laughs) you're getting all of it through one question. But clearly we are going to add components back to the Linux kernel on both IA-32 and IA-64 platforms. We'll work with Linus and everyone in order to make that available. That will take some time. And as I mentioned earlier, I don't know that over time you can have a single kernel -- in fact I know you can't -- that will scale, you know, the breadth of IT technology needs. So I think we're looking, in the Linux community, at having multiple kernels, so...

Q: Multiple Linux kernels? Or multiple UNIX kernels?

Love: Multiple Linux kernels as well, over time.

Q: Thank you.

Love: You bet.

SCO has NO effective case against either IBM, HP or anyone else.

Maybe you'd want to look into adodb.

Oh, and your boss will be a cell phone. See, he's yelling at you right now.

God, I hope they have drugs in the future.

You'll find the summary of this Business 2.0's story on Smart Mobs. And on my blog, you can find two other stories about RFIDs, Bye-Bye Bar Codes? and The Eerie Possibilities of RFID Tags.

You'll find the summary of this Business 2.0's story on Smart Mobs. And on my blog, you can find two other stories about RFIDs, Bye-Bye Bar Codes? and The Eerie Possibilities of RFID Tags.

JFS ( Journalling File System ). NUMA (Non Uniform Memory Access), a SGI/Stanford collaboration . RCU ( Read-Copy-Update ). SMP ( Symmetrical Multi-Processing ).

"'So you want royalties from FreeBSD as well?' I asked. Sontag responded that 'there may or may not be issues. We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property).'"

JFS ( Journalling File System ). NUMA (Non Uniform Memory Access), a SGI/Stanford collaboration . RCU ( Read-Copy-Update ). SMP ( Symmetrical Multi-Processing ).

"'So you want royalties from FreeBSD as well?' I asked. Sontag responded that 'there may or may not be issues. We believe that UNIX System V provided the basic building blocks for all subsequent computer operating systems, and that they all tend to be derived from UNIX System V (and therefore are claimed as SCO's intellectual property).'"