From owner-freebsd-questions@freebsd.org Fri Aug 25 10:49:03 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D1F5DD4C35 for ; Fri, 25 Aug 2017 10:49:03 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay11.qsc.de (mailrelay11.qsc.de [212.99.187.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB3D380BEF for ; Fri, 25 Aug 2017 10:49:02 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay11.qsc.de; Fri, 25 Aug 2017 12:48:58 +0200 Received: from r56.edvax.de (port-92-195-85-107.dynamic.qsc.de [92.195.85.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 672283C77D; Fri, 25 Aug 2017 12:48:57 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v7PAmu4n002032; Fri, 25 Aug 2017 12:48:56 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 25 Aug 2017 12:48:56 +0200 From: Polytropon To: Manish Jain Cc: "freebsd-questions@freebsd.org" , "Warren Block" Subject: Re: Anything specific to keep in mind restoring from rsync ? Message-Id: <20170825124856.a1e4436a.freebsd@edvax.de> In-Reply-To: References: <20170818074902.GA91334@gmail.com> <20170825023237.9b6b22b2.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay11.qsc.de with B84AF6A3706 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1469 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2017 10:49:03 -0000 On Fri, 25 Aug 2017 01:58:05 +0000, Manish Jain wrote: > My /rescue indeed now has all files therein as separate files (unique > inodes). If the system has any more hard links, then my box would be > hosting them as separate files. > > Is it okay if I keep using this box as-is-now (no hard links) ? The box > runs fantastically well. It should be no problem. When you do a system update, files get overwritten (unlinked) and re-instantiated, so the original hardlinks should be back in place. The key idea behind hardlinks will of course still work. A program can decide upon the value of argv[0], which is the name it is called by. For example, the programs in /rescue behave totally different depending on that name, even though it is _the same_ program whenever you execute it. This mechanism does not change when they are individual binaries. For example, I have a script in ~/bin with several symlinks pointing to it, and depending on the name, the script's behaviour changes. It's a "mass image converter" conv_, and it is called conv_png2jpg, conv_dicom2jpg, conv_gif2png and so on, and whenever I need another conv_2, I just add a new symlink. The same would work with hardlinks. A sh shell script can use `basename $0` for this decision. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...