Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Oct 2012 18:39:23 -0700
From:      Devin Teske <>
To:        "Steve O'Hara-Smith" <>
Cc:        Devin Teske <>,
Subject:   Re: MFS root filesystem and static binaries size
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

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 destination-path of the target, a hard link
>> instead looks and acts no different than the original in every way.
> 	A better way of thinking about it (ie. closer to reality) is that
> the inode entry is the file. When two directory entries both have the same
> inode number in them they refer to the same file. Crunchgen produces a
> file  with a lot of names.

For clarity/record, crunchgen(1) itself does not generate the links.

You technically don't have to link to boot_crunch at all, for example:

/stand/boot_crunch ls

Another example:

/rescue/rescue vi

HINT: /rescue/rescue is also a crunchgen(1)-produced binary, just like /sta=
nd/boot_crunch in the mfsroot.

The information contained in this message is proprietary and/or confidentia=
l. If you are not the intended recipient, please: (i) delete the message an=
d all copies; (ii) do not disclose, distribute or use the message in any ma=
nner; and (iii) notify the sender immediately. In addition, please be aware=
 that any message addressed to our domain is subject to archiving and revie=
w by persons other than the intended recipient. Thank you.

Want to link to this message? Use this URL: <>