<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014-01-01 1:12 PM, Kevin Korb
<a class="moz-txt-link-rfc2396E" href="mailto:kmk@sanitarium.net"><kmk@sanitarium.net></a> wrote:<br>
</div>
<blockquote cite="mid:52C45A99.6020905@sanitarium.net" type="cite">
<pre wrap="">The files will not be transferred but they will be stored separately
as new versions of the file even if the content is the same.</pre>
</blockquote>
<br>
Ok, so, 'stored separately' = take up additional space? which is
what I want to avoid.<br>
<br>
<blockquote cite="mid:52C45A99.6020905@sanitarium.net" type="cite">
<pre wrap="">Permissions are per inode not directory entry so you can't have old
and new permissions without breaking the hard link relationship.</pre>
</blockquote>
<br>
Yeah, this is why I asked... thx...<br>
<br>
<blockquote cite="mid:52C45A99.6020905@sanitarium.net" type="cite">
<pre wrap="">The easiest solution is to just do the same chmod on the most recent
backup before running the next backup.</pre>
</blockquote>
<br>
Ah, that should work perfectly...<br>
<br>
So, just to make sure I understand, when I change the perms on the
most recent backup, if I were to go back and look at any of the
previous backups before that one, any files in those older backups
that contain files that are hard-linked in the most recent backup
would reflect the new permissions too, right?<br>
<br>
Thanks!<br>
<br>
<div class="moz-signature">-- <br>
<br>
Best regards,<br>
<br>
<b><i>Charles</i></b><br>
</div>
</body>
</html>