UPDATING and src.conf.5 updates too?

New diff addressing points raised

A note that mail to dteske is timing out and bouncing, so am inclined to commit this.

Is it possible to have a minimal port that solves this problem please?

In D37503#852734, @carlavilla wrote:

Looks good to me.
Only to improve my English. Why "FreeBSD's Handbook" is not ok?
I always thought that you use this to express that the Handbook is "property?" of FreeBSD.

Reword. This would have benefitted from much wider review, from inception to commit. Please allow more time for these wide-ranging changes, and perhaps invite feedback on the doc@ mailing list.

I think doceng need to decide if this is a valid engineering goal, based on recent discussions.

Running out of battery so submitting what I have reviewed. Generally speaking I think the shorter text works against the intent of this being a guide, I'm afraid.

Clarify situation muddied by mention of the port.

Lgtm, thanks.

Thanks!

Odd. Thanks.

OK; I'm going to abandon this review then and just hook up the page as is.
Thanks both.

In D30998#697446, @fernape wrote:

In D30998#697422, @ceri wrote:

In D30998#697421, @manu wrote:

Just realized that we install most OF_* manpages on all arches.
And always installing nvmem.9 would help people developing on amd64 for embedded (most people do that) so I think that this should always be installed.
Sorry for not noticing before.

That's ok; the work that @fernape is doing on installing all manpages anyway should take care of that and will be the default, so the logic here would then just allow people who didn't want the page to leave it out.

Since MAN_ARCH=all by default starting at 0a0f7486413c147d56808b38055c40c64cff61f5 maybe we could add || empty(${MAN_ARCH}) || ${MAN_ARCH} == "all" to that condition. That is what I plan to do with the remaining pages not covered by the initial commit.

In D30998#697421, @manu wrote:

Just realized that we install most OF_* manpages on all arches.
And always installing nvmem.9 would help people developing on amd64 for embedded (most people do that) so I think that this should always be installed.
Sorry for not noticing before.

Could you add egrep to the .Xr section please?

Can we try https://reviews.freebsd.org/F24494081 - this also removes text that clang is imparting to people anyway.

In D30807#695022, @kevans wrote:

In D30807#695258, @grembo wrote:

In D30807#695219, @kevans wrote:

So basically "blacklisted" was not the correct term to begin with.

This is my opinion, yes. I'm still searching for more ideal verbiage

If I would just start implementing this (without any external limitations I'm not aware of), I would probably do something like creating one directory called all and one called trusted with entries in trusted being symbolic links to certificates in all and check those into git.

caroot
|-- all
|   `-- GTS_Root_R1.pem
`-- trusted
    `-- GTS_Root_R1.pem -> ../all/GTS_Root_R1.pem

There are probably reasons why this isn't feasible though.

Fix build with dbaio's clean tree; address comments.

Keen to see some version of this committed, as the current instructions left my laptop unbootable.
Am testing the rest of this.