Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:Not quite (Score 1) 208

While not an OEM per say, I have done this with a Windows 7 System Builder version. Install Win7 System Builder, Upgrade to Win10, reinstall Win7. I did not do the rollback: an actual fresh Windows 7 installation which then requires activation. The activation of Windows 7 upon reinstall worked just fine. Granted, System Builder != OEM, but still...

Now, whether I could -for example- replace the HDD in that machine and try to install Windows 10, that I don't know. The hash is indeed for the machine you upgraded with all hardware it had at that point. However, for many machines upgrading is not somethiing that will happen (think laptops). I had planned to try such a situation (upgrade with 4GB RAM, nuke, install 8GB RAM and then install a fresh 10 and see whether it activates), but I have only limited time.

Besides, they're so desperate to see 10 adoption, they'll look a lot though the fingers.

Comment Re:ZFS is nice... (Score 1) 262

Uh, that doesn't work. The problem is that doing exactly what you've written down is contriving to avoid your copyright responsibility by deliberately creating a structure in someone else's work which you believe would be a copyright insulator. If you went ahead and did this (I'm not saying that you personally would be the one at Ubuntu to do so), I'd love to be there when you are deposed. Part of my business is to feed attorneys questions when they cross-examine you. I have in a similar situation made a programmer look really bad, and the parties settled as soon as they saw the deposition and my expert report. See also my comment regarding how Oracle v. Google has changed this issue. You can't count on an API to be a copyright insulator in any context any longer.

Comment Re:ZFS is nice... (Score 1) 262

I think you need to look at this in the context of the appeal of Oracle v. Google. We had a concept of an API being a boundary of copyright based on 17 CFR 102(b) and elucidated by Judge Walker's finding in CAI v. Altai. That stood for a long time. But Oracle v. Google essentially overturned it and we're still waiting to see what the lower court does in response.

Comment Re:Not quite (Score 1) 208

To be more precise, from what I understand. You upgrade your license (the OEM SLP one or the one on your sticker, which are technically two different licenses. Draw your own conclusion from that and how you can abuse this). During the upgrade process, you get a new product key. This product key, from what I've seen, is the same for every machine that is upgraded. That Win10 product key, for Home, ends with 8HVX7, for Pro, ends with 3V66T. Google that if you want.

What really happens is that a hardware hash is sent to Microsoft during the upgrade process. This hardware hash allows you to use those generic keys in the future (well, depending whether you had Home or Pro... Obviously), which means you can just use the generic ISO Microsoft provides (Finally, an official re-installation ISO! I've been waiting years for that). You can not use those generic keys on non-hashed hardware (Yes, I tried to see what happens). It will not activate.

However, your 7 license will remain fully functional. At least, that's my experience.

What would be an interesting test would be the following: Install Windows 7 in a VM, clone it, but don't run the second instance. Start the first instance, upgrade to 10. Keep it on 10. Now launch the second instance, which is 7 and never upgrade it. See if both remain active. This definitely violates the Microsoft licenses you have, but it would be interesting to see what happens. My prediction: both stay activated, but I'm not sure. I haven't tested it.

Comment Re:Not quite (Score 1) 208

For all Windows machines I have under my control, I upgraded to secure the upgrade that I'll have to do in 2020 anyway. Then in clicked "go back to Windows 7" (well, actually, I didn't... It's easier to image the disk, do the upgrade, and restore from image).
I did this for all machines I have with an OEM license. For some machines, that run Linux, I even bothered to image Linux, install the OEM that came with it, upgrade, put back the Linux image. Why? Because, those machines might still be functional in 2020. It might not be me who will use it, and the future user might prefer 10, so I like to give the future user that option.

That is quite a lot of work, well mostly quite a lot of time, but that way I have the license, and I can continue to use whatever I like (7 or Linux), while keeping my options in the future open.

Comment CDDL and GPL don't mix (Score 3, Informative) 262

Regardless of what Ubuntu has convinced themselves of, in this context the ZFS filesystem driver would be an unlicensed derivative work. If they don't want it to be so, it needs to be in user-mode instead of loaded into the kernel address space and using unexported APIs of the kernel.

A lot of people try to deceive themselves (and you) that they can do silly things, like putting an API between software under two licenses, and that such an API becomes a "computer condom" that protects you from the GPL. This rationale was never true and was overturned by the court in the appeal of Oracle v. Google.

Work expands to fill the time available. -- Cyril Northcote Parkinson, "The Economist", 1955