The good thing about the games is that if you aren't the best FPS shooter, you can be a Medic or Engineer and just play defense.
I wholeheartedly agree.
Even though the maps in Enemy Territory tend to be largish and without knowledge of a map's quirks and understanding the objectives you might end up wandering around waiting for someone to snipe you, a very good way of getting the hang of things is playing a medic.
Just hang back, follow the ones that seem to know what they're doing, avoid fire and keep your syringe ready.
Once you're starting to get the big picture, you might want to try engi or c-ops, just don't rush into fieldopshood - poor judgement with airstrikes is a sure way to get flamed:)
...and remember nobody likes a kamikaze panzer soldat.
Novell today also announced that IBM intends to make a $50 million investment in Novell convertible preferred stock. In addition, Novell and IBM are negotiating extensions to the current commercial agreements between IBM and SUSE LINUX for the continued support of SUSE LINUX on IBM's eServer products and middleware products to provide for product and marketing support arrangements related to SUSE LINUX. Both of these agreements will be effective when the acquisition of SUSE LINUX by Novell is completed.
'As the Canopy Group, which has a stake in SCO, also has interests in several other Linux companies, SCO was asked whether it planned to sue all these companies. The answer was "No. SCO has never planned to sue Linux companies."'
Translation: "SCO has been told it had better not have ever planned to sue companies in which Canopy is involved."
'Among the companies in which Canopy is involved is Linux Networx, which has supplied a supercomputer to the Lawrence Livermore National Laboratory; asked whether SCO would sue the laboratory, the company spokesperson said: "No. SCO has never made concrete plans to sue anyone."'
Translation: "Waitasec, it's a Canopy group company, right? Nope, not suing them then."
Note it's "never planned to sue Linux companies", not any Linux companies. I bet my leftie that with "Linux companies" they mean some subset of Linux companies in general.
Also, not having concrete plans probably only means they've not dared put anything on paper yet.
I wouldn't be surprised if we started seeing more switches from proprietary to oss in the future.
Even if in the IT biz we've accustomed to accepting very very ugly tactics if they're even remotely legally justifiable, it doesn't mean all businesses will want to have anything to do with corporations that employ such if there are alternatives.
Sometimes I wonder when stuff like 'the customer is always right' and such disappeared from the software industry. Well, not all of it. Shops doing custom stuff usually still treat their clients with some respect, at least way better than the large ones with a forcefed product portfolio do. But overall the software biz is starting to resemble some sort of drug pushing operation: "you know you need our product", "oh, that was yesterdays price, it's just doubled", "should you consider not conforming, you can expect a visit from a couple of our friends".
From the article:
"There is no warranty for infringement of intellectual property [in the GPL], so all of the liability ends up with end users."
"End users are improperly using this copyrighted material, and under copyright law SCO is entitled to damages and injunctive relief,"
The latter statement is close to the truth in that under copyright law they would be entitled to damages and injunctive relief should they be able to prove their case. What they seem to be implying that somehow it's the people who've bought a linux distro that should pay for their 'damages'. Which sounds, put mildly, a bit unreasonable. IANAL, but this appears to be pure FUD.
Read the copyright disclaimer in any book, and you'll not see any warranty for infringement. In fact you'll probably see something more like
THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT
(emphasis added). The example is from "Concurrent Programming in Java" by Doug Lea (Addison Wesley)
The end users are not trying to distribute the bits SCO claims to be theirs or derivative works thereof. SCO should be suing whoever sold the 'linux servers' they're in the process of 'identifying', but apparently consider it too risky.
They are trying to make a (possible although unlikely) case of copyright infringement by IBM seem like a violation of an license agreement between them and the end user. At the same time they're trying to convince everyone that the license they've been distributing their linux distro under is not valid and trying to scare people into accepting whatever licensing terms and prices they come up with.
The upside is that if the US legal system hasn't gone/completely/ bonkers, there seems to be no way they can win anything in court.
The downside is that they're making a lot of money with these scare tactics, thus setting an example, and they might be able to scare some companies/people into buying their licenses.
Which, like pointed out before, is just like paying the Mafia.
2.4.20 is roughly 3.5 million lines, although about 2.5 million lines of it is drivers. The SMP code (all platforms) seems to be ~15000 lines of which ~800000 lines is copied verbatim from sysV.
This isn't anything revolutionary though - the TCP slow start has been circumvented in most GPRS applications because the erratic nature of the airlink would cause the slowstart algorithm to decide there was network congestion and thus keep the window size minimal almost all the time.
BTW, UDP only has optional packet checksums and afaik they're seldom used.
I've two fluid bearing diamondmaxes and the only problem i've encountered (not what you'd call a slight problem) is that whenever the temperature inside Das Box gets past 40degC writes start to fail disastrously.
Other than that the disks work like a charm.
Slashdot Mirror
...they're gone.
Not much reason at all tbh.
...are here, at least for a while.
Not anything too witty either, "sad" describes them pretty well.
...is probably Richard Emerson.
Oh, and don't go out the back door.
I wholeheartedly agree.
Even though the maps in Enemy Territory tend to be largish and without knowledge of a map's quirks and understanding the objectives you might end up wandering around waiting for someone to snipe you, a very good way of getting the hang of things is playing a medic.
Just hang back, follow the ones that seem to know what they're doing, avoid fire and keep your syringe ready.
Once you're starting to get the big picture, you might want to try engi or c-ops, just don't rush into fieldopshood - poor judgement with airstrikes is a sure way to get flamed
--
dereksmalls@euroservers
Apparently Xmas took them by surprise and they need 90 more days to recover from the shock.
Also, it seems they haven't really caught anything so far and want to fish about that other nook too (non-sysV AIX and dynix stuff).
For once I find myself hoping the judge doesn't have a sense of humour.
Pretty well:
From the article:
'As the Canopy Group, which has a stake in SCO, also has interests in several other Linux companies, SCO was asked whether it planned to sue all these companies. The answer was "No. SCO has never planned to sue Linux companies."'
Translation: "SCO has been told it had better not have ever planned to sue companies in which Canopy is involved."
'Among the companies in which Canopy is involved is Linux Networx, which has supplied a supercomputer to the Lawrence Livermore National Laboratory; asked whether SCO would sue the laboratory, the company spokesperson said: "No. SCO has never made concrete plans to sue anyone."'
Translation: "Waitasec, it's a Canopy group company, right? Nope, not suing them then."
Note it's "never planned to sue Linux companies", not any Linux companies. I bet my leftie that with "Linux companies" they mean some subset of Linux companies in general.
Also, not having concrete plans probably only means they've not dared put anything on paper yet.
I'm paranoid? Ah, you're with them aren't you?
I wouldn't be surprised if we started seeing more switches from proprietary to oss in the future.
Even if in the IT biz we've accustomed to accepting very very ugly tactics if they're even remotely legally justifiable, it doesn't mean all businesses will want to have anything to do with corporations that employ such if there are alternatives.
Sometimes I wonder when stuff like 'the customer is always right' and such disappeared from the software industry. Well, not all of it. Shops doing custom stuff usually still treat their clients with some respect, at least way better than the large ones with a forcefed product portfolio do. But overall the software biz is starting to resemble some sort of drug pushing operation:
"you know you need our product",
"oh, that was yesterdays price, it's just doubled",
"should you consider not conforming, you can expect a visit from a couple of our friends".
From the article:
/completely/ bonkers, there seems to be no way they can win anything in court.
The downside is that they're making a lot of money with these scare tactics, thus setting an example, and they might be able to scare some companies/people into buying their licenses.
"There is no warranty for infringement of intellectual property [in the GPL], so all of the liability ends up with end users."
"End users are improperly using this copyrighted material, and under copyright law SCO is entitled to damages and injunctive relief,"
The latter statement is close to the truth in that under copyright law they would be entitled to damages and injunctive relief should they be able to prove their case. What they seem to be implying that somehow it's the people who've bought a linux distro that should pay for their 'damages'. Which sounds, put mildly, a bit unreasonable. IANAL, but this appears to be pure FUD.
Read the copyright disclaimer in any book, and you'll not see any warranty for infringement. In fact you'll probably see something more like
THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT
(emphasis added). The example is from "Concurrent Programming in Java" by Doug Lea (Addison Wesley)
The end users are not trying to distribute the bits SCO claims to be theirs or derivative works thereof. SCO should be suing whoever sold the 'linux servers' they're in the process of 'identifying', but apparently consider it too risky.
They are trying to make a (possible although unlikely) case of copyright infringement by IBM seem like a violation of an license agreement between them and the end user. At the same time they're trying to convince everyone that the license they've been distributing their linux distro under is not valid and trying to scare people into accepting whatever licensing terms and prices they come up with.
The upside is that if the US legal system hasn't gone
Which, like pointed out before, is just like paying the Mafia.
This isn't even very funny anymore.
"There are approximately 30 million lines of code in the kernel:" *bzzt* wrong. The dwheeler article line count is of RedHat 7.1, not the kernel.
2.4.20 is roughly 3.5 million lines, although about 2.5 million lines of it is drivers. The SMP code (all platforms) seems to be ~15000 lines of which ~800000 lines is copied verbatim from sysV.
I'm pretty sure that in the near future we'll see worms/virii displaying related messages while performing a low level format.
This isn't anything revolutionary though - the TCP slow start has been circumvented in most GPRS applications because the erratic nature of the airlink would cause the slowstart algorithm to decide there was network congestion and thus keep the window size minimal almost all the time. BTW, UDP only has optional packet checksums and afaik they're seldom used.
I've two fluid bearing diamondmaxes and the only problem i've encountered (not what you'd call a slight problem) is that whenever the temperature inside Das Box gets past 40degC writes start to fail disastrously. Other than that the disks work like a charm.