If you've never had a boss like this -- a lazy narcissist -- you're lucky. But if you have, the pattern is familiar and unmistakable:

* Doesn't understand the issues.

* Doesn't do his homework.

* Believes he's a genius whose "gut" overrules people who do understand and do do their homework.

* Plays his subordinates off against one another.

* Highly susceptible to information from random sources: thing he saw on TV, or heard on the golf course.

* Not particularly fussed about contradicting himself because he doesn't care about being right, but does care about being in charge.

* The more chaotic he can make things, the more in charge he feels.

* Has a cynical view of the people he works for but has a genuine gift for flattery when it suits his purposes.

Once you've seen this up close it's really obvious when you come across it again. You can't *not* listen to a lazy narcissist boss because he absolutely will try the stupid shit he says he will. But you can't count on him either, because he has no commitment to anything other than how he looks and feels *right now*.

Neither. Commerce didn't drop it, it got taken away and given to DoJ, but not because Commerce couldn't handle the invetigation of where the chips were going. The case goes to DoJ because we're talking about criminal charges of smuggling, corporate fraud, violation of national security statutes. Also because the Commerce investigation was tained by potential political interference. And possibly because it ran afoul of a counterintelligence operations siloed in the DoJ -- although by this point the cat is so out of the bag everyone must assume they've got a FISA wiretap warrant on them.

However, the *effect* may be to slow the progress of the investigation and delay any actions being taken.

The first reason for this is that criminal investigations are slower, the standards of proof higher, and potentially involve a criminal trial. Commerce could simply make an administrative law determination that put Megaspeed on some shit list and come to some kind of agreement with NVIDIA.

The second reason is that putting this into DoJ's hands is putting it into a department that has had staff turnover and loss of institutional knowledge, strife between career personnel and political appointees, and difficulty replacing lost employees. It's also led by lame-duck appointees, facing turnover in the next administration. So if they don't make progress in the next two years, allowing for transition delays, it could be years before anything gets accomplished. By then a lot of people will have left their jobs, memories will get hazy, evidence will go missing, and defensive positions constructed.

So while the investigation hasn't been *killed*; it has been delayed so long that it's effectively in suspended animation. It's not possible for Commerce to sanction anyone because the investigation is out of their hands.

And? The two man pages describe the behavior in the Buster and Trixie releases respectively. Regardless of when they were first written.

Even if it fails to compose the error message, it safely terminates the program with abort(). Which is the behavior you asked for.

https://elixir.bootlin.com/gli...

Money may be an aphrodisiac but come on, Jensen, look in the mirror. There's limits to anything.

If you want that behavior you can make a macro which does an assert() after the malloc. C is about giving you the power even if 99% of the time the error should be considered fatal.

You have the order reversed. It used to say null on error. Now it says * on error if so configured (which by default it is).

You are mistaken. That's a 2019 and a 2025 man page. The 2025 man page allows "*".

Consider these two man pages:

Debian Linux 5 years ago: https://manpages.debian.org/bu...

Debian Linux now: https://manpages.debian.org/tr...

You're looking at an older copy of the crypt man page. Compare the two from current Debian and Debian from 5 years ago. Current Debian returns a string starting with "*" so that older applications fail closed (as explained in the man page).

https://manpages.debian.org/tr...
https://manpages.debian.org/bu...

They're renting the ability to access the Internet via a white house IP address. Has nothing to do with email.

Although if you really want a whitehouse email address I could hook you up on whitehouse.net.

For legacy reasons, Crypt() is not allowed to return a null pointer. Some old applications do not expect a null pointer and will crash. On error, it instead returns a string that starts with *. In GNU C the string starts with * and then has a partial, invalid hash. In Musl C it just has the *. Crypt() never returns * on success.

Check the man page.

No, if you read the man page for crypt, a failed return is supposed to start with the "*" character while a successful run will not contain a * character anywhere. GNU libc returns a * followed by additional characters while musl C only returns the *. OpenSSH failed to check whether the crypt output started with *, signaling an error.

That's an OpenSSH bug.

While this is true, being the subject of an experiment to see what happens when you do that is not something most people would choose for themselves. It's not *irrational* to be concerned. Absence of evidence on a largely unexplored question like microplastic infiltration in human bodies is not the moral equivalent of absence of evidence in an extensively studied question like a vaccine-autism link.

Uncopyrightable just means public domain. Using public domain code doesn't make your whole work public domain.