I'll have to make a rescue image to verify, but I think we can drop these two files, and let cust_allow_ssh_root handle it.

Is this an April fools' joke?, if not nice!

Thanks, I appreciate it!

This was much needed, thank you!

Landed as 325ebf37d8efc6488754051fcc2b1aaa40cefd8b.

More testing is needed on frame buffer consoles.

In D34532#782394, @imp wrote:

A lot depends on which terminal emulator you are on.

Briefly mention the new function in rc.subr(8).

Thank you. I’ll add a brief mention to it in rc.subr(8).

Sorry, for a moment I doubted about changing echo -n to printf.

Add missing $@.

In D34426#780372, @markj wrote:
I'm not too familiar with the history of zpool versions - isn't the problem really with feature flags? I suppose we'd need to identify the set of pool features supported by a reasonable range of FreeBSD releases, and ensure that only those features are enabled. A firstboot rc.d script could be used to upgrade the pool.

This is a nice addition!

Landed as 91a35e5803bef59b8ca67b0621216124cc2e42f8.

Moving this, formerly GitHub PR #580, here.

Thank you!
I can offer this HW info:

I have been using a memory-mapped console (Apollo Lake E3950) by adding to /boot/loader.conf.d/console.conf:

Since you want to speed up primarily AWS instances, would disabling Duplicate Address Detection shave a couple of seconds of boot time (i.e. pass no_dad to ifconfig_DEFAULT in ec2.conf for testing purposes only)?

I prefer this approach.

Would this solve the problem on those buses for you?

Thank you!

It has been updated! (Without the c-ares bump, nor the portlint) Thank you all for taking care of it!

I have updated my PR with the latest version. I don't know why this has reached maintainer's timeout, usually the maintainer is very keen.

Great! You beat me to it. I was waiting until tomorrow's security fixes to resubmit.

Reading the usage message, I wonder if status, poll, and reload should also be added to the list?

I like the overall intention, however the example provided can be accomplished without any patch with:

I believe this commit has broken the cross-builds on GitHub.

There’s also this one:

ixl0: Failed to initialize SR-IOV (error=2)

I have created PRs: 257900, 257902, 257903. (I don't see node12 in ports). Thank you!

Adding some upgrade notes here for reference:

Version 14.17.4 LTS is already published, it fixes a CVE and avoids the need of a patch (js-list-format.cc).

The idea was to make it more in line with pflog's behavior, and of course to silence the warning. The patch is good as is for me, however.

I guess, the man pages also need their default version string updated?

I can't see any reason that one would want to run both interfaces.

Works fine. Thank you!

Something like:

It should go in /usr/local/lib/node_modules/yarn/package.json.

Thank you!

I'm moving my suggestions here per request of the package maintainer: