From owner-freebsd-questions@FreeBSD.ORG Thu Oct 18 02:08:59 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED60674C; Thu, 18 Oct 2012 02:08:59 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id AFC208FC08; Thu, 18 Oct 2012 02:08:59 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.4/8.14.4) with ESMTP id q9I1dRDQ028662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 17 Oct 2012 20:39:27 -0500 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 17 Oct 2012 20:39:26 -0500 Subject: Re: MFS root filesystem and static binaries size MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: <20121017093006.11ef91b99dfafdeb3f2a28ed@sohara.org> Date: Wed, 17 Oct 2012 18:39:23 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: <2A51EF1B-7274-439B-AF9D-AB116F9B4583@fisglobal.com> References: <79906B82-7EF3-44DD-95A1-EF1DD239E2CD@fisglobal.com> <20121017093006.11ef91b99dfafdeb3f2a28ed@sohara.org> To: "Steve O'Hara-Smith" X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.431, 0.0.0000 definitions=2012-10-17_05:2012-10-17,2012-10-17,1970-01-01 signatures=0 Cc: Devin Teske , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2012 02:09:00 -0000 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: >=20 >> 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. >=20 > 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. >=20 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. --=20 Devin _____________ 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.