summarylogtreecommitdiffstats
diff options
context:
space:
mode:
authorFaule Socke2016-03-04 18:37:03 +0100
committerFaule Socke2016-03-04 18:42:09 +0100
commit965674079372c0905e8e8a86e4a1789b11822067 (patch)
tree795f97b79835f0eee44d097a3db618a99a7fde92
parente8d90aeb0f2cdac2a4caab2467561d0b25306cf7 (diff)
downloadaur-965674079372c0905e8e8a86e4a1789b11822067.tar.gz
Improved documentation and help text.
-rw-r--r--PKGBUILD6
-rw-r--r--multiencrypt_install8
2 files changed, 8 insertions, 6 deletions
diff --git a/PKGBUILD b/PKGBUILD
index ced97b5fb73..342fca1605d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,8 +1,8 @@
# Maintainer: Faule Socke <github@socker.lepus.uberspace.de>
pkgname=mkinitcpio-multiencrypt
-pkgver=1.0
-pkgrel=2
+pkgver=1.1
+pkgrel=1
pkgdesc="Allows to open multiple LUKS containers during boot (optionally using just a single passphrase)"
arch=(any)
url="https://github.com/faulesocke/mkinitcpio-multiencrypt"
@@ -22,7 +22,7 @@ source=("multiencrypt_hook"
"multiencrypt_install"
"LICENSE")
sha256sums=('105be328329e6352df601d64982d90d9cea7c8e7e630739bc69f42882c8523c6'
- '504a694bc4c8c7153b5112356d498d05e652451a233ada2a575ac433c0bdd4de'
+ '06609a990366c1074b4a694525aa1e741fdb452ee1f1c1aa0f8f5e2c3191c4de'
'c03cea027b4b40e4402fabd08557736727ec3d5bc54ad64ab6472de432198cad')
validpgpkeys=()
diff --git a/multiencrypt_install b/multiencrypt_install
index 3a67244eb9f..99b269313bc 100644
--- a/multiencrypt_install
+++ b/multiencrypt_install
@@ -33,7 +33,9 @@ passphrase once and tries to reuse it for all the devices. If it fails on one
device, it asks for a password again.
Devices are specified on the kernel command line:
-cryptdevices=device1:dmname1[:options1];device2:dmname2[:options2];...
+cryptdevices="device1:dmname1[:options1];device2:dmname2[:options2];..."
+
+Don't forget the quotes here, otherwise it will not work correctly.
Options are optional and separated by commata (,). Currently only one option is
supported:
@@ -42,8 +44,8 @@ allow-discards adds --allow-discards to cryptsetup (see man 8 cryptsetup)
Unlocking via keyfile is currently not supported.
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.
+keyboard available to enter it, and you may need the keymap hook as well to
+ensure that the keyboard is using the layout you are expecting.
HELPEOF
}