You might want to check yours. The code WAS returned to the original developers or publishers pretty much in it's entirety- at least that's what I've heard from ex-Loki developers and other parties that would know the exact details. The problem was that Loki's deals muddied the waters. There was some legal issues with regards to at least some of the ports that were done or were in progress at the time Loki shuttered it's doors. In the case of Kohan, Timegate was checking into the matter and considering going with LGP for the next set of versions, etc.- but while they wanted to do a Linux version, they didn't want to wait for the legal issues to settle on the Loki developed port. Enter Transgaming and the Winelib versions. As for DeusEx, they weren't spending ANY money on that- if you believe that, you don't know much about how porting goes. Loki spent all the money on the port up to that point and it was in Beta at the time Loki expired.
What most people don't seem to understand is that it's not the President that's the source of most of the woes we're seeing in this day and age.
The Administration is responsible for managing the obtaining of monies for the government in the form of taxes and tariffs. The Administration is responsible for signing off approved budgets and enacting the laws of the country. Congress is responsible for determining the allocations of actual spending for this country (Not the President...) and enacting various laws that may help or hinder the country.
Do not lay the blame solely on Clinton, Bush (Jr. or Sr.) or Reagan. It's as much CONGRESS' fault as it is theirs. It never ceases to amaze me that people keep buying into that false belief that it's the President's fault for all of the economic problems, etc.
It's difficult getting into the driver development arena- especially for graphics adapters. You almost have to have done work for a while on DRI or Utah-GLX to get them to take you seriously in the big boys (ATI and NVidia...). I'm still waiting for an answer back for a long-term contract w/them within the team in question- and I've been doing Linux drivers for some time and I've done various things with Utah-GLX over the years and some small smattering of things with DRI.
It depends on how the DMA framework, etc. is laid out. All things being equal, it's relatively simple to code for both OSes- but many driver teams in the past took shortcuts that require more dedicated work.
The whole thing's civil and is limited to what they're claiming. Any notice under the DMCA is a legal document and is limited in scope to what is claimed in the notice and nothing more. If they didn't check that the file was in fact infringing and they claim it is- and it's not... Well, that's purjory, pure and simple.
They are authorized to act only on behalf of the MEMBER companies. Simply put, they're not authorized to act on my behalf or anyone else that doesn't meet the criteria.
That makes it definitely purjory and maybe even fraud considering that they're claiming that they're acting on those people's behalf when they aren't.
It's definitely actionable and someone should call them on it- it'll stop the whole thing pretty quick once they find out that they can be held liable under various other laws and can be stuck with some pretty nasty punitive damages as a result.
It's more like lack of staff, I believe. They've got something like roughly 4% as many developers doing Linux development as they do Windows developers- and these are developers dedicated to Linux driver development.
And they HAVE recently hired relevent experience- Michel Danzer just hired on out there and he's one of the DRI team's better developers. I don't know if the problems are due to them not doing something like NVidia (which is that their driver core is largely the same codebase for Linux and Windows...) or if it's that combined with the shortage of capable people working on them.
Chernobyl and TMI happen to be worse than the proponents tend to make them. In the case of TMI, if a few more things had gone wrong it'd been about as bad as Chernobyl. We still don't know what damage Chernobyl is going to have caused. Isotopes of Cesium, Iodine, and Thorium in dangerous dosage levels were released with Chernobyl. There's places in that area of the country that are technically uninhabitable because they're still too hot to be safe to live in.
Chernobyl is a catastrophe- one brought about with carelessness with an extremely dangerous process for producing energy.
Now, having said this, we're contaminating the environment with equally nasty contaminants with the current generation schemes. Nuke power, if designed with the hazards really and truely in mind is going to be better and safer than the fossil fueled processes. Pebble Bed reactors are the first such design.
In the US, the Telecom companies keep looking at broadband as the product, instead of the means to provide the product. As a result, it's not "profitable" to do the rollouts like they have in Korea and Sweden (and Canada, and...). The profit isn't in moving bits about. It's in the manner in which the bits are generated and collected. If you've got a fat enough pipe, you can do clever things like video on demand (Don't think just movies- think being able to watch any show on TV when you want to after the first timeslot for showing...), VoIP, digital conferencing, etc. All from the same pipe- billed in the manner that the mobile services are now. That's profitable indeed- but the phone and cable companies are too mired in the past (this is the way we've always made money...) to wise up.
It's not just 64 bits that we're talking about here- it's a larger register pool with the AMD64 architechture. This WILL affect many things end-users do.
(Not to mention that an Athlon64 in 32-bit mode seems to stack up rather nicely against the P4 clocked half again faster... Go figure...:-)
Disagree all you want, but they're eroding our rights by basically buying laws from our Legislature- laws that have nothing to do with the interests of the people, but rather perpetuating their frigging monopoly.
In my opinion, you're not entitled to make money doing anything you choose. You're entitled to the attempt to make money and that's all- if you succeed, great, but you're not entitled to the money. RIAA acts as if they're entitled to make money in perpetuity and has hoodwinked everyone in charge to give them that in what is very likely to be a violation of the Constitutional grant of authority to the government.
For that, they need to stop- AND apologize to everyone.
It's not illegal to lie to the press and this judge can't do anything to stop them.
Survey says...
***BZZZT***
Oh, sorry, you lose, thank you for playing.
If you lie to the press in a manner that is damaging to a competitor or other business, it's called Trade Libel. This is a violation of the Lanham Act and as such is something that the Judge in question can do something in regards to stopping them- especially since IBM has filed a complaint against SCO in this regard as part of their countersuit.
They're claiming that it's much more secure that Unix/Linux with this service patch. In terms of being 0wned, it's hard to totally cover your tracks in a Unix box- you leave a trail of breadcrumbs somewhere that typically can be seen (most tools simply automate the process...). In the case of an SP2 XP box, it'a apparently rather easy to cover one's tracks and you have to rely on signature scanning (i.e. Virus/Trojan scanning...) to hope you can find the intruder.
I don't consider that to be a non-problem, nor do I consider it to be more secure. It's definitely not secure enough to be allowed exposure to critical infrastructure of any kind.
The reality is that there will be terrorism so long as the people practicing it think that they can achieve their goals through it.
Being nice to these people will not make it go away any more than "destroying" it will- they want to destroy EVERYTHING we are partly because we're rich and decadent (not to mention not of Islam in the case of the current crop of terrorists...). One of Osama's primary goals is to render us a religious oligarchy under the religion of Islam. You can't nice your way out of that sort of goal- it's not how our foriegn policy has been that he came up with that.
Sorry, but you can tell if it's band-aids or not. Emperical evidence thereof exists and can be shown in the history of the exploits that get reported for IE, IIS, Office, Exchange/Outlook, and Windows.
Many of the exact symptoms of the holes found get fixed only to have a different variant of pretty much the same exploit pop back up- something that wouldn't happen if the problem was fixed properly instead of just being "fixed". That's indicative of NOT fixing the big problems correctly.
The typical 10 year government contract obligates them to support the same product as installed or guarantee that any upgrades will not break any apps or majorly disrupt their daily operations. That's not something that MS is really ready for since they deep-down don't care about 98 users only 5 years out- and you won't get any support for it and they won't help you migrate to new solutions, you have to buy them and figure out how to make all your stuff work.
Do you honsestly think that MS will get enough money from this deal to be able to provide that sort of level of support for this somewhat small account? If you do, I've got some nice beachfront property in Arizona to sell you...
No, this is a stupid PR deal that they're trying to float to see if they can get people back on their bandwagon. If they screw it up or it doesn't shore up their bottom line (they're not posting profits like they used to lately...) then it's going to cost them a hell of a lot more than they'll see with the deal they worked out with the city. And if they back out or fail to live up to their end of the deal, they're going to face a nice n' nasty breach of agreement suit.
I'd call that a little more than a company not in trouble- you don't enter into these sorts of contracts on a whim as the only way out is via mediation and settlement or going bankrupt. That's not to say you shouldn't be going into those sorts of deals, but your business had better be predicated on doing these sorts of deals from the start or else you'll just get burned bad.
IF and only IF they throw the whole damn thing out and start over.
Windows is too complex to fix in in it's current incarnation. With COM/DCOM, ActiveX, band-aids piled on top of band-aids instead of fixing things right the first time, it's amazing that XP even WORKS let alone is as "secure" as it currently is (It's the most robust and secure OS from MS to date and it's still got the holes of a seive...).
Sure security is their top priority- but after the fact is the worst possible time to be worrying about that sort of thing. It's just NOT going to happen the way you're claiming- it's a sysiphean task to begin with and adding the problems of not breaking everything that wasn't designed with security in mind just makes it ten times worse.
That Copyrights aren't the same as Patents. Users typically aren't actionable for past and current infringements of Copyright unless they themselves are guilty of willful and active infringement- and typically don't owe anything on it. The worst that could have ever come out of this whole thing would be that SCO was right, there was some infringing code and it'd have to come out to be legit under the GPL- once that happened everything would be back to complete normal for the end-users. The only people that would be actionable and possibly facing stautory damages would be the guilty parties of the active act of infringement, not the contributory part. Worse, since SCO's pretty much made a botch job of their enforcement of any possible IP rights by way of keeping it secret- you're supposed to tell the infringers what they're infringing upon so they are obligated to stop. Failing to do so may be an estoppel on their pursuing anyone that currently is infringing- and may cause them to lose rights to the alleged IP with regards to it's use within Linux.
$700 to throw at a potential problem- no, that's not a lot.
$700 to throw at a NON-problem (which is what this is, no matter how you slice it...) is far, far too much.
I can't see what you've said as being really insightful- what you've said is valid, but only in the context of a possible or probable problem and SCO's just not a reality and they're about to be NUKED from orbit by Novell. If Novell gets that Dismissal with Predjudice, I expect that the whole damn SCO mess will implode within a day or so- they didn't own the IP rights at the beginning of all these cases so they're actionable under the Lanham Act and pretty much all of their cases go *POOF*, including the IBM one (since Novell executed their rights per the APA to waive any issues regarding contract or IP with regards to the SVR4 source base...) with SCO facing countersuits and suits regarding their obvious Lanham Act violations, Copyright infringements, and Patent infringements.
Do you have anything other than opinion backing up the claim you just made? It's been modded "informative" and unless it's backed up with some sort of proof (it's my understanding that Darwin/MacOS X is a BSD personality layered on top of Mach...) I can't see the comment as anything other than conjecture and thereby not "informative".
But, in light of the fact that they approved Windows for use in medical equipment of any kind, I doubt they're doing their stated role here (Though, looking back on all the things that they've approved that weren't safe at all and all the things that ARE that they haven't approved and never probably will, I don't think they've got that role down very well at all- the safety role, that is...).
The AC posting in the parent has it right in ONE. Why do you need Windows for most medical systems? Convienent UI? You can get that with any of the usual suspects in the embedded arena- and it'll be 100% as good as the Windows UI with the ability to certify the OS for safety use. This is one of those areas where I'd rather have an OS that has been or could concievably be certified for FAA approved use.
Slashdot Mirror
That's just PEACHY, now isn't it?
How in the hell are they supposed to pursue the case? Sorry guys, that doesn't wash.
You might want to check yours. The code WAS returned to the original developers or publishers pretty much in it's entirety- at least that's what I've heard from ex-Loki developers and other parties that would know the exact details. The problem was that Loki's deals muddied the waters. There was some legal issues with regards to at least some of the ports that were done or were in progress at the time Loki shuttered it's doors. In the case of Kohan, Timegate was checking into the matter and considering going with LGP for the next set of versions, etc.- but while they wanted to do a Linux version, they didn't want to wait for the legal issues to settle on the Loki developed port. Enter Transgaming and the Winelib versions. As for DeusEx, they weren't spending ANY money on that- if you believe that, you don't know much about how porting goes. Loki spent all the money on the port up to that point and it was in Beta at the time Loki expired.
What most people don't seem to understand is that it's not the President that's the source of most of the woes we're seeing in this day and age.
The Administration is responsible for managing the obtaining of monies for the government in the form of taxes and tariffs. The Administration is responsible for signing off approved budgets and enacting the laws of the country. Congress is responsible for determining the allocations of actual spending for this country (Not the President...) and enacting various laws that may help or hinder the country.
Do not lay the blame solely on Clinton, Bush (Jr. or Sr.) or Reagan. It's as much CONGRESS' fault as it is theirs. It never ceases to amaze me that people keep buying into that false belief that it's the President's fault for all of the economic problems, etc.
It's more like they have their collective neural net placed in their collective anus...
It's difficult getting into the driver development arena- especially for graphics adapters. You almost have to have done work for a while on DRI or Utah-GLX to get them to take you seriously in the big boys (ATI and NVidia...). I'm still waiting for an answer back for a long-term contract w/them within the team in question- and I've been doing Linux drivers for some time and I've done various things with Utah-GLX over the years and some small smattering of things with DRI.
It depends on how the DMA framework, etc. is laid out. All things being equal, it's relatively simple to code for both OSes- but many driver teams in the past took shortcuts that require more dedicated work.
It's definitely world class as AI's go- Artificial Idiots, that is...
The whole thing's civil and is limited to what they're claiming. Any notice under the DMCA is a legal document and is limited in scope to what is claimed in the notice and nothing more. If they didn't check that the file was in fact infringing and they claim it is- and it's not... Well, that's purjory, pure and simple.
They are authorized to act only on behalf of the MEMBER companies. Simply put, they're not authorized to act on my behalf or anyone else that doesn't meet the criteria.
That makes it definitely purjory and maybe even fraud considering that they're claiming that they're acting on those people's behalf when they aren't.
It's definitely actionable and someone should call them on it- it'll stop the whole thing pretty quick once they find out that they can be held liable under various other laws and can be stuck with some pretty nasty punitive damages as a result.
It's more like lack of staff, I believe. They've got something like roughly 4% as many developers doing Linux development as they do Windows developers- and these are developers dedicated to Linux driver development.
And they HAVE recently hired relevent experience- Michel Danzer just hired on out there and he's one of the DRI team's better developers. I don't know if the problems are due to them not doing something like NVidia (which is that their driver core is largely the same codebase for Linux and Windows...) or if it's that combined with the shortage of capable people working on them.
Chernobyl and TMI happen to be worse than the proponents tend to make them. In the case of TMI, if a few more things had gone wrong it'd been about as bad as Chernobyl. We still don't know what damage Chernobyl is going to have caused. Isotopes of Cesium, Iodine, and Thorium in dangerous dosage levels were released with Chernobyl. There's places in that area of the country that are technically uninhabitable because they're still too hot to be safe to live in.
Chernobyl is a catastrophe- one brought about with carelessness with an extremely dangerous process for producing energy.
Now, having said this, we're contaminating the environment with equally nasty contaminants with the current generation schemes. Nuke power, if designed with the hazards really and truely in mind is going to be better and safer than the fossil fueled processes. Pebble Bed reactors are the first such design.
In the US, the Telecom companies keep looking at broadband as the product, instead of the means to provide the product. As a result, it's not "profitable" to do the rollouts like they have in Korea and Sweden (and Canada, and...). The profit isn't in moving bits about. It's in the manner in which the bits are generated and collected. If you've got a fat enough pipe, you can do clever things like video on demand (Don't think just movies- think being able to watch any show on TV when you want to after the first timeslot for showing...), VoIP, digital conferencing, etc. All from the same pipe- billed in the manner that the mobile services are now. That's profitable indeed- but the phone and cable companies are too mired in the past (this is the way we've always made money...) to wise up.
It's not just 64 bits that we're talking about here- it's a larger register pool with the AMD64 architechture. This WILL affect many things end-users do.
:-)
(Not to mention that an Athlon64 in 32-bit mode seems to stack up rather nicely against the P4 clocked half again faster... Go figure...
Disagree all you want, but they're eroding our rights by basically buying laws from our Legislature- laws that have nothing to do with the interests of the people, but rather perpetuating their frigging monopoly.
In my opinion, you're not entitled to make money doing anything you choose. You're entitled to the attempt to make money and that's all- if you succeed, great, but you're not entitled to the money. RIAA acts as if they're entitled to make money in perpetuity and has hoodwinked everyone in charge to give them that in what is very likely to be a violation of the Constitutional grant of authority to the government.
For that, they need to stop- AND apologize to everyone.
Not that it's going to ever happen, mind.
Survey says...
***BZZZT***
Oh, sorry, you lose, thank you for playing.
If you lie to the press in a manner that is damaging to a competitor or other business, it's called Trade Libel. This is a violation of the Lanham Act and as such is something that the Judge in question can do something in regards to stopping them- especially since IBM has filed a complaint against SCO in this regard as part of their countersuit.
They're claiming that it's much more secure that Unix/Linux with this service patch. In terms of being 0wned, it's hard to totally cover your tracks in a Unix box- you leave a trail of breadcrumbs somewhere that typically can be seen (most tools simply automate the process...). In the case of an SP2 XP box, it'a apparently rather easy to cover one's tracks and you have to rely on signature scanning (i.e. Virus/Trojan scanning...) to hope you can find the intruder.
I don't consider that to be a non-problem, nor do I consider it to be more secure. It's definitely not secure enough to be allowed exposure to critical infrastructure of any kind.
The reality is that there will be terrorism so long as the people practicing it think that they can achieve their goals through it.
Being nice to these people will not make it go away any more than "destroying" it will- they want to destroy EVERYTHING we are partly because we're rich and decadent (not to mention not of Islam in the case of the current crop of terrorists...). One of Osama's primary goals is to render us a religious oligarchy under the religion of Islam. You can't nice your way out of that sort of goal- it's not how our foriegn policy has been that he came up with that.
I don't really play Windows games.
Sorry, but you can tell if it's band-aids or not. Emperical evidence thereof exists and can be shown in the history of the exploits that get reported for IE, IIS, Office, Exchange/Outlook, and Windows.
Many of the exact symptoms of the holes found get fixed only to have a different variant of pretty much the same exploit pop back up- something that wouldn't happen if the problem was fixed properly instead of just being "fixed". That's indicative of NOT fixing the big problems correctly.
The typical 10 year government contract obligates them to support the same product as installed or guarantee that any upgrades will not break any apps or majorly disrupt their daily operations. That's not something that MS is really ready for since they deep-down don't care about 98 users only 5 years out- and you won't get any support for it and they won't help you migrate to new solutions, you have to buy them and figure out how to make all your stuff work.
Do you honsestly think that MS will get enough money from this deal to be able to provide that sort of level of support for this somewhat small account? If you do, I've got some nice beachfront property in Arizona to sell you...
No, this is a stupid PR deal that they're trying to float to see if they can get people back on their bandwagon. If they screw it up or it doesn't shore up their bottom line (they're not posting profits like they used to lately...) then it's going to cost them a hell of a lot more than they'll see with the deal they worked out with the city. And if they back out or fail to live up to their end of the deal, they're going to face a nice n' nasty breach of agreement suit.
I'd call that a little more than a company not in trouble- you don't enter into these sorts of contracts on a whim as the only way out is via mediation and settlement or going bankrupt. That's not to say you shouldn't be going into those sorts of deals, but your business had better be predicated on doing these sorts of deals from the start or else you'll just get burned bad.
IF and only IF they throw the whole damn thing out and start over.
Windows is too complex to fix in in it's current incarnation. With COM/DCOM, ActiveX, band-aids piled on top of band-aids instead of fixing things right the first time, it's amazing that XP even WORKS let alone is as "secure" as it currently is (It's the most robust and secure OS from MS to date and it's still got the holes of a seive...).
Sure security is their top priority- but after the fact is the worst possible time to be worrying about that sort of thing. It's just NOT going to happen the way you're claiming- it's a sysiphean task to begin with and adding the problems of not breaking everything that wasn't designed with security in mind just makes it ten times worse.
That Copyrights aren't the same as Patents. Users typically aren't actionable for past and current infringements of Copyright unless they themselves are guilty of willful and active infringement- and typically don't owe anything on it. The worst that could have ever come out of this whole thing would be that SCO was right, there was some infringing code and it'd have to come out to be legit under the GPL- once that happened everything would be back to complete normal for the end-users. The only people that would be actionable and possibly facing stautory damages would be the guilty parties of the active act of infringement, not the contributory part. Worse, since SCO's pretty much made a botch job of their enforcement of any possible IP rights by way of keeping it secret- you're supposed to tell the infringers what they're infringing upon so they are obligated to stop. Failing to do so may be an estoppel on their pursuing anyone that currently is infringing- and may cause them to lose rights to the alleged IP with regards to it's use within Linux.
$700 to throw at a potential problem- no, that's not a lot.
$700 to throw at a NON-problem (which is what this is, no matter how you slice it...) is far, far too much.
I can't see what you've said as being really insightful- what you've said is valid, but only in the context of a possible or probable problem and SCO's just not a reality and they're about to be NUKED from orbit by Novell. If Novell gets that Dismissal with Predjudice, I expect that the whole damn SCO mess will implode within a day or so- they didn't own the IP rights at the beginning of all these cases so they're actionable under the Lanham Act and pretty much all of their cases go *POOF*, including the IBM one (since Novell executed their rights per the APA to waive any issues regarding contract or IP with regards to the SVR4 source base...) with SCO facing countersuits and suits regarding their obvious Lanham Act violations, Copyright infringements, and Patent infringements.
Do you have anything other than opinion backing up the claim you just made? It's been modded "informative" and unless it's backed up with some sort of proof (it's my understanding that Darwin/MacOS X is a BSD personality layered on top of Mach...) I can't see the comment as anything other than conjecture and thereby not "informative".
But, in light of the fact that they approved Windows for use in medical equipment of any kind, I doubt they're doing their stated role here (Though, looking back on all the things that they've approved that weren't safe at all and all the things that ARE that they haven't approved and never probably will, I don't think they've got that role down very well at all- the safety role, that is...).
The AC posting in the parent has it right in ONE. Why do you need Windows for most medical systems? Convienent UI? You can get that with any of the usual suspects in the embedded arena- and it'll be 100% as good as the Windows UI with the ability to certify the OS for safety use. This is one of those areas where I'd rather have an OS that has been or could concievably be certified for FAA approved use.