8,997 karma · joined September 29, 2014
* https://news.ycombinator.com/item?id=49763972
They've reportedly already tried, and failed, to replace it with a more modern system.
Far more concerning from a RISKS point of view is the spare parts being physically in the same place as the live machine.
But we're talking about a system that is also older than most people.
It was first put into operation in 1967 in the U.S.A., and brought over to the U.K. in 1974. It's formally called 'NAS En Route Stage A', and is written in a 1950s language named JOVIAL. It originally ran on an IBM 9020. It runs on IBM 9020 compatible systems today.
For some reason, a couple of years ago someone added a lengthy unverifiable description of it to Wikipedia's IBM 9020 article, even though that very description said that NAS hadn't run on a 9020 for 34 years at the time of writing, but had been running on a 4381.
Except for: There is no bug that originates in a GNU version of an old networking program and magically makes its way into the NetBSD, FreeBSD, DragonFlyBSD, and OpenBSD (Yes; I checked.) versions of that program.
History simply didn't happen that way.
This bug goes as far back at least as far as the Jolitz-released 386BSD source for libexec/telnetd , where it can be found and which is credited in the GNU versions of the file. GNU just took the 386BSD code. But BSD had a telnetd before 386BSD. In BSD, telnetd itself goes back to 1983. Although its code to do line mode did not pre-date RFC 1116, which was published in August 1989.
The code to do line mode was written the month after that RFC, by Paul Borman, and the bug is in the very first version of that code:
* https://github.com/dspinellis/unix-history-repo/blob/dc8d504...
This bug is not 32 years old.
* https://groups.google.com/g/comp.lang.asm.x86/c/ErG5TJEDjiw/...
* https://github.com/netwide-assembler/nasm/blob/nasm-0.98.x/C...
* https://jdebp.uk/Softwares/dd-with-getopt.html
It only took 52 years. My prediction stands, by the way. (-:
The apparently related bug in the origin project is https://github.com/uutils/coreutils/issues/2949, filed back in 2022 and which sat unmoved for several years until, probably not coincidentally, almost the same time yesterday that this appeared on Hacker News.
And it's not because of the antics of Donald J. Trump. It's been a shit-show for 50 years: a tale of long-term multiple-phase projects losing funding and changing direction mid-phase, of technical debt never dealt with, of the consequences of data entry methodologies, and of cultural erasure because of magtapes encoded in EBCDIC.
(Yes, EBCDIC. There wasn't a systematic deliberate plan to eliminate diacritics from the U.S.A. in the 1970s, as one might guess from observation. There was EBCDIC. In fact, there was initially a plan to put the accents back on, with extra data fields to record the correct names from state-level sources, after moving away from EBCDIC. During the Reagan Era. You can see today how that turned out.)
One bizarre thing, almost as bizarre as the re-spelling of an entire country by EBCDIC, is that the name change from South Park to South America is tame in comparison to the sort of shenanighans that went on in the GNIS. Ghost towns that never existed got named after rural post offices in wide open unpopulated country, railway stations, steam train water stops, local stations serving farms, company executives, loads of springs in California, and in extreme cases things like a fish pond, survey marker trees, and a cage for a monkey. Or a lone building at a crossroads got the name of something else because a map font was difficult to distinguish, or a name printed by something else just happened to run over it.
And then some people handy with computer automation enshrined this rubbish, by mass-importing it into Wikipedia. Wikipedia is still cleaning this up by hand almost two decades later. Oh the wonders that we have collectively done with computers! (-:
The creators of South Park have a long way to go before they are anywhere near as mad as actual history is.
* https://wiki.openstreetmap.org/wiki/USGS_GNIS
* https://en.wikipedia.org/wiki/Wikipedia:Reliability_of_GNIS_...
* https://en.wikipedia.org/wiki/Geographic_Names_Information_S...
And then right at the bottom it went and mentioned Dymaxion.
Dymaxion is one of the few projections that actually shows Antarctica with something resembling its actual shape. Interestingly, to counter the people who say that the best thing to learn from is an actual globe, a couple of children's globes of the world that I had as a child had large metal caps around the axle that obscured most of Antarctica.
Any decent atlas uses a variety of projections, of course. The tatty, second-hand, older-than-I-am atlas that I had at school was already on to Interrupted Mollweide's Homolographic by page 3. (-:
1. WordPerfect‽
I last personally encountered WordPerfect in the early 1990s, when a marketing bod assured me that WordPerfect users never wanted to see the desktops of their graphical operating systems, so there was no reason to integrate with them. For me, it was not unexpected that I never heard of it again, except in nostalgic discussions of the 1980s. Until today.
It turns out that the boycotting U.S.A. movement missed the spot when it was both Canadian-owned and Canadian-made by some years. I myself am just amazed that it still exists, and equally amazed to find under the #WordPerfect hash-tag on the FediVerse someone posting a picture of a shop selling WordPerfect off the shelf, in boxes, in 2026. (https://pixelfed.social/p/rl_dane/972538257736811779)
1. Social media
It's interesting that https://Mstdn.CA , owned by Canadians, moderated by Canadians, hosted in Canada, does not get a mention. GuardTheLeaf promotes Hey.Cafe as well, but it is not a federated site.
1. Maps
Today's news about Apple Maps (9 Hacker News submissions already) has already hit this list, it appears; with several things listed as alternatives to Apple Maps. So it's up to date at the time of launch. The question is whether the list as a whole will be kept up to date, or be added to, as events unfold. And as noted, there are prominent omissions.
I follow the FediVerse robot that announces MirBSD CVS updates, which is quite active. The last major change, apart from some doco, was a fix to rdate at the end of May 2026, just 2 months ago. And even if MirOS BSD were unchanged for longer than that, it would very much still be around.
For starters, on the old BSDs there was no Almquist shell, unless you went to Usenet, grabbed the shar, and built it. The TENEX C shell was the hot new thing, as were BIND and Sendmail. And we got genuine Joy+Horton vi.
Whereas modern NetBSD does not have Sendmail any more, has nvi2, and supports access control lists. And of course under the covers has lots of things that the old BSDs didn't have, like UFS for TiB disc volumes and kqueue.
I've heard tell that they're even thinking of finally doing away with BIND in base.
* https://news.ycombinator.com/item?id=48778757 (https://crocidb.com/post/freebsd-ate-my-ram/)
* https://freshports.org/sysutils/btop/
The fix is still pending being even made to the origin version.
* https://cgit.freebsd.org/src/tree/contrib/tnftp/ChangeLog#n1...
* https://cvsweb.netbsd.org/bsdweb.cgi/src/usr.bin/ftp/main.c?...
* https://cvsweb.openbsd.org/log/src/usr.bin/ftp/main.c,v?sort...