I'm thinking of the days before MAD. By the start of the Korean war, the Soviets had tested one device only. Some might have entered service by the time of the war, but the Americans still had the upper hand with nuclear weapons at that time.

There was arguments to use them, and Truman did go so far as to release them to the theater, but he never dropped them. Nor did Ike when he won the election. There seemed to be a reluctance to use them even before the whole arms race and MAD became what it did.

Now generals and admirals would probably have tossed the things around like fire-crackers, and they definitely had plans for first-strike use, but the civilian bosses are the ones who were reluctant when it came to their use.

I add the following for your consideration.

After dropping those two bombs, nobody on Earth has ever dropped one since. Think about that for a second. Yes, they have been tested, but never once dropped in anger since the first two. And all nuclear-capable countries between the 50s and the 80s have had was at some point to consider using them. All of them treated them as retaliation weapons, only to be used if they were shot at first.

So let us treat Hiroshima and Nagasaki as the ignorant first use of an unknown technology that it was and accept that the world went through a massive, rapid learning curve and HAVE NOT USED THEM SINCE.

I suspect that would be the case. One good war where you lose because your computer controlled weapons system got zero-dayed and the enemy was launching your own missiles at you via TeamViewer while your mouse refused to respond and I suspect your replacement ships would require you to manually program the coordinates and launch the missile by pulling a piece of string from behind a blast screen.

Acts 10 9-16 repeals the unclean animal laws that the Mosaic Law brought in to keep nasty diseases out of the population. Both the prohibition and the repealing are couched in "Orders from God" terms, but are actually based on prevailing understanding of health and hygiene at the time of each event. And which got unfortunately ritualized.

In a primitive civilization, pork and other meats can be severe risks if they don't know how to cook it properly. A lot of early civilizations had pork prohibitions, but as soon as they realized that a long, hot cooking process rendered the meat harmless, they were dropped. Long before the early Roman Empire times, it was common knowledge and only those adhering to the old Mosaic laws kept up the prohibition as tradition.

The repealing was done as a direct instruction from God because that was probably the only way to get the traditionalists to accept the change and was likely initiated as the early Jewish Christians interacted more with the Romans and Greeks and the knowledge that pork and related "unclean" meats were now safe to eat. And that the gentiles who were becoming more and more of the Christian base weren't going to accept archaic traditions.

Well, they are being fined $11 mil for this missing of the deadline.

An opinion on the law being violated was given in footnote 5 on page 12 of the judgement. It suggests he is not guilty of the charge.

If he is retried, he can bring into evidence footnote 5 on page 12 of the judgement where the judges advanced the opinion that he was innocent of the accessing without authorization or in excess of authorization charge because there was no password or code barrier and the program accessed a publicly facing interface and retrieved information that AT&T unintentionally published. It reads that even if they found the venue as correct, they would have vacated the guilty verdict because of that.

The fix needed is in the systemd code, not the kernel. He can fix it, in less than a minute of editing probably two constants. (from "debug" and "quiet" to "systemd.debug" and "systemd.quiet")

The problem is systemd is a johnny-come-lately and is violating the standard way of doing things, even if the standard way isn't the most optimal. Think of it like a court of law, no court is going to accept a junior lawyer changing terminology that has been in use for centuries just because the lawyer has read a thesaurus. The impact is just too large.

To take it further, apparently all but two parameters (debug and quiet) that systemd recognizes are prefixed by systemd.xxxxxx, so they know how to work within the kernel standard.

The kernel has for a long time had a protocol of parameter naming. Direct kernel parameters are plain, module-specific parameters have mod.xxxx format and that was designed to pass driver-specific parameters in. SystemD, being a child process and not even part of the kernel should respect the existing protocol and ignore any parameters not passed without a leading systemd.

The balaclava isn't for you to wear to hide yourself, it's to pull over the head of the glasshole to cover the camera up. And get them in trouble with the fuzz.

Disable the DNS Client service in Services MMC stops this as well. You'll have a few more DNS queries, but who cares.

Begone and good riddence to your vandalizing of channels.

The problem with producing a car that can only do the highway speed limit, is that it can then still exceed the town limits which is where you have the greater risk of hitting people and other cars.

Imagine an area on the plane where the screaming kids will sit, able to hear what's going on, but not being heard. Or to separate first class from cattle class even better than it already is. Not the most necessary of solutions, but might gain them some extra pax.

They are documented in the regulations linked by the GP and there are clearly documented compliance and appeals processes in there as well. It's a hell of a read though.