Sco is dying It is official. Netcraft has confirmed: Sco is dying
One more crippling bombshell hit the already beleaguered Sco community when IDC confirmed that Sco's market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that Sco has lost more market share, this news serves to reinforce what we've known all along. Sco is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict Sco's future. The hand writing is on the wall: Sco faces a bleak future. In fact there won't be any future at all for Sco because Sco is dying. Things are looking very bad for Sco. As many of us are already aware, Sco continues to lose market share. Red ink flows like a river of blood.
Sco Open Server is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time Sco Open Server developers only serves to underscore the point more clearly. There can no longer be any doubt: Sco is dying.
Let's keep to the facts and look at the numbers.
Sco leader Darl McBride states that there are 7000 users of Sco. How many users of Sco are there? Let's see. The number of Linux versus Unix posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Sco users. Sco Open Server posts on Usenet are about half of the volume of Sco posts. Therefore there are about 700 users of Sco Open Server. A recent article put Sco Open Server at about 80 percent of the Sco market. Therefore there are (7000+1400+700)*4 = 36400 Sco users. This is consistent with the number of Sco Open Server Usenet posts.
Due to the troubles of The Sco Group, abysmal sales and so on, Sco went out of business and was taken over by IBM who sell another troubled OS. Now Sco is also dead, its corpse turned over to yet another charnel house.
All major surveys show that Sco has steadily declined in market share. Sco is very sick and its long term survival prospects are very dim. If Sco is to survive at all it will be among OS dilettante dabblers. Sco continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Sco is dead.
The laser beam would be pretty narrow- a cordless drill and a big old drill bit should clear a nice 1.5 inch diameter path between nodes. I guess to line the hole up, you'd need GPS readings and a laser pointer, and then you just go out at dusk and drill a hole through anything the laser hits.
I hope this was a joke I just didn't get. Have you ever been in the woods? This is simply impossible. Forests are not static things, but dymanic ever changing things. A critter could stop up your hole with nesting, or a tree could topple in its path. The wind will move trees back and forth, breaking the line of sight constantly.
A Linux virus could do significant damage without root access, and there are a variety of ways that such a virus could trick the user into giving it root access. Trojan a RPM or DEB, or even just ask the user for their root password with some excuse like "Your hard disk has reached a fragmentation level of 30%, we recommend that you defragment it now. Please enter your root password").
At the very least, this indemnifies *everyone* past the first rogue, and arguably makes it impossible for SCO to call the code back.
They already know this, but that isn't what the law suit is about. The law suit is about $1 billion that SCO claims this alleged offense has cost them. Honestly I doubt they care if the code is there by this point. Taking the code out will only cause some one to write a replacement relatively quickly, and net SCO nothing.
What I'm pondering on though, is how they are going to prove the code's time.
Well, they could say this kernel source was created $DATE and here's a SCO kernel created on $DATE from this source. Now, if they compile the kernel source and out pops the same binary they've been distributing for years, they've got a good leg to stand on. Otherwise, they're FUBARed I'd say, but IANAL of course.
Renters do not receive distribution.
Case in point: I run Linux, to serve web pages that are dynamically constructed by Tomcat and Apache. Where is the distribution of GPLed software happening in this scenario? I simply rent managed database storage, and provide the web interface.
You're not distributing software in this scenario. People are not renting your Apache and Tomcat from you, they are renting/leasing a service. For $DOLLARS per $PAYPERIOD you provide them with dynamic web hosting; you do not provide them with Tomcat and Apache.
Now, assume I have my own company, and create a modified version of GPLed software, then rent it to you in binary format only. You have received a binary from me, meaning that I have distributed a binary compiled from modified GPL software to you. Under the terms of the GPL, I must provide you with my modified source code.
If it's GPLed, you can just get the source somewhere else, right? What's the issue here then?
Sorry, but you're wrong. Even if it is GPLed doesn't neccessarily mean you can get the source from elsewhere. Here's a hypothetical. I get a copy of some GPLed software, make some cool ass changes, and then lease that software to you. Sure you can get the same source I got, but that doesn't mean you can get the modified source that created the binary you leased from me.
It's hard to tell if they're right when they won't talk about what parts of Linux they have a problem with.
Oh, but they did mention one little area. SCO said it was simply impossible for Linux to have achieved such strong SMP support without one of two things:
1) A strong development platform.
2) SCO source.
They seem to have forgotten that Caldera gave Alan Cox a dual processor machine so he could write the Linux SMP code in the kernel.
Not good! Then I tried vmware, and had some issues there too (it doesn't like slackware's startup scripts, so I had issues getting modules to restart on reboot).
Anything that can be made to run under one GNU/Linux distro can be made to run under another, and slackware is no exception. Indeed, slackware is perhaps the poster child for running proprietary applications on a distro they weren't designed for. It's so homogenious that major changes are rarely needed. Since you mentioned trouble with vmware, why don't you take a look at this page which documents exactly how to install vmware on slackware liux. I've done it several times with no problems, and find it to be a walk in the park.
Re:"Young lady, in this house we obey the laws...
on
Energy From Vibrations
·
· Score: 1
the article poster just invented perpetual motion, arguing that the vibrator from the ringer could power the cellphone
See I don't have this problem. i realized a long time ago that if I sucked power from the vibrations of my cell-phone, that the vibrations would decrease. I also understand that vibration is in effect sound, so that this harnessing of vibration would silence the phone. I considered implementing this, but soon realized there was a much more efficient way to accomplish the same performance from my cell-phone, and retain battery life greater than this vibration harnessing technology can. I keep my cell phone turned off.
I used Lindows just this past Saturday. I installed it on my computer where it lived for roughly 30 minutes while I rushed in a panic to download and burn Slackware 9.0. Lindows is now gone forever, and I'm in Slack Heaven.
If the contractor did not pay HIS suppliers, the supplier could put a lean on your house. And it was LEGAL!
This is still legal in GA. Case in point, last year when the new building at my Church was being finished, the bankers put a lien on it. To make matters worse, it was neither our fault nor our contractor's fault. He had previously done work on publicly owned buildings, and they hadn't paid him what he was owed. When the bank came to call, they put a lien on our building until the mess was straightened out. Why did they put a lien on us? Well, in GA, it's illegal to put a lien on publicly owned property, which means the government can shaft a contractor and pass the buck along to the next privately owned job until they can make good on their debts.
I'm heading to my local patent office to patent my right to not buy Intel processors.
I assume your reasoning is doing this will hurt intel. If' that's so, that's messed up. You should be patenting buying intel processors so you can then charge royalties on anyone wishing to do the same. By patenting not buying intel chips, you're helping intel and hurting AMD.
You'll notice at the slackware store that there is a wonderful paperback book licensed under the GPL entitles, "Slackware Linux Essentials". It is perhaps one of the best linux books I have ever read and am thankful to be involved with.
Mysel and many of the "BOZOs" in alt.os.linux.slackware are currently working on a revised edition to bring this book up to date with the latest release of Slackware Linux. You can take a look at our (so far meager) progress here. I encourage anyone who wants to participate to give me an e-mail, you can find my address at that link, as well as a mailing list for this project. Any contributions would be greatly appreciated.
Slashdot Mirror
Sco is dying
It is official. Netcraft has confirmed: Sco is dying
One more crippling bombshell hit the already beleaguered Sco community when IDC confirmed that Sco's market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that Sco has lost more market share, this news serves to reinforce what we've known all along. Sco is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict Sco's future. The hand writing is on the wall: Sco faces a bleak future. In fact there won't be any future at all for Sco because Sco is dying. Things are looking very bad for Sco. As many of us are already aware, Sco continues to lose market share. Red ink flows like a river of blood.
Sco Open Server is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time Sco Open Server developers only serves to underscore the point more clearly. There can no longer be any doubt: Sco is dying.
Let's keep to the facts and look at the numbers.
Sco leader Darl McBride states that there are 7000 users of Sco. How many users of Sco are there? Let's see. The number of Linux versus Unix posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Sco users. Sco Open Server posts on Usenet are about half of the volume of Sco posts. Therefore there are about 700 users of Sco Open Server. A recent article put Sco Open Server at about 80 percent of the Sco market. Therefore there are (7000+1400+700)*4 = 36400 Sco users. This is consistent with the number of Sco Open Server Usenet posts.
Due to the troubles of The Sco Group, abysmal sales and so on, Sco went out of business and was taken over by IBM who sell another troubled OS. Now Sco is also dead, its corpse turned over to yet another charnel house.
All major surveys show that Sco has steadily declined in market share. Sco is very sick and its long term survival prospects are very dim. If Sco is to survive at all it will be among OS dilettante dabblers. Sco continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Sco is dead.
Fact: Sco is dying
I hope this was a joke I just didn't get. Have you ever been in the woods? This is simply impossible. Forests are not static things, but dymanic ever changing things. A critter could stop up your hole with nesting, or a tree could topple in its path. The wind will move trees back and forth, breaking the line of sight constantly.
As long as the world's population continues to grow, there's at least one.
Agriculture.
This would never float on my Linux.
They already know this, but that isn't what the law suit is about. The law suit is about $1 billion that SCO claims this alleged offense has cost them. Honestly I doubt they care if the code is there by this point. Taking the code out will only cause some one to write a replacement relatively quickly, and net SCO nothing.
Well, they could say this kernel source was created $DATE and here's a SCO kernel created on $DATE from this source. Now, if they compile the kernel source and out pops the same binary they've been distributing for years, they've got a good leg to stand on. Otherwise, they're FUBARed I'd say, but IANAL of course.
You're not distributing software in this scenario. People are not renting your Apache and Tomcat from you, they are renting/leasing a service. For $DOLLARS per $PAYPERIOD you provide them with dynamic web hosting; you do not provide them with Tomcat and Apache.
Now, assume I have my own company, and create a modified version of GPLed software, then rent it to you in binary format only. You have received a binary from me, meaning that I have distributed a binary compiled from modified GPL software to you. Under the terms of the GPL, I must provide you with my modified source code.
Sorry, but you're wrong. Even if it is GPLed doesn't neccessarily mean you can get the source from elsewhere. Here's a hypothetical. I get a copy of some GPLed software, make some cool ass changes, and then lease that software to you. Sure you can get the same source I got, but that doesn't mean you can get the modified source that created the binary you leased from me.
Oh, but they did mention one little area. SCO said it was simply impossible for Linux to have achieved such strong SMP support without one of two things:
1) A strong development platform.
2) SCO source.
They seem to have forgotten that Caldera gave Alan Cox a dual processor machine so he could write the Linux SMP code in the kernel.
Anything that can be made to run under one GNU/Linux distro can be made to run under another, and slackware is no exception. Indeed, slackware is perhaps the poster child for running proprietary applications on a distro they weren't designed for. It's so homogenious that major changes are rarely needed. Since you mentioned trouble with vmware, why don't you take a look at this page which documents exactly how to install vmware on slackware liux. I've done it several times with no problems, and find it to be a walk in the park.
See I don't have this problem. i realized a long time ago that if I sucked power from the vibrations of my cell-phone, that the vibrations would decrease. I also understand that vibration is in effect sound, so that this harnessing of vibration would silence the phone. I considered implementing this, but soon realized there was a much more efficient way to accomplish the same performance from my cell-phone, and retain battery life greater than this vibration harnessing technology can. I keep my cell phone turned off.
Welcome back tot he fold, brother.
This is still legal in GA. Case in point, last year when the new building at my Church was being finished, the bankers put a lien on it. To make matters worse, it was neither our fault nor our contractor's fault. He had previously done work on publicly owned buildings, and they hadn't paid him what he was owed. When the bank came to call, they put a lien on our building until the mess was straightened out. Why did they put a lien on us? Well, in GA, it's illegal to put a lien on publicly owned property, which means the government can shaft a contractor and pass the buck along to the next privately owned job until they can make good on their debts.
I assume your reasoning is doing this will hurt intel. If' that's so, that's messed up. You should be patenting buying intel processors so you can then charge royalties on anyone wishing to do the same. By patenting not buying intel chips, you're helping intel and hurting AMD.
You'll notice at the slackware store that there is a wonderful paperback book licensed under the GPL entitles, "Slackware Linux Essentials". It is perhaps one of the best linux books I have ever read and am thankful to be involved with.
Mysel and many of the "BOZOs" in alt.os.linux.slackware are currently working on a revised edition to bring this book up to date with the latest release of Slackware Linux. You can take a look at our (so far meager) progress here. I encourage anyone who wants to participate to give me an e-mail, you can find my address at that link, as well as a mailing list for this project. Any contributions would be greatly appreciated.
Slack on!