From owner-freebsd-questions@FreeBSD.ORG Wed Oct 17 09:36:58 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 57C7EF20; Wed, 17 Oct 2012 09:36:58 +0000 (UTC) (envelope-from ateve@sohara.org) Received: from uk1rly2283.eechost.net (relay01a.mail.uk1.eechost.net [217.69.40.75]) by mx1.freebsd.org (Postfix) with ESMTP id 142B48FC17; Wed, 17 Oct 2012 09:36:57 +0000 (UTC) Received: from [31.186.37.179] (helo=rpi-1.marelmo.com) by uk1rly2283.eechost.net with esmtpa (Exim 4.72) (envelope-from ) id 1TOOwZ-0002yB-Og; Wed, 17 Oct 2012 09:25:35 +0100 Received: from [192.168.63.1] (helo=steve.marelmo.com) by rpi-1.marelmo.com with smtp (Exim 4.72) (envelope-from ) id 1TOP2c-0007QR-NM; Wed, 17 Oct 2012 09:31:50 +0100 Date: Wed, 17 Oct 2012 09:30:06 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Subject: Re: MFS root filesystem and static binaries size Message-Id: <20121017093006.11ef91b99dfafdeb3f2a28ed@sohara.org> In-Reply-To: <79906B82-7EF3-44DD-95A1-EF1DD239E2CD@fisglobal.com> References: <79906B82-7EF3-44DD-95A1-EF1DD239E2CD@fisglobal.com> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Auth-Info: 15567@permanet.ie (plain) Cc: Devin Teske X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2012 09:36:58 -0000 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. -- Steve O'Hara-Smith