SCO Names 1st Lawsuit Target: AutoZone [Updated]
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."
Yes, SCO has exactly one "evidence" against AutoZone. Evidentially you need to get help, as your English skills are somewhat lacking.
Unless you meant to use the word "any" in your post title. Then that would make more sense!
You do NOT want to work for Autozone. Been there, done that. Unless you like wearing red, like doing a company 'cheer', and think rednecks are fun to work for.
... *augh*
Give me an 'A'! Give me a 'U'!
Check out the best P2P sharing website: MEDIACHEST.COM
I believe the user ID on the parent post says it all;
as usual "no data" means "not in a position to offer anything of value". I suggest that those who would like to see open source software succeed might learn something from the experience of people who've actually *done*something* to help make that happen.
Maybe it's just me, but I really fucking hate the FUD acronym. I'm not sure why, exactly, but it sounds fucking retarded. It's like a retarded person trying to say "fudge". It is overused in every SCO story on Slashdot. I fucking hate it; that is all.
Now, what is up with this Groklaw shit? I swear it's fucking quoted like the Bible in every SCO story on Slashdot. But on the very top of the site in plain view is this disclaimer: IANAL. I am a paralegal, so if you have a legal problem and want advice, this isn't the place. Hire an attorney instead. Granted, there probably are some useful bits of information, but I would talk to a real lawyer who specializes in this particular area of the law.
Hmmm. Now that I think of it, Slashdot is TOTALLY about zealotry:
Groklaw == 'The Bible'
SCO == 'Satan'
Microsoft == 'that fallen angel guy' (NOT the thing about the truck driver)
GPL == 'Ten Commandments'
RMS == 'Moses'
Linus == 'God'
Linux == 'Jesus'
ESR == 'some retarded guy'
I wish you GNU zealots would stop redefining words to suit your own purposes. If I buy a DVD I'm free to share it with my friends, by inviting them over to watch it with me or loaning it to them. What you are talking about it stealing. I don't care how many times you call it "sharing", it's not.
[Posted with my account to karma whore]
Supplemental No. 8: AutoZone claims are false
Authored by: jbgreer on Wednesday, February 18 2004 @ 10:00 AM EST
I don't know whether to be pleased or angry at SCO's assertion that IBM must have assisted AutoZone's transition to Linux due to the "precision and efficiency with which the migration occurred". You see, I was a Sr. Technical Advisor at AutoZone, where I was an employee for over 10 years. During my tenure, I participated and led in the design, development and maintenance of many of AutoZone's store systems. More importantly, I initiated AutoZone's transition to Linux and I directed the port of their existing store software base to Linux. I personally ported all of AutoZone's internal software libraries for use under Linux. I personally developed the rules by which other AutoZone developers should make changes to their code to support both Linux and SCO's OpenServer product. I believe at one point I had as many as 35 AutoZone developers performing porting work for me, much of which was trivial, given that our code did not generally rely on SCO specific features and that the more technologically sophisticated portions of our code tended to reside in our libraries. The developers were also responsible for testing their individual applications under both SCO and Linux; I supplemented this activity by performing builds of the entire AutoZone store software base on my desktop, which I had converted to Linux.
As to the claim that SCO's shared libraries were a necessary part of the port: false. No SCO libraries were involved in the porting activity.
As to the claim that IBM induced us to transition to Linux: false. It was, in fact, SCO's activities that 'greased the skids' and allowed the business case for using Linux to be made more easily. That is a story long in the telling; perhaps I'll share it another day.
One should remember the Linux business environment that existed at the time the AutoZone transition began. Several vendors - the original Caldera Linux distribution company, Red Hat, and Linuxcare - were offering support for enterprise installations of Linux. In fact, Bryan Sparks, then CEO of Caldera, flew to Memphis and met with me during my evaluation of the various distribution and support offerings. I also met and talked briefly with Dave Sifry of Linuxcare during the 1999 Linux Expo. AutoZone settled on Red Hat chiefly because of my familiarity with their distribution and the ease with which AutoZone could negotiate a support agreement with them.
I must add that SCO was eventually made aware of AutoZone's transition to Linux. They responded by offering to assist AutoZone in the porting activity. By the time of their offer, AutoZone had already completed the initial porting activity and had already installed a Linux-based version of their store system in several stores.
Finally, I'll add that I was for a time a member of SCO's Customer Advisory Board. As such, I believe I have some useful insights as to why SCO lost AutoZone's and several other large accounts' business.
[Yes, this is a joke.]
I remember when legal used to mean lawful, now it means some kind of loophole. - Leo Kessler