FS#63953 - [cryptsetup] encrypt hook does not document :allow-discards.
Attached to Project:
Arch Linux
Opened by Eric Toombs (ewtoombs) - Sunday, 29 September 2019, 22:52 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:13 GMT
Opened by Eric Toombs (ewtoombs) - Sunday, 29 September 2019, 22:52 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:13 GMT
|
Details
Description:
/usr/lib/initcpio/hooks/encrypt supports :allow-discards, but this support is undocumented by mkinitcpio -H encrypt. Additional info: * cryptsetup-2.2.1-1 output of mkinitcpio -H encrypt: ==> Help for hook 'encrypt': This hook allows for an encrypted root device. Users should specify the device to be unlocked using 'cryptdevice=device:dmname' on the kernel command line, where 'device' is the path to the raw device, and 'dmname' is the name given to the device after unlocking, and will be available as /dev/mapper/dmname. For unlocking via keyfile, 'cryptkey=device:fstype:path' should be specified on the kernel cmdline, where 'device' represents the raw block device where the key exists, 'fstype' is the filesystem type of 'device' (or auto), and 'path' is the absolute path of the keyfile within the device. Without specifying a keyfile, you will be prompted for the password at runtime. This means you must have a keyboard available to input it, and you may need the keymap hook as well to ensure that the keyboard is using the layout you expect. ==> This hook has runtime scripts: -> pre-mount hook |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:13 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/cryptsetup/issues/2
Saturday, 25 November 2023, 20:13 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/cryptsetup/issues/2
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.