Page MenuHomeFreeBSD

geli taste: allow GELIBOOT tagged providers as well
ClosedPublic

Authored by kevans on Jan 27 2020, 11:02 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Sep 29, 12:00 AM
Unknown Object (File)
Sep 17 2025, 4:13 AM
Unknown Object (File)
Sep 17 2025, 2:52 AM
Unknown Object (File)
Sep 8 2025, 3:45 AM
Unknown Object (File)
Aug 20 2025, 4:36 AM
Unknown Object (File)
Aug 11 2025, 9:45 AM
Unknown Object (File)
Jul 27 2025, 10:43 AM
Unknown Object (File)
Jul 22 2025, 11:47 AM
Subscribers

Details

Summary

Currently the installer uses -bg, but it seems like it'd be sensible for -g to imply that we want this partition to be attached at boot since that's presumably our root filesystem.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This doesn't break multiple encrypted disks?
If I have 3 disk and only one should be decrypted by the loader?

This doesn't break multiple encrypted disks?
If I have 3 disk and only one should be decrypted by the loader?

I'm not sure I follow- I have no intention of changing how loader determines what should be decrypted, just to reduce/eliminate the need to tag both GELIBOOT and BOOT to get the kernel to taste the partition that was tagged for decrypting by loader.

Oh sorry I miss read the patch.
Then this looks good to me :)

This revision is now accepted and ready to land.Feb 7 2020, 7:58 PM
This revision was automatically updated to reflect the committed changes.