38 lines
1.5 KiB
Plaintext
38 lines
1.5 KiB
Plaintext
|
# This configuration file lists filesystem objects that should get verified
|
||
|
|
# during startup and be created if missing.
|
||
|
|
#
|
||
|
|
# Entries have the following format:
|
||
|
|
# <type> <owner> <group> <mode> <path> <linksource>
|
||
|
|
# where the items are separated by whitespace !
|
||
|
|
#
|
||
|
|
# The # character introduces a comment lasting until end of line.
|
||
|
|
# Blank lines are ignored.
|
||
|
|
#
|
||
|
|
# <type> : d|f|l : (d)irectory|(f)ile|(l)ink
|
||
|
|
#
|
||
|
|
# A linking example:
|
||
|
|
# l root root 0777 /var/test /tmp/testfile
|
||
|
|
# f root root 0644 /var/test none
|
||
|
|
#
|
||
|
|
# Understanding links:
|
||
|
|
# When populate-volatile is to verify/create a directory or file, it will first
|
||
|
|
# check it's existence. If a link is found to exist in the place of the target,
|
||
|
|
# the path of the target is replaced with the target the link points to.
|
||
|
|
# Thus, if a link is in the place to be verified, the object will be created
|
||
|
|
# in the place the link points to instead.
|
||
|
|
# This explains the order of "link before object" as in the example above, where
|
||
|
|
# a link will be created at /var/test pointing to /tmp/testfile and due to this
|
||
|
|
# link the file defined as /var/test will actually be created as /tmp/testfile.
|
||
|
|
d root root 1777 /run/lock none
|
||
|
|
d root root 0755 /var/volatile/log none
|
||
|
|
d root root 1777 /var/volatile/tmp none
|
||
|
|
l root root 1777 /var/lock /run/lock
|
||
|
|
l root root 0755 /var/run /run
|
||
|
|
l root root 1777 /var/tmp /var/volatile/tmp
|
||
|
|
l root root 1777 /tmp /var/tmp
|
||
|
|
d root root 0755 /var/lock/subsys none
|
||
|
|
f root root 0664 /var/log/wtmp none
|
||
|
|
f root root 0664 /var/run/utmp none
|
||
|
|
l root root 0644 /etc/resolv.conf /var/run/resolv.conf
|
||
|
|
f root root 0644 /var/run/resolv.conf none
|