Not true! One of the biggest sources of water in Las Vegas and Phoenix is groundwater.
There are many other groundwater sources that would be used except they are too salty. Cheap desalinization technologies are high on the list of things to help with water problems in the southwest.
Other things that might happen include Vegas paying for desalinization in LA, and then using LA's portion of Lake Mead.
And as a fellow DOI employee, my take on this is they did no scoping or internal comment or ANYTHING to base this decision on. I do not think it is going to fly, in the long term.
My entire IT office is up in arms about this. With NO comments from the rank and file, many people are upset.
The rumor is that this was actually caused by someone blaming lack of standard email servers (Lotus Domino and Groupwise) for screwing up a email greeting/distribution from the Secretary. This problem was probably actually caused by network connectivity problems, rather than standardization issues. I got it fine from my Groupwise POP server.
Thus this unfunded mandate to move to some standard platform.
Given that there is no money behind it, and we're talking 40+ mill in LICENCES ALONE!!!
I don't see this happening anytime soon.
On the other hand, it is almost easier for Linux to interoperate with MS stuff than Novell, except Exchange/Outlook, which does have a non-free solution (Evolution).
Further, we have several pieces of Unix only software, and I don't see those being ported soon.
They used to have the domain home-ed-press.com, but lost it in a very similar case. See this.
What do you know? A whois query turns up the SAME company! Buy This Domain, at
5 Pechatnikova St., # 33
Yerevan, 375010
AM
It appears that this guy is a real sleazeball, looking for medium-high traffic sites that are expiring, and runs a domain registration race exploit.
This is bad, and should be stopped. This is pretty offensive, given that lots of homeschoolers would have strong objections to pron.
Is ICANN's UDRP policy strong enough to handle this type of issue, or is this type of operation, probably on a massive scale, not something that they can handle?
This guy ought to have his internet driver's license revoked.:P
Come on folks, I can't believe that Microsoft would have sent that email without thinking VERY carefully about what they were getting into.
(Of course, that could be wrong, considering how busy their lawyers must be with the anti-trust suit, and the instant mirroring of DeCSS around the world!)
I'm not sure that they released the spec for malicious reasons (although it is suspicious), but they must think they have a bulletproof case here to email/. of all sites!
The most important point of all this is to act responsibly!
Since I've been hearing all about this, and figure it can't be too bad, I wanted to help out with the Mozilla effort.
However, Mozilla doesn't run AT ALL on solaris currently, and there appears to be multiple nasty bugs keeping that from happening, even if I build it from source. (at least some are understood fairly well)
Therefore, I'll stick with Netscape, but all that's keeping me from beating on Mozilla is the fact that it is not available for my platform. UG!
At the university here, the unix sysadmin group (Hi guys!) claimed that Star Office had a poor networking installation mode, and performed poorly in a client/server architecture.
This is interesting, but how do you prove it? I mean, all they've got is the fact that NSAKEY showed up as a debugging symbol. Sure NSA happens to be the acronym of a particularly annoying secret government agency, but...
At least, it DOES appear that there is more than one key available in the crypto packages. Whose keys? This should be the rallying call, and since we don't have the code, we can't tell.
This is a VERY good reason to be suspicious of Microsoft products.
How many people actually USE the cryptoAPI? It seems to me that unless you're using this stuff, all of this has no effect.
This link is germane and interesting, but also presents a solution for at least one order of magnitude more email users. 350,000 + was referenced, and the paper is from 1997.
"If it's worth doing, someone probably already has" is quite true in this situation, and seems to be the case for most of the things I try to do.:)
Downsides: The architecture described does not handle IMAP, as they hadn't implemented it.
>This isn't possible with the GPL. It's always there, blatantly in your face, telling you `You > may not use this code in proprietary ventures.' If a company takes your work, repackages it and > sells the repackaging and service for it, your code is still available. It isn't legally >permissible for them to take your code, incorporate it into another product and sell that product.
But not quite... as I understand it, it IS legally permissable for them to take your code, incorporate it, and sell that product. They ARE required to give the altered version of the code to everyone they sell it to, or to everyone that uses it. This is important, not only for this commercial case, but also for internal uses by companies. If I alter a GPL'd product, but only give binaries to people inside my company, I just have to give them the code as well, or tell them where to get it.
This is a point that I see sometimes missed or downplayed. The GPL does not mean that you are required to release your code to the public always, but only to those you give the product to!
As far as the comparison between the licenses, I have to say "no opinion."
Not true! One of the biggest sources of water in Las Vegas and Phoenix is groundwater.
There are many other groundwater sources that would be used except they are too salty. Cheap desalinization technologies are high on the list of things to help with water problems in the southwest.
Other things that might happen include Vegas paying for desalinization in LA, and then using LA's portion of Lake Mead.
Well, it installed and ran fine with demos etc, but
trying it in RTCW:ET blew up, and the visuals had some artifacts.
Gug.
Nice. Ati's site didn't have Xfree 4.3 drivers, but
his does.
Binary drivers worked this time, anyway.
And as a fellow DOI employee, my take on this is they did no scoping or internal comment or ANYTHING to base this decision on. I do not think it is going to fly, in the long term.
My entire IT office is up in arms about this. With NO comments from the rank and file, many people are upset.
The rumor is that this was actually caused by someone blaming lack of standard email servers (Lotus Domino and Groupwise) for screwing up a email greeting/distribution from the Secretary. This problem was probably actually caused by network connectivity problems, rather than standardization issues. I got it fine from my Groupwise POP server.
Thus this unfunded mandate to move to some standard platform.
Given that there is no money behind it, and we're talking 40+ mill in LICENCES ALONE!!!
I don't see this happening anytime soon.
On the other hand, it is almost easier for Linux to interoperate with MS stuff than Novell, except Exchange/Outlook, which does have a non-free solution (Evolution).
Further, we have several pieces of Unix only software, and I don't see those being ported soon.
They used to have the domain home-ed-press.com, but lost it in a very similar case. See this.
What do you know? A whois query turns up the SAME company! Buy This Domain, at
5 Pechatnikova St., # 33
Yerevan, 375010
AM
It appears that this guy is a real sleazeball, looking for medium-high traffic sites that are expiring, and runs a domain registration race exploit.
This is bad, and should be stopped. This is pretty offensive, given that lots of homeschoolers would have strong objections to pron.
Is ICANN's UDRP policy strong enough to handle this type of issue, or is this type of operation, probably on a massive scale, not something that they can handle?
This guy ought to have his internet driver's license revoked. :P
Ah well, we can dream about it.
I have to agree here, at least in part.
/. of all sites!
Come on folks, I can't believe that Microsoft would have sent that email without thinking VERY carefully about what they were getting into.
(Of course, that could be wrong, considering how busy their lawyers must be with the anti-trust suit, and the instant mirroring of DeCSS around the world!)
I'm not sure that they released the spec for malicious reasons (although it is suspicious), but they must think they have a bulletproof case here to email
The most important point of all this is to act responsibly!
One correction: Apparently the instructions are
64 or 128 bit wide.
(Perusing the tech white paper...)
Enjoy!
This works, even on RV 5.0. (Solaris even!)
Hoorah!
Since I've been hearing all about this, and figure it can't be too bad, I wanted to help out with the Mozilla effort.
However, Mozilla doesn't run AT ALL on solaris currently, and there appears to be multiple nasty bugs keeping that from happening, even if I build it from source. (at least some are understood fairly well)
Therefore, I'll stick with Netscape, but all that's keeping me from beating on Mozilla is the fact that it is not available for my platform. UG!
At the university here, the unix sysadmin group (Hi guys!) claimed that Star Office had a poor networking installation mode, and performed poorly in a client/server architecture.
Can anyone else confirm this?
Andrew
Indeed, this should be followed up with a "Hacker's Guide to Packet Switched Visual and Audible Analog Communication."
This is interesting, but how do you prove it? I mean, all they've got is the fact that NSAKEY showed up as a debugging symbol. Sure NSA happens to be the acronym of a particularly annoying secret government agency, but...
At least, it DOES appear that there is more than one key available in the crypto packages. Whose keys? This should be the rallying call, and since we don't have the code, we can't tell.
This is a VERY good reason to be suspicious of Microsoft products.
How many people actually USE the cryptoAPI? It seems to me that unless you're using this stuff, all of this has no effect.
Andrew
----
This link is germane and interesting, but also presents a solution for at least one order of magnitude more email users. 350,000 + was referenced, and the paper is from 1997.
:)
"If it's worth doing, someone probably already has" is quite true in this situation, and seems to be the case for most of the things I try to do.
Downsides: The architecture described does not handle IMAP, as they hadn't implemented it.
Share and Enjoy!
--
This stuff sickens a bit. I like computers and all, but I've got a LIFE.
Scenes like this are why I'm not directly in CS. With a wife and kids, I'll put in a good 40 hour week, thanks, and then GO HOME.
My aunt complains of deafness from too much loud music 20 years ago. I wonder what not enough sleep will do to these folks in the long run.
E/INFP... yep, I'll ring in as one more.
Pretty cool to see us 5%ers posting.
>This isn't possible with the GPL. It's always there, blatantly in your face, telling you `You
> may not use this code in proprietary ventures.' If a company takes your work, repackages it and
> sells the repackaging and service for it, your code is still available. It isn't legally
>permissible for them to take your code, incorporate it into another product and sell that product.
But not quite... as I understand it, it IS legally permissable for them to take your code, incorporate it, and sell that product. They ARE required to give the altered version of the code to everyone they sell it to, or to everyone that uses it. This is important, not only for this commercial case, but also for internal uses by companies. If I alter a GPL'd product, but only give binaries to people inside my company, I just have to give them the code as well, or tell them where to get it.
This is a point that I see sometimes missed or downplayed. The GPL does not mean that you are required to release your code to the public always, but only to those you give the product to!
As far as the comparison between the licenses, I have to say "no opinion."
Share and Enjoy!
Indeed, this is the key to our whole point. This is the question to ask.
Alan Cox wrote a useful little discussion about this, relating to the Linux on 8086 project. (heh)
Where's the code?
They've been dealing with this problem with netrek clients for ages.
The client source is available, but to be allowed to play against many servers, they have to "know" your clients key.
And the keys are not easy to get.
RSA is also an option available there.
Now, mind you, I'm no netrek God, but I know this problem's been worked on alot already.
This is looking more like a lesson in "How NOT to manage your Geek." Perhaps his managers missed those last few /. discussions on the subject.
/.
This pretty much invalidates most of the 400+ messages to the previous info.
It still sounds to me like Red Hat is doing right by us. I mean, they are STILL releasing everything as GPL.
Careful folks, or we might give Paranoia a new definition: see
Andrew Gilmore
(gotta do something while my home directory gets restored from tape!)