1# This configuration file lists filesystem objects that should get verified 2# during startup and be created if missing. 3# 4# Entries have the following format: 5# <type> <owner> <group> <mode> <path> <linksource> 6# where the items are separated by whitespace ! 7# 8# The # character introduces a comment lasting until end of line. 9# Blank lines are ignored. 10# 11# <type> : d|f|l|b : (d)irectory|(f)ile|(l)ink|(b)ind 12# 13# A linking example: 14# l root root 0777 /var/test /tmp/testfile 15# f root root 0644 /var/test none 16# 17# Understanding links: 18# When populate-volatile is to verify/create a directory or file, it will first 19# check it's existence. If a link is found to exist in the place of the target, 20# the path of the target is replaced with the target the link points to. 21# Thus, if a link is in the place to be verified, the object will be created 22# in the place the link points to instead. 23# This explains the order of "link before object" as in the example above, where 24# a link will be created at /var/test pointing to /tmp/testfile and due to this 25# link the file defined as /var/test will actually be created as /tmp/testfile. 26d root root 1777 /run/lock none 27d root root 0755 /var/volatile/log none 28d root root 1777 /var/volatile/tmp none 29l root root 1777 /var/lock /run/lock 30l root root 0755 /var/run /run 31l root root 1777 /var/tmp /var/volatile/tmp 32l root root 1777 /tmp /var/tmp 33d root root 0755 /var/lock/subsys none 34f root root 0664 /var/log/wtmp none 35f root root 0664 /var/run/utmp none 36l root root 0644 /etc/resolv.conf /var/run/resolv.conf 37f root root 0644 /var/run/resolv.conf none 38