On Oct 17, 2012, at 1:30 AM, Steve O'Hara-Smith wrote:
> On Tue, 16 Oct 2012 13:13:41 -0700
> Devin Teske wrote:
>
>> When two files have the same inode, they are "hard links" to each other.
>> Unlike a "soft link" (or "symbolic link" as they are more appropriately
>> called), which stores a de
On Tue, 16 Oct 2012 13:13:41 -0700
Devin Teske wrote:
> When two files have the same inode, they are "hard links" to each other.
> Unlike a "soft link" (or "symbolic link" as they are more appropriately
> called), which stores a destination-path of the target, a hard link
> instead looks and acts
Kudos to Devin for his explanation!
On Tue, Oct 16, 2012 at 4:13 PM, Devin Teske wrote:
>
> On Oct 16, 2012, at 11:13 AM, Stanislav Zaharov wrote:
>
>> Hello,
>>
>> I have a question regarding the mfsroot file system organization on
>> installation cd.
>> How is it possible that we have bigger bi
On Wed, Oct 17, 2012 at 12:13 AM, Devin Teske wrote:
>
> On Oct 16, 2012, at 11:13 AM, Stanislav Zaharov wrote:
>
> Hello,
>
> I have a question regarding the mfsroot file system organization on
> installation cd.
> How is it possible that we have bigger binary files in ls list while actual
> occu
On Oct 16, 2012, at 11:13 AM, Stanislav Zaharov wrote:
> Hello,
>
> I have a question regarding the mfsroot file system organization on
> installation cd.
> How is it possible that we have bigger binary files in ls list while actual
> occupied space is less.
The beauty of crunchgen(1).
If you
On Tue, Oct 16, 2012 at 2:13 PM, Stanislav Zaharov
wrote:
> Hello,
>
> I have a question regarding the mfsroot file system organization on
> installation cd.
> How is it possible that we have bigger binary files in ls list while actual
> occupied space is less. But when we try to copy these files
