Well they're the ones who issued Microsoft certificates to a fraudster. And the ones who implemented Site Finder. They also did a bit of securities fraud (options backdating).
None of the console manufacturers have announce *any* information about their next generation or products. So why bother creating straw men for your case?
The argument was that we should let the manufacturers off about the unsafety of this generation, because the next generation might be better. There is no evidence that the next generation will be better, so that argument is fairly bad.
How many companies changed their product, midcycle, to comply before they were legally compelled to?
Some did, but obviously not enough, or RoHS laws would not have been necessary. We can still criticize the companies for gambling with our safety.
*unless there's a heavy marketing angle in it.
That's what Greenpeace is trying to accomplish. I'm sure that Greenpeace wouldn't mind having a law forbidding brominated flame retardants, but in the meantime they have to work with what they have.
Anyway, now is the time to complain anyway, because it's at this time that decisions for the next console are being made. So far none of the manufacturers have announced anything related to improved product safety for their next consoles, so blindly hoping that it will be better is probably naive.
The BROADCAST was for support for obsolete IP stacks. Yes, DHCP servers should still support it, but given that noone used it, some of the newer DHCP servers didn't implement support for it. Hardly surprising.
The fact is that "A client that can receive unicast IP datagrams before its protocol software has been configured SHOULD clear the BROADCAST bit to 0." Vista CAN receive unicast IP datagrams before its protocol software has been configured, it just drops them unless a registry entry is defined.
The RFC's are based on the principle of "be strict in what you send and lenient in what you expect". Vista breaks the first rule and the various router DHCP servers broke the second.
I simply can't think of an innocent reason to have a registry entry which out to be called be_incompatible and having it default to "yes".
So, amazingly enough, the manufacturers didn't dump their hundreds of millions of dollars of investments, six months in to their ten year lives, just because Greenpeace told them to? Why that's just crazy.
Other manufacturers have managed to change their then-current products. E.g. the ROHS program, which forced manufacturers to remove lead (and other things) from their products -- for a while it was fairly hard to get the WRT54GL, but a month later that was all cleared up.
Changing the way you produce a motherboard or replacing brominated flame retardants (nasty stuff, by the way) with something safer doesn't require a product redesign.
Not "exactly the same thing happens with the GPL". See if I spend 5 years developing a program, and for some reason if GPL code happens to slip into it (junior programmer), and it gets released before the problem is found, I now have to release all the source to my entire program.
No you don't. You have to pay the fine and the compensation and stop distributing your program. The GPL isn't an EULA, if you don't like it then you can just ignore it and be subject to usual copyright rules.
Normally, DHCP servers and BOOTP relay agents attempt to deliver
DHCPOFFER, DHCPACK and DHCPNAK messages directly to the client using
uicast delivery. The IP destination address (in the IP header) is
set to the DHCP 'yiaddr' address and the link-layer destination
address is set to the DHCP 'chaddr' address. Unfortunately, some
client implementations are unable to receive such unicast IP
datagrams until the implementation has been configured with a valid
IP address (leading to a deadlock in which the client's IP address
cannot be delivered until the client has been configured with an IP
address).
A client that cannot receive unicast IP datagrams until its protocol
software has been configured with an IP address SHOULD set the
BROADCAST bit in the 'flags' field to 1 in any DHCPDISCOVER or
DHCPREQUEST messages that client sends. The BROADCAST bit will
provide a hint to the DHCP server and BOOTP relay agent to broadcast
any messages to the client on the client's subnet. A client that can
receive unicast IP datagrams before its protocol software has been
configured SHOULD clear the BROADCAST bit to 0.
That's from RFC 2131, published March 1997. Guess what? Vista apparently has a deficient IP stack which "cannot receive unicast IP datagrams until its protocol software has been configured with an IP address.". At least it sets the BROADCAST bit. It gets even stupider, because Vista actually HAS a modern IP stack, and CAN receive unicast without having an IP address. You just need to set a registry entry.
Needless to say, not every router vendor supported the BROADCAST bit in their DHCP servers. Well now they do.
No. If you get caught, you would likely be forbidden from distributing it anymore, and you pay Microsoft and Borland compensation for the copies already distributed. Exactly the same happens with the GPL.
Unless you didn't distribute it at all, in which case it all depends on the EULA. The GPL allows you to do whatever you want if you don't distribute the result, by the way.
but I'm not entirely sure that they could just cease distributing the code since it is already "out there" now
That can happen in copyright violations where the GPL isn't involved too, and indeed it's common in many kinds of law suits that the defendant is unable to undo the harm he did. Monetary compensation is often used instead.
Copyright isn't viral. If you integrate your code and someone else's code (to which you do not have a license), there's nothing viral about that. You simply violated copyright and neither party has rights to the combined code.
That is exactly the same with GPL-licensed code. The only difference is that authors of GPL software quite often drop their cases when the defendant decides to free their software. Authors of proprietary software rarely show such courtesy. Either way, it's up to the defendant to negotiate a settlement or to accept their punishment (and to lobby to get copyright law changed, perhaps).
Re:Which seems to make sense over all
on
F-22 Raptor Cancelled
·
· Score: 2, Informative
Aircraft carriers are tremenduously useful when you AREN'T fighting a nation which has a real ability to defend itself. Most of the well-defended countries have nukes anyway.
Aircraft carriers make force-projection possible even when there are no nearby friendly bases.
If you have a screen that works 90% of the time, and you detain 300 people, 270 will be terrorists.
Congratulations, you got it wrong exactly the way that is being complained about.
The test accuracy is measured compared to the population tested. In fact, a test that consistently says "no cancer" in all cases is 99% accurate when run on the general population.
I don't know about other nations, but in Denmark most soldiers take a couple of tours in their military career. This is comparable to the number of trips an astronaut takes.
Soldiers from Western nations deployed to war generally have at most 1-2% risk of death per 6 month tour. At least that's what I have previously estimated from death tolls in Afghanistan and Iraq (although I'll admit that I haven't been very rigorous). The Shuttle is at around 2%.
Fedora version upgrades using preupgrade or simply yum work fine for me. I prefer the yum upgrade, but it has not been officially supported. Luckily it seems that it is getting more attention now that people have realized that it will never be possible to guarantee system upgrades using a fixed ISO once the system you upgrade from has had updates.
My previous laptop went from around Fedora 2 to Fedora 9, this one has gone Fedora 9 to 11. Servers tend to last about 6 Fedora releases before being obsolete.
I'm pretty sure the FLOSS community will continue to develop what is worth, and for free
I highly doubt that, apart from jailbroken iPhones. Windows CE has approximately zero free software after more than 10 years. I use zero free software applications from the App Store. I use a couple of gratis applications, but those are add-supported and the source is neither available nor open.
Nagios is dead slow during large outages. If it loses contact with a few hundred devices (out of a few thousand monitored), it will be 15 minutes at least before it has figured out the scope of the problem, and the same again when the problem is solved. Throwing hardware at the problem doesn't help.
The RNEP program was cancelled before a functional bomb was produced. Funding may of course have continued under another name. Personally I doubt that the US has a functional nuclear bunker buster.
It's hard to tell what the reasons for the cancellation were. They probably include the fact that a vast network of well-defended tunnels didn't exist in either Iraq or Afghanistan, but only in Donald Rumsfeld's deluded mind.
Slashdot Mirror
Well they're the ones who issued Microsoft certificates to a fraudster. And the ones who implemented Site Finder. They also did a bit of securities fraud (options backdating).
Wonderful company.
Verisign is Network Solutions...
None of the console manufacturers have announce *any* information about their next generation or products. So why bother creating straw men for your case?
The argument was that we should let the manufacturers off about the unsafety of this generation, because the next generation might be better. There is no evidence that the next generation will be better, so that argument is fairly bad.
How many companies changed their product, midcycle, to comply before they were legally compelled to?
Some did, but obviously not enough, or RoHS laws would not have been necessary. We can still criticize the companies for gambling with our safety.
*unless there's a heavy marketing angle in it.
That's what Greenpeace is trying to accomplish. I'm sure that Greenpeace wouldn't mind having a law forbidding brominated flame retardants, but in the meantime they have to work with what they have.
Anyway, now is the time to complain anyway, because it's at this time that decisions for the next console are being made. So far none of the manufacturers have announced anything related to improved product safety for their next consoles, so blindly hoping that it will be better is probably naive.
The BROADCAST was for support for obsolete IP stacks. Yes, DHCP servers should still support it, but given that noone used it, some of the newer DHCP servers didn't implement support for it. Hardly surprising.
The fact is that "A client that can receive unicast IP datagrams before its protocol software has been configured SHOULD clear the BROADCAST bit to 0." Vista CAN receive unicast IP datagrams before its protocol software has been configured, it just drops them unless a registry entry is defined.
The RFC's are based on the principle of "be strict in what you send and lenient in what you expect". Vista breaks the first rule and the various router DHCP servers broke the second.
I simply can't think of an innocent reason to have a registry entry which out to be called be_incompatible and having it default to "yes".
So, amazingly enough, the manufacturers didn't dump their hundreds of millions of dollars of investments, six months in to their ten year lives, just because Greenpeace told them to? Why that's just crazy.
Other manufacturers have managed to change their then-current products. E.g. the ROHS program, which forced manufacturers to remove lead (and other things) from their products -- for a while it was fairly hard to get the WRT54GL, but a month later that was all cleared up.
Changing the way you produce a motherboard or replacing brominated flame retardants (nasty stuff, by the way) with something safer doesn't require a product redesign.
Not "exactly the same thing happens with the GPL". See if I spend 5 years developing a program, and for some reason if GPL code happens to slip into it (junior programmer), and it gets released before the problem is found, I now have to release all the source to my entire program.
No you don't. You have to pay the fine and the compensation and stop distributing your program. The GPL isn't an EULA, if you don't like it then you can just ignore it and be subject to usual copyright rules.
Normally, DHCP servers and BOOTP relay agents attempt to deliver DHCPOFFER, DHCPACK and DHCPNAK messages directly to the client using uicast delivery. The IP destination address (in the IP header) is set to the DHCP 'yiaddr' address and the link-layer destination address is set to the DHCP 'chaddr' address. Unfortunately, some client implementations are unable to receive such unicast IP datagrams until the implementation has been configured with a valid IP address (leading to a deadlock in which the client's IP address cannot be delivered until the client has been configured with an IP address).
A client that cannot receive unicast IP datagrams until its protocol software has been configured with an IP address SHOULD set the BROADCAST bit in the 'flags' field to 1 in any DHCPDISCOVER or DHCPREQUEST messages that client sends. The BROADCAST bit will provide a hint to the DHCP server and BOOTP relay agent to broadcast any messages to the client on the client's subnet. A client that can receive unicast IP datagrams before its protocol software has been configured SHOULD clear the BROADCAST bit to 0.
That's from RFC 2131, published March 1997. Guess what? Vista apparently has a deficient IP stack which "cannot receive unicast IP datagrams until its protocol software has been configured with an IP address.". At least it sets the BROADCAST bit. It gets even stupider, because Vista actually HAS a modern IP stack, and CAN receive unicast without having an IP address. You just need to set a registry entry.
Needless to say, not every router vendor supported the BROADCAST bit in their DHCP servers. Well now they do.
No. If you get caught, you would likely be forbidden from distributing it anymore, and you pay Microsoft and Borland compensation for the copies already distributed. Exactly the same happens with the GPL.
Unless you didn't distribute it at all, in which case it all depends on the EULA. The GPL allows you to do whatever you want if you don't distribute the result, by the way.
but I'm not entirely sure that they could just cease distributing the code since it is already "out there" now
That can happen in copyright violations where the GPL isn't involved too, and indeed it's common in many kinds of law suits that the defendant is unable to undo the harm he did. Monetary compensation is often used instead.
Copyright isn't viral. If you integrate your code and someone else's code (to which you do not have a license), there's nothing viral about that. You simply violated copyright and neither party has rights to the combined code.
That is exactly the same with GPL-licensed code. The only difference is that authors of GPL software quite often drop their cases when the defendant decides to free their software. Authors of proprietary software rarely show such courtesy. Either way, it's up to the defendant to negotiate a settlement or to accept their punishment (and to lobby to get copyright law changed, perhaps).
Aircraft carriers are tremenduously useful when you AREN'T fighting a nation which has a real ability to defend itself. Most of the well-defended countries have nukes anyway.
Aircraft carriers make force-projection possible even when there are no nearby friendly bases.
If you have a screen that works 90% of the time, and you detain 300 people, 270 will be terrorists.
Congratulations, you got it wrong exactly the way that is being complained about.
The test accuracy is measured compared to the population tested. In fact, a test that consistently says "no cancer" in all cases is 99% accurate when run on the general population.
This image is going to be scaled to be the exact same size on the screen in any web browser.
Only in your dreams. Lots of people lie to their OS about their monitor DPI, because said OS is deficient.
I don't know about other nations, but in Denmark most soldiers take a couple of tours in their military career. This is comparable to the number of trips an astronaut takes.
Soldiers from Western nations deployed to war generally have at most 1-2% risk of death per 6 month tour. At least that's what I have previously estimated from death tolls in Afghanistan and Iraq (although I'll admit that I haven't been very rigorous). The Shuttle is at around 2%.
How about hybrids? They seem to provide the best of both worlds, and even Mythbusters have managed to build one.
Fedora version upgrades using preupgrade or simply yum work fine for me. I prefer the yum upgrade, but it has not been officially supported. Luckily it seems that it is getting more attention now that people have realized that it will never be possible to guarantee system upgrades using a fixed ISO once the system you upgrade from has had updates.
My previous laptop went from around Fedora 2 to Fedora 9, this one has gone Fedora 9 to 11. Servers tend to last about 6 Fedora releases before being obsolete.
I'm pretty sure the FLOSS community will continue to develop what is worth, and for free
I highly doubt that, apart from jailbroken iPhones. Windows CE has approximately zero free software after more than 10 years. I use zero free software applications from the App Store. I use a couple of gratis applications, but those are add-supported and the source is neither available nor open.
V3.0.4 currently
I didn't say planned, I said considered. Since they (AFAIK) never managed to build the RNEP, it's hard to plan for its use.
Crap, the link failed somehow. Here we go again
Nagios is dead slow during large outages. If it loses contact with a few hundred devices (out of a few thousand monitored), it will be 15 minutes at least before it has figured out the scope of the problem, and the same again when the problem is solved. Throwing hardware at the problem doesn't help.
(1680x1050 is a fscking stupid resolution to put on a 15" screen, but that's another story altogether :)
I wouldn't call it fucking stupid, the alternative is full HD, and that is still quite expensive.
Unless you mean that you'd prefer a lower resolution, but why would anyone like jagged edges?
Bunker buster article at GlobalSecurity.org
The RNEP program was cancelled before a functional bomb was produced. Funding may of course have continued under another name. Personally I doubt that the US has a functional nuclear bunker buster.
It's hard to tell what the reasons for the cancellation were. They probably include the fact that a vast network of well-defended tunnels didn't exist in either Iraq or Afghanistan, but only in Donald Rumsfeld's deluded mind.