You got all the good stuff but here's the whole thing.
SCO Confronting Its Creation
Company's CEO is taking precautions as the head of the 'most despised' tech firm.
From Bloomberg News
Darl McBride, chief executive of SCO Group Inc., says he sometimes carries a gun because his enemies are out to kill him. He checks into hotels under assumed names. An armed bodyguard protected him when he gave a speech last month at Harvard Law School.
Linus Torvalds, creator of the Linux operating system, calls SCO "the most despised company in technology."
The reason: SCO Group is claiming rights to the Linux open source software code that thousands of users and supporters say should have no owner. SCO filed a $50-billion suit against IBM Corp. last year and on Wednesday turned on Linux users DaimlerChrysler and AutoZone Inc., seeking an injunction and unspecified damages.
"We are fighting the big battle," McBride said in a telephone interview from his office at SCO headquarters in Lindon, Utah, 40 miles south of Salt Lake City.
McBride, 44, is pitting SCO against an industry it once helped develop. Less than two years ago SCO, formerly Caldera International Inc., was helping to form a standard version of Linux to compete with Microsoft Corp.'s Windows. Once McBride took the helm in June 2002, SCO changed tack, hired attorney David Boies -- who won the government's antitrust suit against Microsoft -- and began claiming that Linux users infringed SCO's intellectual property.
Linux has attracted thousands of individuals and firms, some of whom see it as the only credible threat to Windows. Others use it because it's cheaper.
The software is now being used by companies ranging from DaimlerChrysler, the world's largest maker of luxury cars, to Lehman Bros. Inc., the fourth-largest U.S. securities firm by capital, to Google Inc., the world's most widely used Internet search engine. Lockheed Martin Corp., the world's largest defense contractor, also has servers that run on Linux as part of its computer network.
IBM pushes computers that run on the Linux operating system. Shipments of Linux-powered server computers, fast machines used to run websites, rose 53% in the fourth quarter, more than double the rate of Windows servers, according to market researcher IDC.
McBride and SCO are more hated than Microsoft, the world's largest software maker, and its Chairman Bill Gates, according to some Linux backers. That's because SCO, once a backer of Linux, has turned around and attacked the essence of the system: its free source code.
"SCO are just complete hypocrites," said Jeremy Allison, co-author of Samba, an open source software that runs a file and print service that SCO sells.
SCO says it owns the copyright to the Unix system and that parts of the Unix code have been copied into Linux. SCO is demanding payment from each user of Linux. Novell Inc. separately is disputing SCO's claim to Unix.
SCO claims IBM is distributing the Linux software containing its copyrighted Unix code. It claims companies such as Red Hat Inc. are building products using the same code.
DaimlerChrysler spokesman Han Tjan said he had no comment on SCO's lawsuit. AutoZone CEO Steve Odland declined to comment on the claims. IBM spokeswoman Trink Guarino said the lawsuit is groundless and the company will contest it.
"The real reason why people don't like SCO, and Darl McBride in particular, is that he is so dishonest," Torvalds, 34, said in an e-mail.
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.
February 24, 2004 Linux Gets Security Boost from NSA By Sean Michael Kerner
Most stories about government deployments of Linux involve a distributor helping various federal and municipal agencies install the open source operating system. But in this case, a federal agency is helping Linux.
The U.S. National Security Agency (NSA), also known as the codemakers and codebreakers cryptologic division within the Department of Defense, has helped to harden Linux with newly-released Security Enhanced Linux (SELinux) kernel modifications.
The latest release, which updates the base kernel to 2.6.3 and 2.4.24, contains numerous significant improvements to security in the open source operating system. The SELinux improvements mark a major breakthrough for Linux. Because of the NSA's contributions to the kernel, the new security features will now show up in mainstream distributions of Linux.
"Conditional policies are significant and also networking hooks were added, which makes SElinux all that much more powerful," Joshua Brindle, hardened Gentoo Linux Project Leader and the NSA's SELinux contributor, told internetnews.com.
"They also exported AVC (define) controls to userland to facilitate strong X-based access control and privilege separation," he added.
SELinux was released by the NSA under the GNU GPL open source license. SELinux is essentially a Linux Kernel with a number of utilities that provide enhanced security functionality. But the critical component of SELinux is how it implements and handles mandatory access controls.
"SELinux is important because mandatory access controls are essential to limiting access to daemons and users to only what they need. It also solves the age-old almighty powerful superuser problem in Linux," Gentoo's Brindle told internetnews.com.
"We stress however that it isn't an end-all solution, that it must be combined with additional layers of protection."
Debian, Gentoo and Red Hat Fedora's latest test release of Fedora Core 2 all currently make some use of SELinux. Red Hat also plans to incorporate SELinux into its next Red Hat Enterprise Linux release
This "marks an important milestone in what enterprises globally feel is an important issue," Red Hat spokesperson Leigh Day said of the SELinux update. "One of the first issues we hear from our customers when talking with them about solution requirements is security," she told internetnews.com. "Were pleased to be working with the NSA to bring SELinux to our distribution. We will incorporate SELinux fully in our next release of RHEL 4."
The Security-enhanced Linux kernel enforces mandatory access control policies that confine user programs and system servers to the minimum amount of privilege they require to do their jobs.
Well, technically yes. The reason people call a plain-text file as non-binary is because Windows treats text files different from other ("binary") files when reading and writing them. "Binary" files have to be opened with a special binary flag.
Slashdot Mirror
// You never allocated any space for gender #include char* gender; char* main(){ gender = malloc(5); *gender = "male"; return gender; }
You got all the good stuff but here's the whole thing.
That means nothing. 5 out of those 23 files don't even have the word 'pam' in them.
I know that was only a joke, but you still deserve to die a horrible, horrible death just for thinking of it.
While we're on the topic (off topic?):
From acronymfinder.com:
Thanks, I thought something sounded a bit off on my correction, but I couldn't quite put my finger on it. That'll learn me I guess.
To correct the above:
Beer: the cause of, and solution to, all of life's problems.
Where have you been? Of course there's something better. It's called Betamax.
A: because this is slashdot
[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.]
Obviously not or he would've exlicitly stated it in his article.
I almost started crying when I first read that.
It might have just been because somebody is playing country music in the office, though.
As much as I really like Linux and would like to see Rome using it, I think I'd still rather see a Mafia shootout in Redmond.
I certainly hope there would be people left in this world after getting rid of the cannibals, necrophiliacs and trade anarchists.
So does the NSA :)
February 24, 2004
Linux Gets Security Boost from NSA
By Sean Michael Kerner
Most stories about government deployments of Linux involve a distributor helping various federal and municipal agencies install the open source operating system. But in this case, a federal agency is helping Linux.
The U.S. National Security Agency (NSA), also known as the codemakers and codebreakers cryptologic division within the Department of Defense, has helped to harden Linux with newly-released Security Enhanced Linux (SELinux) kernel modifications.
The latest release, which updates the base kernel to 2.6.3 and 2.4.24, contains numerous significant improvements to security in the open source operating system. The SELinux improvements mark a major breakthrough for Linux. Because of the NSA's contributions to the kernel, the new security features will now show up in mainstream distributions of Linux.
"Conditional policies are significant and also networking hooks were added, which makes SElinux all that much more powerful," Joshua Brindle, hardened Gentoo Linux Project Leader and the NSA's SELinux contributor, told internetnews.com.
"They also exported AVC (define) controls to userland to facilitate strong X-based access control and privilege separation," he added.
SELinux was released by the NSA under the GNU GPL open source license. SELinux is essentially a Linux Kernel with a number of utilities that provide enhanced security functionality. But the critical component of SELinux is how it implements and handles mandatory access controls.
"SELinux is important because mandatory access controls are essential to limiting access to daemons and users to only what they need. It also solves the age-old almighty powerful superuser problem in Linux," Gentoo's Brindle told internetnews.com.
"We stress however that it isn't an end-all solution, that it must be combined with additional layers of protection."
Debian, Gentoo and Red Hat Fedora's latest test release of Fedora Core 2 all currently make some use of SELinux. Red Hat also plans to incorporate SELinux into its next Red Hat Enterprise Linux release
This "marks an important milestone in what enterprises globally feel is an important issue," Red Hat spokesperson Leigh Day said of the SELinux update. "One of the first issues we hear from our customers when talking with them about solution requirements is security," she told internetnews.com. "Were pleased to be working with the NSA to bring SELinux to our distribution. We will incorporate SELinux fully in our next release of RHEL 4."
The Security-enhanced Linux kernel enforces mandatory access control policies that confine user programs and system servers to the minimum amount of privilege they require to do their jobs.
My favorite quote:
Oh wait.. sorry. I haven't read the article yet, but you can't mod me down because you probably never either :)
Only if you mean it.
Am I the only one the stopped reading the headline after reaching 'Virus'.
Don't worry, I can forward you the one she sent me. Sounds like the same email.
Well, technically yes. The reason people call a plain-text file as non-binary is because Windows treats text files different from other ("binary") files when reading and writing them. "Binary" files have to be opened with a special binary flag.
Only YOU can prevent copyright infringement.
That should be:
Dealer: Nineteen
Darl: Hit me
Dealer: Twenty
Darl: Hit Me
Dealer: Twenty-one
Darl: Hit me
Dealer: Twenty-two
Darl: SC'oh!