kernel
/
dracut
mirror of https://git.kernel.org/pub/scm/boot/dracut/dracut.git/
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
136 Commits
1 Branch
68 Tags
6.7 MiB
Tree: f8a22bfb95
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f8a22bfb95'
${ noResults }
dracut/modules.d/90crypt/63-luks.rules

14 lines
379 B
Raw Normal View History Unescape

Support root on LUKS (dm-crypt) Support having root on LUKS with the password prompting handled by plymouth. This requires ensuring our input is from /dev/console and also requires that we import vol_id info about all block devices rather than ignoring dm devs (which is what the persistent storage rules do by default)
16 years ago
# hacky rules to try to try unlocking dm-crypt devs
#
# Copyright 2008, Red Hat, Inc.
# Jeremy Katz <katzj@redhat.com>
SUBSYSTEM!="block", GOTO="luks_end"
ACTION!="add|change", GOTO="luks_end"
Import volume info here too (noticed by wtogami with root-on-crypt-lv)
16 years ago
KERNEL!="sr*", IMPORT{program}="vol_id --export $tempnode"
Make cryptroot handling act as a real producer/consumer. This should handle the case of having more than one encrypted block device on the system as best we can right now.
16 years ago
ENV{ID_FS_TYPE}=="crypto_LUKS", RUN+="/bin/sh -c 'echo $env{DEVNAME} luks-$env{ID_FS_UUID} >>/cryptroot'"
Support root on LUKS (dm-crypt) Support having root on LUKS with the password prompting handled by plymouth. This requires ensuring our input is from /dev/console and also requires that we import vol_id info about all block devices rather than ignoring dm devs (which is what the persistent storage rules do by default)
16 years ago
LABEL="luks_end"