Forgot your password?
typodupeerror

Comment Re:Does this mean Sam Altman's going to prison? (Score 1) 11

But sending this guy to jail as a scammer? Laughable. He gave people what they paid for.

The fraud charge sounds like it was defrauding the university rather than his clients. The CPS press release which all of the media reports seem to be based on doesn't break down the sentencing among the three charges of fraud by false representation, accessing a computer system without authorisation, and money laundering. The case doesn't appear to be available (yet?) at caselaw.nationalarchives.gov.uk.

Comment Re:Does this mean Sam Altman's going to prison? (Score 1) 11

Was this written by AI? What tripe. Heart surgeons? Structural engineers? You sound like a cliche machine. Please, find me an example of this fantasy. Spend the tokens, bitch. Academic honesty is a largely an individual decision. If you catch students, fail them. Strip their degrees in more extreme cases. But sending this guy to jail as a scammer? Laughable. He gave people what they paid for. And you totally misunderstand the post. This guy is nothing compared to what happens daily on ChatGPT and the like. I support locking up Altman. Do you?

Comment Re:Give my my SysVInit (Score 1) 53

There's nothing in Linux that demands you use SystemD. You can choose to use SysVInit if you really want to. Indeed the only kernel requirement is something called "init" is either in /, /bin, or /usr/bin

But the init scripts are really just faking what init was doing - watching processes and restarting them as necessary. The SysVInit scripts are a crude re-implementation of inittab.

Comment Re:C (and here are somemore chars to satisfy the b (Score 1) 35

The major issue of strlcpy() is, it needs to check the source string length, then decide whether to do the string copy or not. So in effect the computer needs to parse the source string twice unnecessarily, and introduces a timing gap, making the function not thread safe.

strscpy() is thread safe because it always tries to copy the source string regardless it will truncate or not. Thus a change of content of source string in the middle of strscpy() operation is not going to cause any undefined behaviour. The implementation can be thread safe.

What is being described is GIGO not thread safety.

Comment Re:C (and here are somemore chars to satisfy the b (Score 1) 35

strncpy() is one of those functions that looks like it was designed as a footgun from day one. The totally stupid semantics are because it was meant for copying strings into fixed-length records inside structs, things like user names and directory entries. It was never meant to be used for about 99.9% of the ways it's actually been used since then, and the C standards committee decided to perpetuate the footgun rather than replacing or supplementing it with a safe string copy. There were safe replacements introduced twenty years ago in TR 24731 but they saw virtually no adoption because it would sap and impurify C's precious bodily fluids to actually do anything to make it safer to use.

Slashdot Top Deals

The perversity of nature is nowhere better demonstrated by the fact that, when exposed to the same atmosphere, bread becomes hard while crackers become soft.

Working...