The trick is to handle the case where you CANT get an IPv4 address. Dual stack normally assumes you can get one IPv4 address along with your block of IPv6 addresses.
The solution is probably carrier-grade NAT for IPv4 (so you only get a private IPv4 address) with dual-stack.
But that has it's own problems.
All modern versions of Windows (desktop or server) fully support IPv6. I have it, I use it, and it works.
Of course, it works for my Linux and Mac boxes too.
You don't understand IPv6 well.. It has an option for pricacy-enhanced "temporary" IPv6 addresses to be used for outbound connections. Windows has this on by default, most linuxes seem to require you to turn it on.
When it is on, a randomly generated short-term IPv6 address is generated when you make an outbound connection. This IP address lives for a short while (until the connection is closed or a few hours, whichever comes later).
Windows uses a new one for each new outbound connection (you can have thousands of IPv6 addresses at the same time.
However, if you are worried about your home internet, it doesn't help much. You need either a traceable IPv4 address, or a traceable IPv6 routing prefix, so packets can get to you. They can't tell which machine on your network generated the traffic, but they do know it was from your network.
Solaris, for a while, was free to use. Now it has become not free. For a while, they (Sun) were trying to make it open-source, now (Oracle) they are reversing that.
I would buy a support contract if I was running real, important, production work. But, If I want to run a low-priority internal server, or a small external web app, I can't see it worth the support contract, so I'll just go with Linux. If not free, I'll go with Windows for many uses (yes, Windows does work in real-life applications).
So, it's a "Full, Supported Release", but we can't use it for anything except as a development platform (and what to deploy on?).
From the license agreement: We can't "use the Programs for your own internal business purposes... or for any commercial or production purposes"
So in reality, it's just a way to show off, an try to keep people from jumping ship to linux.
It's definitely the antithesis of FOSS -- nothing is free about it.
Pressurized light-water reactors like this are not useful for plutonium production.
You need to shut down the reactor to add or remove fuel.
For plutonium production, you need to introduce U-238 for a specific amount of time to maximize Pu-239 without getting much Pu-240.
The spent fuel from a light-water reactor has too much Pu-240 to be used in making bombs. The Pu-240 contamination would cause premature ignition, ending up with a "fizzle" not a real nuclear explosion.
The centrifuges they have for producing fuel for the reactors can be used to make weapons grade U-235... That is the main risk.
The developer should never be the ONLY one testing the code.
But the developer should absolutely test the code before turning it over to QA.
You should be convinced your code works before giving it to someone else to test.
I understand the goal of the FDA. They don't want people bypassing treatments that might work to go for untried treatments or ones that are known to not work. But in the case where there are no remaining approved treatments, I think we should be allowed to do what we want, regadless of risk. I'll be in that position when my current drugs stop working (I'm on the last FDA approved treatment for my cancer).
Sigh... Ok, we know there are some treatments that are safe, and not likely at all to work. There are others that have higher risks, probably don't work, but might have a shot. Then there are total unknowns... Where we don't have any idea if it is safe or effective. Many drugs I could try will be fully evaluated in only 10 to 20 years, but I expect I have only a couple of years. Yes, it isn't good science, but that doesn't make it a bad choice to try things. I don't think there should be laws against someone like me trying these things.
I have terminal stage 4 colon cancer...
None of the treatments available have any likelyhood of stopping the cancer, or even keeping it at bay for more than a couple of years.
But, there are always statistical outlyers, and I hope I'm one of the rare lucky ones that goes for quite a few years.
For example, I have terminal cancer, although for now I feel fine.
The doctors know that none of the FDA approved treatments will stop the cancer, the best they can do is slow it down some.
If I saw a treatment that had a high risk of killing me, but a decent chance it would cure me, I'd go for it, even knowing it might kill me.
Yes, if you have a smart phone, the calculations can be done there. Most people have "dumb" phones.
But it doesn't matter, if the phone is on, in reach of a cell tower, the cell company knows where it is.
I doesnt matter how fast or slow your phone is, most were designed to send the ephemeris data to the cell tower. The cell company knows where you are, as long as the phone is turned on.
The phones don't usually have the CPU power to actually compute the lat/lon. Instead, the send the ephemeris data up to the Cell phone company's servers, which compute the lat/lon, and send it back.
And the carrier has the ability to ask your phone to send the lat/lon information anytime they want it.
At the same time, the carrier has the ability to save that information. Many sell services where you can look up the location of phones you own (AT&T does this, usually sold as a way to track your children).
Uhm... That's exactly what your current monitor/TV does... Uses R, G, and B to give a close approximation of the full color image.
Adding a Yellow channel is like adding an audio channel half way between left and center... Sure, some sound originally came from there, and if you could know, you'd like the reproduction to come from there.
Sure, The display could have 100 different pixel colors, ahd your could estimate which to use, but it is like having an extra speaker between Left and Center... Sure, some sound originally came from there, but can you know? Can you tell the difference?
Not with our eyes.
Slashdot Mirror
Giving people a private IPv4 isn't so bad if they also have a real public IPv6 block.
Sure, it will break all the P2P traffic that relies on IPv4-only, but that will quickly force those services to support IPv6.
And it never will be until we really rely on it, which won't happen until we run out of IPv4 addresses.
The trick is to handle the case where you CANT get an IPv4 address. Dual stack normally assumes you can get one IPv4 address along with your block of IPv6 addresses.
The solution is probably carrier-grade NAT for IPv4 (so you only get a private IPv4 address) with dual-stack. But that has it's own problems.
How can you route packets to the location the cell phone is currently roaming at?
A single IPv6 subnet has room for every network interface ever built, or will be built in the next decade. And that's only ONE /64 subnet.
DD-WRT or OpenWRT firmware supports IPv6, so you can often convert your older router to one that supports IPv6.
All modern versions of Windows (desktop or server) fully support IPv6. I have it, I use it, and it works. Of course, it works for my Linux and Mac boxes too.
You don't understand IPv6 well.. It has an option for pricacy-enhanced "temporary" IPv6 addresses to be used for outbound connections. Windows has this on by default, most linuxes seem to require you to turn it on.
When it is on, a randomly generated short-term IPv6 address is generated when you make an outbound connection. This IP address lives for a short while (until the connection is closed or a few hours, whichever comes later). Windows uses a new one for each new outbound connection (you can have thousands of IPv6 addresses at the same time.
However, if you are worried about your home internet, it doesn't help much. You need either a traceable IPv4 address, or a traceable IPv6 routing prefix, so packets can get to you. They can't tell which machine on your network generated the traffic, but they do know it was from your network.
Adding the class E addresses would add ONE /8, which is a fraction of a year of use. And which RIR gets it? Share it?
6RD and 6to4 require you to have a public IPv4 address. Native dual-stack and/or DSLITE don't require this, but those are still not ready on Comcast.
But I like fried Chicken! That doesn't mean I like Solais :(
Solaris, for a while, was free to use. Now it has become not free. For a while, they (Sun) were trying to make it open-source, now (Oracle) they are reversing that. I would buy a support contract if I was running real, important, production work. But, If I want to run a low-priority internal server, or a small external web app, I can't see it worth the support contract, so I'll just go with Linux. If not free, I'll go with Windows for many uses (yes, Windows does work in real-life applications).
I dont really care about that... I care I can't use it for anything useful. So what is the point, and why should I be happy about this "release"?
So, it's a "Full, Supported Release", but we can't use it for anything except as a development platform (and what to deploy on?). From the license agreement: We can't "use the Programs for your own internal business purposes... or for any commercial or production purposes" So in reality, it's just a way to show off, an try to keep people from jumping ship to linux. It's definitely the antithesis of FOSS -- nothing is free about it.
Converting fuel grade uranium to weopons grade requires centrifuges.... Which Iran has, supposedly only for creating fuel for reactors
Pressurized light-water reactors like this are not useful for plutonium production. You need to shut down the reactor to add or remove fuel. For plutonium production, you need to introduce U-238 for a specific amount of time to maximize Pu-239 without getting much Pu-240. The spent fuel from a light-water reactor has too much Pu-240 to be used in making bombs. The Pu-240 contamination would cause premature ignition, ending up with a "fizzle" not a real nuclear explosion. The centrifuges they have for producing fuel for the reactors can be used to make weapons grade U-235... That is the main risk.
The developer should never be the ONLY one testing the code. But the developer should absolutely test the code before turning it over to QA. You should be convinced your code works before giving it to someone else to test.
I understand the goal of the FDA. They don't want people bypassing treatments that might work to go for untried treatments or ones that are known to not work. But in the case where there are no remaining approved treatments, I think we should be allowed to do what we want, regadless of risk. I'll be in that position when my current drugs stop working (I'm on the last FDA approved treatment for my cancer).
Sigh... Ok, we know there are some treatments that are safe, and not likely at all to work. There are others that have higher risks, probably don't work, but might have a shot. Then there are total unknowns... Where we don't have any idea if it is safe or effective. Many drugs I could try will be fully evaluated in only 10 to 20 years, but I expect I have only a couple of years. Yes, it isn't good science, but that doesn't make it a bad choice to try things. I don't think there should be laws against someone like me trying these things.
I have terminal stage 4 colon cancer... None of the treatments available have any likelyhood of stopping the cancer, or even keeping it at bay for more than a couple of years. But, there are always statistical outlyers, and I hope I'm one of the rare lucky ones that goes for quite a few years.
For example, I have terminal cancer, although for now I feel fine. The doctors know that none of the FDA approved treatments will stop the cancer, the best they can do is slow it down some. If I saw a treatment that had a high risk of killing me, but a decent chance it would cure me, I'd go for it, even knowing it might kill me.
Yes, if you have a smart phone, the calculations can be done there. Most people have "dumb" phones. But it doesn't matter, if the phone is on, in reach of a cell tower, the cell company knows where it is.
I doesnt matter how fast or slow your phone is, most were designed to send the ephemeris data to the cell tower. The cell company knows where you are, as long as the phone is turned on.
The phones don't usually have the CPU power to actually compute the lat/lon. Instead, the send the ephemeris data up to the Cell phone company's servers, which compute the lat/lon, and send it back. And the carrier has the ability to ask your phone to send the lat/lon information anytime they want it. At the same time, the carrier has the ability to save that information. Many sell services where you can look up the location of phones you own (AT&T does this, usually sold as a way to track your children).
Uhm... That's exactly what your current monitor/TV does... Uses R, G, and B to give a close approximation of the full color image. Adding a Yellow channel is like adding an audio channel half way between left and center... Sure, some sound originally came from there, and if you could know, you'd like the reproduction to come from there. Sure, The display could have 100 different pixel colors, ahd your could estimate which to use, but it is like having an extra speaker between Left and Center... Sure, some sound originally came from there, but can you know? Can you tell the difference? Not with our eyes.