• Wordsmith

Remove password prompt from the example

• address feedback (I answered some of the comments directly or at least marked them as done)
• sort copyright header

I'll close this revision now that the underlying problem has apparently been fixed.

@ziaee I tested the LSI SAS 3908 (MegaRAID 9560 8i), with 14.3-RELEASE. The mrsas driver is automatically loaded, it works with either JBOD mode or RAID0. However, after devctl detach -f and devctl set driver -f device mpr, devctl responded with "device not configured". Even with hint.mpr.0.at="pcix:y:z" in device.hints, the mrsas driver will be loaded instead of the mpr one. In my test, mpr driver does not support SAS 3908, at least with the current firmware.

Awesome, thank you so much. When you test it tomorrow, could you also test blacklisting it and using mrsas as well? We've been having a big problem trying to identify what is supported lately, and we do have an open review for it:

IIRC, I only have LSI 3808 (MegaRAID 9500 8i), and I could test it tomorrow. The original mailing list about LSI 3808 I found is Re: SAS3808 PCI-E 4.0, FreeBSD / ZFS support ?.

Have you tested this? There is also a newer driver called mrsas.

Thank you so much. Tested, confirmed, and pushed!

• UMA -> uma

Please close PR:121440 since this change is not needed.

LGTM, Thanks!

Seems reasonable to me, thanks!

Incorporate review feedback

Can any SME's confirm so we can get this in?

This is a very nice improvement over not having a flua man page!

Is the fix for PR 121440 to close as not a bug?
I'm not sure what to do otherwise, based on your comment.

Not really part of this specific problem, but jail(8) should auto-recognize list parameters because their SYSCTL_JAIL specification has a type with ",a" appended. Ideally, it would build a list of such parameters it sees like that. For non-kernel parameters like vnet.interface and zfs.dataset, putting them in the array is probably as good as its going to get.

Looks good to me.

The tests looks good. I need some time to read the code carefully ...

Manpage LGTM

Thank you!

If you do not use arc diff --create/--update please upload a diff -U9999 so that there is context to be displayed.

I'm sorry, I won't do it again. I thought it would be a hilarious way to ping.

Please don't accept your own revisions. That's implied ;-)

Bump dates

Yes. Going to do so now.

Can you bump .Dd on all these (I'll also need to do on iwm.4 given I forgot)

Correct I missed another spot, some of my slashes were backwards.

I did miss a spot.
The table in urtw looked ever so slightly off, turns out the syntax was completely wrong (e.g. mdoc(7) says mdoc files should never have a tab for any reason, but the linter didn't see that.
Also, every network device driver manual afaik uses driver in the title, except a few, so fix those.

Once this is settled, I'll begin writing a section in style.mdoc(5) describing preferred style for hardware section in manuals, so we can make it more consistent going forward.

I'll just get this in; we'll have a few days until we'll expand anything from this file again.

Use a bullet list for hardware
While here improve some language and fold pesky lines.

In other words, I'd prefer the way iwlwifi got rendered over the way rtw88 got rendered.

I'll leave the comment here (applies to github as well I would assume):

+ s/Nm iwmfw/Xr iwmfw 4/
+ adjust HARDWARE to proposed display block convention

I'd like to make it consistent if possible. The patch on github switches from Bl to Bd so that the extra spaces used for alignment will render.

Okay, thanks Graham! That sounds good. Next push will revert proposed example prompts.

(Sorry, I forgot to click "submit" when I looked at this a few days ago.

Correct my backwards forward slash, thank you for your patience.

mention 802.11a, and convert example to cidr notation! Thank you so much, many people in the community have wanted this for a long time. I'll do the rest of them in one review.

192.0.2.20/24 (and we can ditch the netmask line). 192.0.2.0 is the network address.

I wonder if we want to add a note forward to iwlwifi(4). @emaste I seem to remember you having a review open to switch defaults. Do we want to leave a note here at least that all these devices are equally supported by iwlwifi(4)?

malo has had a hardware section since malo appeared in 3c7e78d32 for FreeBSD 7.1

Where's the change for malo(4)?

I was auditing the list after discovering that an(4) was already removed prior to FreeBSD 14 and discovered that malo(4) already has a hardware section, so add it in.