Lines Matching refs:only

26    read-only (the latter via e.g. a read-only bind mount on itself) in order
32    been modified to behave accordingly when these file systems are read-only.
33    (It's OK to mount `/sys/` as `tmpfs` btw, and only mount a subset of its
35    so on. If you do that, make sure to mark `/sys/` read-only, as that
42    ttys, to avoid being killed by SAK. It only opens ttys for the time it
57    will check for `/sys/` being read-only, as an indication whether device
58    management can work. Therefore make sure to mount `/sys/` read-only in the
60    read-only state of `/sys/`, including PID 1 itself and `systemd-networkd`.
72    "upper" parts read-only of the hierarchies, and only allow write-access to
74    all controller hierarchies with exception of `name=systemd` fully read-only
75    (this only applies to cgroupv1, of course), to protect the controllers from
76    alteration from inside the containers. Or to turn this around: only the
90    Do not add new cgroup directories to the top of the tree. This will not only
103    the UUID for `/etc/machine-id` to some manager supplied value. This is only
107    to the effect of `qemu`'s `-uuid` switch). Note that you should pass only a
108    UUID here that is actually unique (i.e. only one running container should
121    variable's name you may only specify ptys, and not other types of ttys. Also
144    some location (ideally a read-only and non-swappable file system, like
169    do a clean shutdown. Note however, that since only systemd understands
221 hierarchy — and probably most subdirs should be read-only to the
231    it only, and is mostly an internal vehicle to achieve this. Other container
316 6. Don't mount only a sub-tree of the `cgroupfs` into the container. This will not
330    read-only state of `/sys/` enables a nice automatism: as soon as `/sys/` and
336    `/sys/` read-only.)
386 own. Note though that this file is only accessible to root. systemd hence early