git: dm_target_crypt - make the next generation (ng) module the default

[Michael Neumann]

On Sun, Aug 10, 2025 at 12:09:25PM +0800, Aaron LI wrote:
> On 7/30/25 3:03 AM, Michael Neumann wrote:
> > commit f9c79d28d9ec0c95b4e78c6374f774077944db5e
> > Author: Michael Neumann <mneumann at ntecs.de>
> > Date:   Tue Jul 29 20:23:45 2025 +0200
> > 
> >      dm_target_crypt - make the next generation (ng) module the default
> >      * The next generation version has been thoroughly tested by me for the
> >        last few months
> >      * Remove the "legacy" dm_target_crypt code and module
> >      * Rename dm_target_crypt_ng -> dm_target_crypt (in the source tree
> >        dm/crypt_ng -> dm/crypt)
> >      * Whenever you read "dm_target_crypt_ng" in old commit messages, this
> >        is now the current module (just named "dm_target_crypt"). Sorry for
> >        the confusion
> >      * swapon(8) will now pick up the new module, as "dm_target_crypt" is
> >        hard-coded in it
> >      * Check your /boot/loader.conf and change `dm_target_crypt_ng_load=YES`
> >        to `dm_target_crypt_load=YES` in case of need
> 
> Hi Michael,
> 
> Sorry for delayed reply.

No worries :)

> I think we should add 'TO_REMOVE+=/boot/kernel/dm_target_crypt_ng.ko' to
> Makefile_upgrade.inc.

Thanks for the suggestion. I've added that!

Normally, you want to do a "make installkernel" beforehand, if you
upgrade world.


Regards,

  Michael

> 
> Cheers,
> Aaron