Please consider adding a brief package message to cover key points. Maybe something along these lines: * end user preparedness to build and install from source, should the need arise * caution if intending to use the module with a boot pool on FreeBSD 12.⋯ * create, activate then boot a new boot environment before editing /boot/loader.conf * edition of /boot/loader.conf i.e. zfs_load="NO" openzfs_load="YES"
Created attachment 227605 [details] proposed first-install message for new users hi Ryan this would be a great help. And we should also mention where users should report bugs - in BZ? in the ZoF repo? or upstream in the ZoL repo? I'm happy to commit this, if that helps.
Thank you, (In reply to Dave Cottlehuber from comment #1) In lieu of: - remove zfs_load=... – maybe advise a change from YES to NO. To have the zfs_load line readily available will be slightly more foolproof, should a person somehow dig himself or herself into a hole.
FreeBSD 12.⋯ ============ Whilst also thinking about this use case, and possible advice to change YES to NO where /boot/loader.conf includes this: opensolaris_load="YES" – I stumbled across (arm64) bug 240478 comment 9: > After the switch to OpenZFS this line must be added to loader.conf: > > cryptodev_load="YES"
https://cgit.freebsd.org/ports/commit/?id=a4fbc9aaa13e475b1150823011948209c82d6775
(In reply to Dave Cottlehuber from comment #1) I didn't mention it in the package messages, but you can simply report it to the openzfs/zfs repo we build the port from directly.