A minimalist linux kernel inlcuding only what your application needs has long been a strategy to reduce attacks on a public facing system.

It's more about not running the malware that would utilize such dark web tools.

1) And that differs from US companies how?
2) I "trust" Xi Jin Pooh more than Uncle Sam simply because China has no legal authority over me.
3) You go right ahead and do without; we couldn't care less about your holy war, we just want sub-$10k BYDs.

The GP merely rephrased the old idea that fines are nothing more than a cost of doing business. When the only "punishment" is financial and knowable in advance, that's neither punishment nor deterrence; it's simply an above-the-line calculation.

How many of us have intentionally chosen to risk a speeding and/or parking ticket to make it on time to an important appointment? Same idea, just at a much larger scale: Ford famously chose to literally let Pinto owners DIAF rather than pay an extra $11 to make key parts of the fuel system safer in a rear collision. Despite that, Ford is somehow still in business and not a single executive from that era was sent to prison over knowingly choosing to kill people as a cost cutting measure.

I see the attraction of utc, but doesn't that completely mess with things that reference system time to adjust incoming time-related things?

Eg a meeting request from another system in a different time zone, where it says "the meeting is at 5pm for my sender, but you receiver are x hours different, so I adjust your announced meeting time by the"?

Yes, that was your mistake.

I am not referring to these. Although I've written software for such systems that programmatically updates the timer/clock hardware with fixed DST updates and is not updatable. In other words my software disables the functionality and resets the time twice a year itself. Taking on DST responsibility itself for various regions that differ from national policy.

Except that we are talking about solutions for people tired of having to do manual updates.

And like I said, need to be replaced.

Except that we are talking about solutions for people tired of having to do manual updates. Changing from one variant to another variant doesn't solve any problem.

The actual timer/clock hardware typically does not. All there is is an on/off. And as pointed out, these tend not to be user configurable.

AH, I get it. As long as you consume the proper flavor of slop, then bootlicking is approved.

Thanks for explaining!

Can't we define the timezone as a UTC offset? I thought WIndows, macOS and Linux all allowed that?

Being in the Bogota timezone is not the same as being in Bogota. Parts of Canada and Bogota are in the same UTC offset, UTC-5. Its not like the locale is saying Bogota.

A friend works in an environment like that. There is a serial diagnostic port where status information is regularly dumped for logging purposes. They install a unidirectional serial adapter, TX lines but no RX lines.

You are assuming buyers are not demanding default passwords because they erroneously consider them to be a type of backup. Sometimes you are just not allowed to do the right thing.

In practice, audit trails are 99% about reporting and monitoring needs, not liability after-the-fact. By the time the insurance companies are involved, you're already tossing thousands of dollars of food and possibly have sick people lining up to sue

If there was any sort of centralized monitoring involved here, they would have caught the problem as soon as the temperatures rose above $AlarmHigh or remained above $AlarmLow for more than X minutes. They did not. The exploited interface was therefore a function of convenience, not compliance.

Not really. Internally, Lumentum valuation was probably expected to suffer the same as or more than Marvell valuation.