mirror of
https://github.com/systemd/systemd.git
synced 2024-11-01 17:51:22 +03:00
6c5496c492
For encrypted block devices that we need to unlock from the initramfs, we currently rely on dracut shipping `cryptsetup.target`. This works, but doesn't cover the case where the encrypted block device requires networking (i.e. the `remote-cryptsetup.target` version). That target however is traditionally dynamically enabled. Instead, let's rework things here by adding a `initrd-cryptsetup.target` specifically for initramfs encrypted block device setup. This plays the role of both `cryptsetup.target` and `remote-cryptsetup.target` in the initramfs. Then, adapt `systemd-cryptsetup-generator` to hook all generated services to this new unit when running from the initrd. This is analogous to `systemd-fstab-generator` hooking all mounts to `initrd-fs.target`, regardless of whether they're network-backed or not.
18 lines
564 B
SYSTEMD
18 lines
564 B
SYSTEMD
# SPDX-License-Identifier: LGPL-2.1+
|
|
#
|
|
# This file is part of systemd.
|
|
#
|
|
# systemd is free software; you can redistribute it and/or modify it
|
|
# under the terms of the GNU Lesser General Public License as published by
|
|
# the Free Software Foundation; either version 2.1 of the License, or
|
|
# (at your option) any later version.
|
|
|
|
[Unit]
|
|
Description=Initrd Encrypted Volumes
|
|
Documentation=man:systemd.special(7)
|
|
OnFailure=emergency.target
|
|
OnFailureJobMode=replace-irreversibly
|
|
AssertPathExists=/etc/initrd-release
|
|
DefaultDependencies=no
|
|
Conflicts=shutdown.target
|