summaryrefslogtreecommitdiffstats
path: root/abs/core/plymouth/plymouth-encrypt.install
diff options
context:
space:
mode:
authorBritney Fransen <brfransen@gmail.com>2013-11-29 20:03:49 (GMT)
committerBritney Fransen <brfransen@gmail.com>2013-11-29 20:03:49 (GMT)
commit6d3f149ab4808e3e2e53427a7d290a1b7f27f550 (patch)
tree82a85e41602a4df87859a1b47bc1eb1e92706bc6 /abs/core/plymouth/plymouth-encrypt.install
parentd6516faa2bb58b90035609b16674cb86b75a7570 (diff)
downloadlinhes_pkgbuild-6d3f149ab4808e3e2e53427a7d290a1b7f27f550.zip
linhes_pkgbuild-6d3f149ab4808e3e2e53427a7d290a1b7f27f550.tar.gz
linhes_pkgbuild-6d3f149ab4808e3e2e53427a7d290a1b7f27f550.tar.bz2
plymouth: forgot to add some files. refs #891.
Diffstat (limited to 'abs/core/plymouth/plymouth-encrypt.install')
-rw-r--r--abs/core/plymouth/plymouth-encrypt.install50
1 files changed, 50 insertions, 0 deletions
diff --git a/abs/core/plymouth/plymouth-encrypt.install b/abs/core/plymouth/plymouth-encrypt.install
new file mode 100644
index 0000000..0ee8512
--- /dev/null
+++ b/abs/core/plymouth/plymouth-encrypt.install
@@ -0,0 +1,50 @@
+#!/bin/bash
+
+build() {
+ local mod
+
+ add_module dm-crypt
+ if [[ $CRYPTO_MODULES ]]; then
+ for mod in $CRYPTO_MODULES; do
+ add_module "$mod"
+ done
+ else
+ add_all_modules '/crypto/'
+ fi
+
+ add_binary "cryptsetup"
+ add_binary "dmsetup"
+ add_file "/usr/lib/udev/rules.d/10-dm.rules"
+ add_file "/usr/lib/udev/rules.d/13-dm-disk.rules"
+ add_file "/usr/lib/udev/rules.d/95-dm-notify.rules"
+ add_file "/usr/lib/initcpio/udev/11-dm-initramfs.rules" "/usr/lib/udev/rules.d/11-dm-initramfs.rules"
+
+###
+ add_file "/usr/share/fonts/TTF/DejaVuSans.ttf"
+ add_file "/etc/fonts/fonts.conf"
+ add_file "/etc/fonts/conf.d/60-latin.conf"
+###
+
+ add_runscript
+}
+
+help() {
+ cat <<HELPEOF
+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.
+HELPEOF
+}
+
+# vim: set ft=sh ts=4 sw=4 et: