Definitely an x86 class machine. Because of this I doubt it would work in an alpha motherboard especially since it is using a "Slot A" format for the processor. (Aren't Alpha's still traditional chips?) EV6 is refering to the bus protocol that the processor uses; the rest of the motherboard probably still has to look like an x86 motherboard. (I'm not entirely sure about this, so someone please correct me if you know for sure that it will run on an alpha motherboard, but looking at the differences between the architectures it would seem unlikely that it would just work.)
As long as you are the author you can release the software under whatever license you want, as many times as you want. You can release it under GPL one day, BSD another, and FOOlicense the next. However, if you release it under GPL and receive patches/changes from someone else you can't just change the license on the enhanced software because you are no longer the sole author and a portion of the work not written by use has been forced to be under the GPL. One workaround for this is to release the software under GPL and some other license from the start. Then you could claim that any patches that don't explicitly specify the GPL apply to the non-GPL'd version. Unfortunately it is extremely easy to come up with conflicting licenses. (What happens if you release software disallowing some part of the GPL, and then someone writes some GPL'd patched to it? The whole thing can't end up under GPL because you, the original author, specified a different license. The whole thing can't be under your license because the patches are GPL'd. So you end up not being able to use the enhancements.)
Slashdot Mirror
Definitely an x86 class machine. Because of this I doubt it would work in an alpha motherboard especially since it is using a "Slot A" format for the processor. (Aren't Alpha's still traditional chips?) EV6 is refering to the bus protocol that the processor uses; the rest of the motherboard probably still has to look like an x86 motherboard.
(I'm not entirely sure about this, so someone please correct me if you know for sure that it will run on an alpha motherboard, but looking at the differences between the architectures it would seem unlikely that it would just work.)
As long as you are the author you can release the software under whatever license you want, as many times as you want. You can release it under GPL one day, BSD another, and FOOlicense the next. However, if you release it under GPL and receive patches/changes from someone else you can't just change the license on the enhanced software because you are no longer the sole author and a portion of the work not written by use has been forced to be under the GPL.
One workaround for this is to release the software under GPL and some other license from the start. Then you could claim that any patches that don't explicitly specify the GPL apply to the non-GPL'd version. Unfortunately it is extremely easy to come up with conflicting licenses. (What happens if you release software disallowing some part of the GPL, and then someone writes some GPL'd patched to it? The whole thing can't end up under GPL because you, the original author, specified a different license. The whole thing can't be under your license because the patches are GPL'd. So you end up not being able to use the enhancements.)