My first thought about ENODEV was something about GEOM. ENOENT, on the other hand, would make it obvious what's going on: the root device node is simply not there.

I've been burned by this in the past, but I've assumed it's just me. This time, though, there was another person involved, and this made me reconsider. In this case it's not even that it's a remote machine: this is for a homebrew remote management mechanism; essentially we have BeagleBone Blacks hooked up to the actual machine, which provide remote console and virtual media, and halting one of those by mistake - for example when you fail to notice the cu(1) to the "real" machine has been disconnected - results in having to power cycle the whole thing, which is one thing our BBB-based remote management does not provide.

Linux, it’s a Linux core file :-) The easiest way is to use debootstrap port to bootstrap an Ubuntu Bionic userland, then chroot there and do “apt install gdb”. See https://wiki.freebsd.org/LinuxJails.

I’m not opposed to this patch, but isn’t this what core files are for?

Fix sc_fpstate.

It's gonna be two weeks soon, can I assume a timeout for releng?

Few more nits - most from Pau, but there's also two grammar fixes
I've noticed.

Nice! This cleanup was long overdue. A few nits though.

Rebase (the mechanical change got committed) and reword
things a bit to make them bit less src-centric; point
at {contributing} instead.

In D34134#771952, @dbaio wrote:

I prefer the previous/first patch you sent, with the titles.

It's clean, and the page emphasizes only releases, but CURRENT and STABLE have their spot.

For me, that looks good.

But let's wait for others.

Back to the first version.

Perfect. There's not much that's needed: literally a single sentence for the linux(4) man page, and perhaps a paragraph for the Handbook. It's more about pointing users at the package than explaining everything in details.

In D34134#771931, @gjb wrote:

In D34134#771926, @trasz wrote:

Btw, it would be nice if we could provide a direct link to amd64 14-CURRENT memstick image, but the filenames contain git revisions, so it's a bit impractical. Perhaps we could have a symlink?

The download mirrors are already over-polluted with symlinks.

Go a bit further.

Btw, it would be nice if we could provide a direct link to amd64 14-CURRENT memstick image, but the filenames contain git revisions, so it's a bit impractical. Perhaps we could have a symlink?

Preview: https://people.freebsd.org/~trasz/D34134.html