Detect might be hard, but enforcing isn't neccesarily so. You file a civil lawsuit and then it's up to courts to enforce the contract (as this would be viewd in EU or copyright infringement (in the US).
Some countries have laws around Net Neutrality or Open Internet that can protect you from this, but even those countries have other legislations that can superseed that in specific cases. (e.g. hijacking DNS can be completely legal for some child protection laws, or to uphold laws that makes some web sites illegal)
Note that there are ISPs that actively hijack traffic to UDP port 53 further inside their network and transparently maps that onto their internal DNS servers.
Updated and rebooted an LTS server today. It was a disaster.
Kubernetes node went to pieces.
Apparmor prevented nginx from doing anything sensible, so the ingress didn't work. Easy fix when you know what's up, not so apparent when starting troubleshooting.
One app invoked tshark in a pod, apparmor denied it.
Those two were the visible ones. Apparmor now also blocks some unix signals that e.g. postgres uses in a few circumstances - leaving latent annoying bugs.
Pod shutdown hangs. Logs indicate 7 more apps affected by the signal "armor".
It is non-deterministic mainly due to compilers that generate different code or when there are concurrent computations that are executed in an unpredictable order.
A single sequence of floating-point operations executed on an IEEE 754 compliant CPU has always been perfectly deterministic since the first version of the standard.
Who wants a deterministic computation must use a single-threaded program or a multi-threaded program where the order of execution is deterministic, and one must be careful so that changes in compiler versions or compilation options will not affect the type and order of the operations that are executed.
Ofcourse they can. But which particular person will do it ?
The "upstream" people deal with their own drivers, subsystems or tasks which takes up their time - but if someone feels they want to take on this too, they'll do it (normally that doesn't happen - it's up to the original authors to take responsibility)
users , especially non-technical, find it highly useful in my experience. Is it a net positive to get rid of them, or will it largely only make developers happier ?
At the very least, drive letters do make SMB shares a bit simpler for the non technical folks. T:\MyData is easier for them than \\0010-somehost-win.site1.mycorp.loca\Share01\MyData\
I used to support a group of completely tech illiterate users in construction & manufacturing. Them figuring out T:\ was hard enough, ask them to type in a UNC path into the address bar in explorer and you get "Wtf is file explorer? Wtf is an address bar? Where is the backslash key??"
reply