They were real alright, just not real new.

Recycling is green behavior, not greedy behavior. They sure had only the best intentions.

About in the same ballpark as Linux on the desktop?

Android is also Open Source. Perhaps SurfaceFlinger will be what winds up winning instead of Wayland ;)

The shame is not especially, the public shame of it forcing him to change careers is. If the goal is to punish him, and he's already been punished, then there's no reason why that should not be a mitigating circumstance as the goal has already been at least partially achieved.

You can physically disable communications, if there is later a problem with one of those modules or a related system they might try to deny you warranty protection. They might also try to charge you for any software updates which you have to go to the dealer for because you disabled the equipment used for OTA. If you do it in software, you will probably have to defeat a protection mechanism, and then they could conceivably go after you for that, but probably won't as there's no damages to show so there's no point, unless you publish info on how to do it.

You don't know what "cool" means and you don't know what "Ad Hominem" means? What a fucking waste of time talking to you is.

The finding both in the US and the EU was that they couldn't have done it without them, and that they provided aid when they knew what they were doing with it. So, no.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Foag.ca.gov%2Fnews%2Fpress-...
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.reuters.com%2Farticl...

I remember when IBM, SGI, Infornix, Oracle, and HP first got involved in Linux. At the time, I included patches from some of them in the Functionally Overloaded Linux Kernel.

I proposed, back then, a simple league table for commercial support of Linux: Every new major feature or software product got so many points, and every bugfix release got a smaller number of points. Kernel features that made it into the mainstream kernel would qualify as goals for, kernel features and products discontinued were goals against. Closed-source contributions got half points, and were also considered goals against.

It would then be obvious which companies were serious and which were piggybacking, and it would also be clear who understood the philosophy, not just the opportunity.

Such a table would have ensured that nobody forgot the companies who contributed. Quite the opposite. There'd be an incentive to encourage the team you supported to improve position in the table.

Of course, no such league table ever happened. I could have maintained such a table without difficulty, but it would require the vendors to openly say what they'd contributed. I couldn't invent one out of thin air.

So I'd say Oracle has to look at themselves, not just the Linux community.

It's possible to conjecture - we know it collided with something massive, so if said body contained very limited radioactive materials, one might expect this to reduce the radioactivity per unit mass.

Is this the answer? Probably not, but it's good enough (I think) to argue that a simple answer is possible.

I'll amend that to say the typical IT managed OS is too easy to compromise. If an incompetent IT insists on management and observability of an endpoint, they frequently screw up whatever security the platform might actually have, because it somehow inconvenienced them and it's easier to turn the safeguards off.

If true SSO, that wouldn't be so bad, you don't have to enter login credentials. That's almost a unicorn in my experience, like 3 or 4 sites 'get it' and the rest ask for your password.

If it's just same user/password, that's actually a bit worse, since phishing is likely to be successful then.

But yeah, when normal operating procedures resemble phishing often, then it's hard to blame the users.

Yeah, my work has those too. I report as phishing and they say "no, that ones real, you need to follow the directions". Nope, I'm not going to disable smartscreen on a Windows system so I can run http://123.45.6.7/khcsueoac/se... as admin to correct some failure in your remote automation. I won't follow through until you properly provide a solution.

Ultimately, against company policy I broke all the IT management of my systems and self manage, because they are morons and I'm quite positive one day they will tank all of our systems with their incompetence, either making systems unavailable or letting attackers just have the keys to the kingdom.

The failure is with IT who forwards fishing mail and then blames the users.

I used Cygwin on Perl on Windows for 12 years, working at Philips, to automate builds and releases. The same code also ran for a time on Linux virtual machines. Perl has the best interface abstractions of any language, masking e.g., the ugly Windows process interface (possibly also through Cygwin :-)) with a proper POSIX process interface. And Perl is almost like (Common) Lisp, the only thing really missing is the CL macro facility.