diff options
author | Lennart Poettering <lennart@poettering.net> | 2022-09-23 14:59:02 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2022-09-23 15:10:53 +0200 |
commit | 32e276708089110243682d8aaa3d58075b91f0d6 (patch) | |
tree | 44a32b969266f7dfe9529f31e79046e78ca7e474 /man/udev.xml | |
parent | addc84ec9184094db4439006e8a3b955b6387f74 (diff) | |
download | systemd-32e276708089110243682d8aaa3d58075b91f0d6.tar.gz |
tree-wide: use the term "initrd" at most places we so far used "initramfs"
In most cases we refernced the concept as "initrd". Let's convert most
remaining uses of "initramfs" to "initrd" too, to stay internally
consistent.
This leaves "initramfs" only where it's relevant to explain historical
concepts or where "initramfs" is part of the API (i.e. in
/run/initramfs).
Follow-up for: b66a6e1a5838b874b789820c090dd6850cf10513
Diffstat (limited to 'man/udev.xml')
-rw-r--r-- | man/udev.xml | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/man/udev.xml b/man/udev.xml index 886455f61f..142f295f3e 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -647,13 +647,11 @@ <varlistentry> <term><option>db_persist</option></term> <listitem> - <para>Set the flag (sticky bit) on the udev database entry - of the event device. Device properties are then kept in the - database even when - <command>udevadm info --cleanup-db</command> is called. - This option can be useful in certain cases - (e.g. Device Mapper devices) for persisting device state - on the transition from initramfs.</para> + <para>Set the flag (sticky bit) on the udev database entry of the event device. Device + properties are then kept in the database even when <command>udevadm info + --cleanup-db</command> is called. This option can be useful in certain cases + (e.g. Device Mapper devices) for persisting device state on the transition from + initrd.</para> </listitem> </varlistentry> <varlistentry> |