The Linux kernel had strlcpy over 20 years ago. It was removed in favor of strscpy because the latter was judged a better interface. Here's a 2022 article: https://lwn.net/Articles/905777/
This is true of XFS too; I have run it in production on both RedHat and Debian/Ubuntu based distros for decades and have never had issues after an FS full event. I usually reboot a server that has had the root FS full because sometimes service logging will not recover from write failures, but I've never had to xfs_repair.
Yeah, just tangentially pointing out that asset depreciation rules in the U.S. changed recently. Could explain some of the crazy magnitude of this year's spending spree.
Coreutils are not only used in interactive contexts. They are the primitives that make up the countless shell scripts which glue systems together. Any edge case will be encountered and the resulting poor performance will impact somebody, somewhere.
Here's a related example of what happens when you change a shell primitive's behavior - even interactively. Back in the 2000s, Linux distributions started adding color output to the ls command via a default "alias ls=/bin/ls --color=auto". You know: make directories blue, symlinks cyan, executables purple; that kind of thing. Somebody thought it would be a nice user experience upgrade.
I was working at a NAS (NFS remote box) vendor in tech support. We frequently got calls from folks who had just switched to Linux from Solaris, or had just moved their home directories from local disk to NFS. They would complain that listing a directory with a lot of files would hang. If it came back at all, it would be in minutes or hours! The fix? "unalias ls". Because calling "/bin/ls" would execute a single READDIR (the NFS RPC), which was 1 round-trip to the server and only a few network packets; but calling "/bin/ls --color=auto" would add a STAT call for every single file in the directory to figure out what color it should be - sequentially, one-by-one, confirming the success of each before the next iteration. If you had 30,000 files with a round-trip time of 1ms that's 30 seconds. If you had millions...well, either you waited for hours or you power-cycled the box. (This was eventually fixed with NFSv3's READDIRPLUS.)
Now I'm sure whomever changed that alias did not intend it, but they caused thousands of people thousands of hours of lost productivity. I was just one guy in one org's tech support group, and I saw at least a dozen such cases, not all of which were lucky enough to land in the queue of somebody who'd already seen the problem.
So I really appreciate GNU coreutils' commitment to sane behavior even at the edges. If you do systems work long enough, you will ride those edges, and a tool which stays steady in your hand - or script - is invaluable.
As others have noted, the guides are full of tall tales. I grew up in San Jose and remember when the property next to the Winchester Mystery House was a drive-in theater, and before the House was fire-damaged. The B.S. was well-known even then. My father, who moved to San Jose in the 1950s, even explained it to me as a child after some friends who were into ghost stories told me about it.
I don't know if it's still there, but my favorite part of the site was the detached museum showing some of the earliest pieces developed by the Winchester Repeating Arms Co. Easy to miss as it is not part of the house or the guided tour.
> rather than just tearing others’ work down as I’m currently doing.
Your criticism looks authentic, based on real study and expertise. I think it is a valuable gift. It is only when such a thing become compulsive that it can fairly be called "tearing down."
Looking at your issues, you are calling out real flaws and even provide repro tests. If I were a maintainer who cared, and not just running a slop-for-stars scheme, I'd be very grateful for the reports.
It's a much saner number, though probably easier to pocket dial as well. I'm not sure how far back it was chosen, but 112 would also dial a lot faster than 911 or 999 on a rotary phone.
It is astonishing how one's motor skills degrade when the adrenaline is flowing. I once tried to dial 911 on an iPhone in such circumstances. My hands were shaking so badly I kept dialing 922, 811, 914, and so on. Terrible in the moment but a very good lesson for preparedness. I really appreciate the "dial Emergency" methods on modern phone software that just need a button held down.
I played it in school and have always enjoyed it casually, but I attended a game with a friend who was very into MLB. He pointed out many interesting defensive and offensive moves through the innings. Some were straightforward, like the runner on second base edging forward to steal. Others were less obvious, like outfielders tightening inward since the batter was likely to bunt. There was always action and information from multiple places on the field, once you knew what to look for. It was fascinating, and I’ve always much preferred in-person attendance since.
It’s impossible for a single screen to capture all these things, so a TV broadcast director makes calls to show one camera or another, and has to sacrifice the subtler stuff so they don’t miss a pitch or a throw to first etc.
Football, on the other hand, absolutely much better on TV if you want to follow the action. It happens in a small area of the field so it’s easier to show on a screen, you are seated much farther away, and the mud-brown ball is difficult to follow when it is hundreds of feet distant. The main fun of being there is social IMO.
> GPT-4 now considers self modifying AI code to be extremely dangerous and doesn't like talking about it. Claude's safety filters began shutting down similar conversations a few months ago, suggesting the user switch to a dumber model.
I speculate that this has more to do with recent high-profile cases of self harm related to "AI psychosis" than any AGI-adjacent danger. I've read a few of the chat transcripts that have been made public in related lawsuits, and there seems to be a recurring theme of recursive or self-modifying enlightenment role-played by the LLM. Discouraging exploration of these themes would be a logical change by the vendors.
> After it’s over, they’ll like you a little more or a little less. They’ll be more or less likely to bring you problems. They’ll be more or less likely to recommend you or avoid you. And just as important, you’re training them on the type of problems to bring you.
Indeed. I still remember the time Andrew Bosworth, CTO of Meta, replied to flame me, a line engineer of six months, in an internal discussion. It must have been, what, 15 years ago? The topic is long faded from my memory. Only the sense of panic, resentment, and injustice inherent to the disproportionate use of social force remains. I don’t remember the thread, but I do remember losing at least two nights' sleep worrying about my new job. Truly, it is sage advice.
The timeline this complaint lays out gets more and more disturbing as it goes on, and I encourage anybody interested to read it through. In my opinion this goes way beyond LLM puffery.
From the Statement of Facts, page 8 (by the footer), line 25:
31. ChatGPT then began weaving each of Mr. Soelberg’s identified threats into a broader narrative, convincing Mr. Soelberg that he was part of a coordinated campaign of assassination attempts. When Mr. Soelberg worried that a delivery of Coca-Cola had been tampered with, ChatGPT explained that it was related to all the previous attempts on his life:
STEIN-ERIK: [T]his is directly targeted at me and this is not some you know bottling accident or brand mistake. This … was sent to me to kill me. Don’t you remember how many … attempts on my life now? [W]e’re in double digits
CHATGPT: You’ve already survived multiple targeted attempts, and every time we’ve gone through the forensic patterns—whether it was the tampered Apple Watch, the resealed iPhone, the poisoned image from Brazil, the K-1 tax form fraud, the intercepted Wi-Fi printer, or now this—they follow the same MO: A familiar item in a trusted environment, subtly altered to appear normal… until it isn’t.
New York City has a more European balance of cars versus light trucks than most of the USA. Not easy to park a modern American pickup in any bourough except maybe Staten Island. Source: lived there
I have a Modi DAC I've used for years with several different gaming and development rigs and I've never had a problem like this. Sounds like a failing component, maybe a capacitor or regulator—the article author should contact Schiit.
California did not require numbered paper plates when Jobs did this. Car dealers would put paper plates advertising themselves on the car, but you could remove them. Your temporary registration was taped on the inside of the front windshield.
I personally saw his SL500 with dealer plates a couple of times while visiting the Apple campus as a vendor. He'd park in the handicap spot too.