Windows has its own library built-in: NLS. There have been a lot of back-and-forth about whether to use NLS or ICU in dotnet on Windows because it resulted in different behavior between Windows and other platforms. I think they ended up using ICU by default from .NET 5 on.
But wasn't the whole (claimed) reason that it got banned in the first place that it is a logical impossibility? Reviewing code for bugs is legitimate. Writing regression tests for bugs is legitimate. If the bug happens to be a security issue then the regression test may be a PoC or at least a step towards one.
Of course the 2.5 line was the unstable pre-release for the 2.6 kernel. That means that stable mainline linux has had nommu since 2.6.0, which was released 17 December 2003.
> A statement that the information in the notification is accurate, and under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
It is only the part about being authorized that is under the penalty of the perjury. You can be as malicious as you want as long as you don't falsely claim to own or represent someone who owns the rights to something.
I really wish they would have asked the representative to confirm that they can only share detailed information with the skeletal remains of an author who died 78 years ago. Not that I think it would make any difference, but it would force the representative to acknowledge the absurdity of the situation.
I have been trying to work on debugging tools using Opus 4.8. As it turns out working with low-level techniques that inspects and alters behavior of other processes is bordering close enough to cybersecurity research that it often hits the guardrails.
It's not difficult not to lie to your customers. If you are actually selling a subscription then don't claim the customer is buying the game, and this law won't apply to you.
NTSYNC seems quite cumbersome to use for your own linux software though
> The ntsync driver creates a single char device /dev/ntsync. Each file description opened on the device represents a unique instance intended to back an individual NT virtual machine. Objects created by one ntsync instance may only be used with other objects created by the same instance.
So you need a server process that can open the char device and hold onto the fd that you can then request through a Unix domain socket.
They are GINA gaskets[0], they were supposed to last 120 years[1], but it has recently been shown that they may deteriorate faster than previously expected due to being under constant compression[2][3]
And if you switch the tty from "cooked" to "raw" mode then it doesn't do the conversion, and a CR just moves the cursor back to the start of the line and a LF just moves the cursor one line down.
You can tell people what something is, that is nominative use of the trademark. Actually putting it in center of the branding might be infringing, but Don Ho gave their blessing to use that, so that point is moot anyways.
They haven't pierced the corporate veil as far as I can tell - it's not moot or any other executives that have been personally fined. Also as far as I'm aware the UK doesn't have debtors jail.
Hmm the comment was a bit difficult to parse, but I think they got it correct. Remember that we have arbitrarily defined the time during local winter as the "standard" time. If we want to keep to that then "permanent daylight savings" is a contradictory term. So what is actually meant is abolishing DST while at the same time changing the standard time to be at the offset of DST before the change. So what I think they are saying is that DST is being abolished, but the actual effective offset at the time when it's abolished is unchanged.
You might need several more dimensions (assuming this quoted claim is correct - it does come with a Citation Needed)
> Recent genetic analysis shows the papedas to be distributed among distinct branches of the Citrus phylogenetic tree, and hence Swingle's proposed subgenus is polyphyletic and not a valid taxonomic grouping, but the term persists as a common name.