summaryrefslogtreecommitdiffstats
path: root/dev-tools/debugging-tools/network.functions
diff options
context:
space:
mode:
authorSimon Rettberg2024-06-13 15:41:01 +0200
committerSimon Rettberg2024-06-13 15:41:01 +0200
commitbed4315a7ca1c67b5528e2a5def6ded1dcf26054 (patch)
tree1b0e840560659342e149c57cd6c79ec0e52e240c /dev-tools/debugging-tools/network.functions
parentDe-duplicate tools copied vs. what busybox ships (diff)
downloadsystemd-init-bed4315a7ca1c67b5528e2a5def6ded1dcf26054.tar.gz
systemd-init-bed4315a7ca1c67b5528e2a5def6ded1dcf26054.tar.xz
systemd-init-bed4315a7ca1c67b5528e2a5def6ded1dcf26054.zip
[slx-dmsetup] Avoid unnecessary dm targets, rename crypted ones
1) Avoid creating linear targets that would be fully covered by an encrypted target later. Also don't create a linear slice for the thinpool if it's going to be the only thing we put in our writable partition. 2) Previously, when we created an encrypted device, it would look like | ` devicename ` devicename-crypt Which was a bit confusing/surprising, because the final name was not what was specified in our custom partition table. Now, the result would look like | ` devicename-k ` devicename So the final device you'd use has the expected name.
Diffstat (limited to 'dev-tools/debugging-tools/network.functions')
0 files changed, 0 insertions, 0 deletions