Roger Blake wrote:
On 2018-12-28, Anonymous wrote:
It's systemd. VOMIT!!! DRY HEAVES!!!

Although I dislike systemd, I'll take it over Microsoft's activation hell,
which I am currently embroiled in on a friend's computer that needed to
be reloaded. MS's promise that the Windows 10 "digital license" would be
honored if the OS needed to be reinstalled turns out to be just another
Big Lie.


Help is available with activation issues.

If the user logs in normally with an MSA
to the machine, the phone help can use the MSA
to zero in on the machine needing help.

The server problem that lasted for a couple days
has been fixed, and unless you did something rash,
they've been backfilling the mess they made. What
happened there, is already-activated copies started
throwing up notification dialogs at startup. When
that happens... don't panic. That's what happens
when you insist on a "mainframe architecture" in
the form of activation (single point of failure).

Paul