summaryrefslogtreecommitdiff
path: root/rules.d
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2021-03-02 18:57:04 +0100
committerYu Watanabe <watanabe.yu+github@gmail.com>2021-03-03 12:16:32 +0900
commit725ad3b06288b2beeaaf178120010612a30646e4 (patch)
treeed62db87f169bc887b495d327696270862554b44 /rules.d
parentab05bee1dd9e59a34c2f4866a1285dc29c010904 (diff)
downloadsystemd-725ad3b06288b2beeaaf178120010612a30646e4.tar.gz
fstab-generator: add new root=tmpfs option
It's useful to be able to combine a regular /usr/ file system with a tmpfs as root, for an OS that boots up in volatile mode on every single boot. Let's add explicit support for this via root=tmpfs. Note the relationship to the existing systemd.volatile= option: 1. The kernel command line "root=/dev/… systemd.volatile=yes" will mount the specified root fs, and then hide everything at the top by overmounting it with a tmpfs, except for the /usr subtree. 2. The kernel command line "root=tmpfs mount.usr=/dev/…" otoh will mount a toot fs at the top (just like the case above), but will then mount the top-level dir of the fs specified in mount.usr= directly below it. Or to say this differently: in the first case /usr/ from the physical storage fs is going to become /usr/ of the hierarchy ultimately booted, while in the second case / from the physical storage fs is going to become /usr of the hierarchy booted. Philosophically I figure systemd.volatile= is more an option for "one-off" boots, while root=tmpfs is something to have as default mode of operation for suitable images. This is currently hard to test reasonably, since Dracut refuses to accept root=tmpfs. This needs to be addressed separately though.
Diffstat (limited to 'rules.d')
0 files changed, 0 insertions, 0 deletions