On Mon, Mar 23, 2015 at 5:28 PM, Randy Witt
randy.e.w...@linux.intel.com wrote:
If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there, they will no longer be able to be
accessed
once the tmpfs gets mounted at /var/volatile.
why not use
On 03/24/2015 08:53 AM, Khem Raj wrote:
On Mar 24, 2015, at 8:46 AM, randy.e.w...@linux.intel.com wrote:
On Mon, Mar 23, 2015 at 5:28 PM, Randy Witt
randy.e.w...@linux.intel.com wrote:
If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there,
On Mar 24, 2015, at 8:46 AM, randy.e.w...@linux.intel.com wrote:
On Mon, Mar 23, 2015 at 5:28 PM, Randy Witt
randy.e.w...@linux.intel.com wrote:
If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there, they will no longer be able to be
On Mon, Mar 23, 2015 at 5:28 PM, Randy Witt
randy.e.w...@linux.intel.com wrote:
If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there, they will no longer be able to be accessed
once the tmpfs gets mounted at /var/volatile.
why not use copy-bind
If /var/volatile is a mount point it shouldn't contain any files before
mount time. If files are there, they will no longer be able to be accessed
once the tmpfs gets mounted at /var/volatile.
This problem can be seen for instance when systemd creates
/var/volatile/log/journal as part of its
