MAmarkusQi·Oct 29, 2026
The source code and README are here: https://github.com/NetBSD/src/tree/trunk/usr.bin/atto
You are welcome!
In NetBSD adds a new text editor called attoNetBSD
src
C2017–2026
NetBSD / src
src
Automatic conversion of the NetBSD src CVS module, use with care. Please submit bugs/changes via https://gnats.NetBSD.org. NOTE: Links to commits here WILL ROT. Use https://nxr.NetBSD.org or https://cvsweb.NetBSD.org links instead.
21Distinct people
23Mentions
0Explicit recommenders
1KGitHub stars
What to know before exploring
What it is
Automatic conversion of the NetBSD src CVS module, use with care. Please submit bugs/changes via https://gnats.NetBSD.org. NOTE: Links to commits here WILL ROT. Use https://nxr.NetBSD.org or https://cvsweb.NetBSD.org links instead.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- openbsd/src · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year23 dated mentions
Observed mentions: 2017-09-13 05:48:40 UTC to 2026-10-29 13:25:10 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 5 | 0 | 5 |
What Hacker News says
23 sourcesI think he has actually posted videos of the restoration before (they've popped up in my youtube feed in the past), but I've never watched them, so dunno. The LLM site design and advertisement front-and-center are certainly a... choice....
But, more importantly, why do you reckon DEQNA would be hard to connect to a modern network? NetBSD still supports it when running on a q-bus VAX: https://github.com/NetBSD/src/blob/trunk/sys/dev/qbus/if_qe....
It has some pretty broken behavior regarding multicast/broadcast traffic IIRC, but nothing putting it behind a vlan or separate LAN altogether wouldn't solve. I've got a little lsi-11 system under my bed I'm hoping to, one day, get the Fuzzball [0] distribution running on. The 22-bit address extension wirewrap the previous owner did needs to be redone entirely, so it's been a "later" project for
Read the rest
years now, but I am hoping my little DEQNA will be able to ping the Internet still.
[0] https://en.wikipedia.org/wiki/Fuzzball_router
>Claude assisted code found in external/ibm-public/postfix/dist...
That is from the original post in the thread. Is that really due to LLM ? I do not know since I avoid AI as much as I can.
But the person also posted this link too:
https://github.com/NetBSD/src/commit/f764ddf4062e855f73fe2e3...
In Openrsync: An implementation of rsync, by the OpenBSD teamAlso, the *BSD are structured somewhat differently to a Linux distro.
It's not like the Linux world where you have distinct projects like the Kernel, GNU, OpenSSL, and then it's the distributions job to assemble everything.
In the BSD projects, the scope is developing and distributing an entire base system, i.e., the kernel but also the libc, the shell/all posix utilities, and a few third parties like OpenSSH (which are usually "softforked").
It's quite visible in the sources, it's a lot more than just a kernel:
https://github.com/NetBSD/src
Additional packages you could get from pkg_in/pkgsrc (NetBSD), pkg-ng/ports (FreeBSD) or pkg_add (OpenBSD) are clearly distinct from the base system, installed in a dedicated subtree (/usr/src in NetBSD, /usr/local/ OpenBSD/FreeBSD), and provided in a best effort manner.
The reproducible build target
Read the rest
was almost certainly only for the base system, which is a few percent of what Debian tries to achieve, and on which NetBSD has a tighter control over (developer + distributor instead of downstream assembler+distributor).
A reproducible base system is useful, but given how quickly you typically need to install packages from pkgsrc, it's not quite enough.
I was saying that NetBSD works on those older systems, while it either has no support (64-bit POWER) or spotty support (modern ARM) on more modern platforms. I've got netbooting set up for all of them, and it's "useful" for testing, though even a 20 MHz VAX is pain and suffering (12+ hours to generate RSA private keys for SSH).
FWIW, Linux does work fine on the Alpha, it's just slow. Both NetBSD and Linux have busted framebuffers on my workstation, which has a 3DLabs graphics chipset. Having acceleration enabled causes Linux to output pure garbage, and NetBSD to kernel panic. The CPU performance is surprisingly okay, though. About half the performance of an original Raspberry Pi, in pure integer math...
Linux is busted on my SPARC box though, not because of the system itself, but a bug in the Weitek 2000A CPU. It was an aftermarket part f
Read the rest
rom Weitek, and in order to retrofit an 80 MHz CPU into a system with discrete MMU and cache chips that expect a 40 MHz single-issue RISC processor, it adds a funky on-chip cache, branch-predictor, and instruction prefetcher.
Details on specifics are ~impossible to find nowadays, but the word on Usenet was that chips made before 1995 are no good for Linux. My limited testing with a '93 chip corroborates this. I really ran into this while building a new Sprite [0] distribution, where I learned this chip makes tons of spurious page faults from the branch predictor hitting bogus instructions, which causes the Sprite (and Linux?) kernel to freak out. This corroborates the Usenet reports for random signal 11s killing processes on Linux...
Doesn't effect NetBSD, though. I think this [1] code is why (replaces the bogus fault address with the process counter) but I'm not sure. I have a partial fix for Sprite's kernel which allows userspace to boot up and work, and have networking fixed, but if you sneeze it kernel panics and murders the Sprite-bespoke filesystem, so testing has been a slog. :-)
[0] https://en.wikipedia.org/wiki/Sprite_(operating_system)
[1] https://github.com/NetBSD/src/blob/trunk/sys/arch/sparc/spar...
One of the cooler Unix command utilities is tsort, which performs a topological sort. Basically you give it a list of items (first word in each line) and their dependencies (subsequent words on each line) and it sorts them accordingly, similar to how, e.g., Make builds a graph of targets and dependencies to run recipes in the correct order. https://en.wikipedia.org/wiki/Tsort https://pubs.opengroup.org/onlinepubs/9799919799/utilities/t...
However, I've never found a use for it. Apparently it was written for the Version 7 Unix build system to sort libraries for passing to the linker. And still used.[1][2] But of the few times I've needed a topological sort, it was part of a much larger problem where shell scripting was inappropriate, and implementing it from scratch using a typical sort routine isn't that difficult. Still, I'm waiting for
Read the rest
an excuse to use it someday, hopefully in something high visibility so I can blow people's minds.
[1] https://github.com/openbsd/src/blob/17290de/share/mk/bsd.lib...
[2] https://github.com/NetBSD/src/blob/7d8184e/share/mk/bsd.lib....
What's interesting is that the syscall-compatibility layers in the BSDs began with SunOS binary compat on NetBSD m68k/32-bit sparc-- which was created by Theo de Raadt.
https://marc.info/?l=openbsd-tech&m=161435521906992&w=2
https://github.com/NetBSD/src/commit/6ce3f21
https://github.com/NetBSD/src/commit/1a68594
He also came to the same conclusion compat layers were a dead end (OpenBSD removed all compat_*(8) support, including Linux).
In Unofficial Windows 11 requirements bypass tool allows disabling all AI features> Isn't powerd off by default
Sometimes it's on, see https://ftp.netbsd.org/pub/NetBSD/NetBSD-release-10/src/etc/...
> By default only one tty is enabled
Ah, but the rest is getting enabled by the installer, see https://github.com/NetBSD/src/blob/netbsd-10/usr.sbin/sysins...
> NetBSD might have some "bloatware" but _the user must enable it_ first
> Everything is off by default. That is one of the things that makes NetBSD great IMHO
I mean, it gets pretty close to that, and I don't even mind syslogd and powerd, but I'm confused why they enable stuff like postfix, inetd and makemandb without asking. Especially makemandb is pretty intensive on slow machines.
> "I was able to fix it by adding usermod disable wss to the bootloader line."
> Does he mean userconf
Whoopsie, that's on me, good catch!
In Running NetBSD on IBM ThinkPad 380ZI like NetBSD sh's nextopt <https://github.com/NetBSD/src/blob/23fcbd850aae17ef0843523f3...>. Since getopt's internal state can't be reset portably, most shells roll their own option parser.
In getopt() but smallerAwk is cool. It's a full-fledged programming language that's there in anything remotely unix-flavored, but I mostly see it used in one-liners to grab bits of text from piped stdout.
But you can use awk as a general-purpose scripting language [1], in many ways it's nicer than bash for this purpose. I wonder why you don't see more awk scripts in the wild. I suppose perl came along and tried to combine the good features of shell, awk, and sed into one language, and then people decided perl was bad and moved on from that.
[1] Random excerpt from NetBSD's source code
https://github.com/NetBSD/src/blob/trunk/sys/dev/eisa/devlis...
In Aho – a Git implementation in AwkIf anyone wants to review the NetBSD implementation, see:
https://github.com/NetBSD/src/blob/trunk/sys/net/if_wg.c
In WireGuard in FreeBSDAt least NetBSD make (also used by FreeBSD, and packaged as bmake in some distros) has the same optimization:
https://github.com/NetBSD/src/blob/netbsd-9/usr.bin/make/com...
In An opinionated approach to GNU Makeor, do!
https://github.com/NetBSD/src/tree/trunk/lib/libedit
also:
isn't the entire GNU project itself someone 'being a prick and writing their own unix because the terms of the AT&T one were not to their liking'?
(pay no attention to the Berkely UNIX behind the curtain)
also also:
isn't this hacker news?
In Things to Know About GNU ReadlineShowing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.