From owner-freebsd-hubs Mon Jan 22 17:36:48 2001 Delivered-To: freebsd-hubs@freebsd.org Received: from basm.cerias.purdue.edu (basm.cerias.purdue.edu [128.10.243.21]) by hub.freebsd.org (Postfix) with ESMTP id 16D7437B400 for ; Mon, 22 Jan 2001 17:36:31 -0800 (PST) Received: from localhost (raj@localhost) by basm.cerias.purdue.edu (8.9.3+Sun/8.9.3) with ESMTP id UAA07110 for ; Mon, 22 Jan 2001 20:36:30 -0500 (EST) Date: Mon, 22 Jan 2001 20:36:30 -0500 (EST) From: Brian Poole To: Subject: Re: using loopback mounts... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 23 Jan 2001, jason andrade wrote: > no.. i loopback mount an ISO, copy the data out to the place it should be > and then rsync over the top to fix any oddities. then i unmount the ISO > image. Ahhhh, that makes a bit more sense. Can't say I really looked at it like that. Don't have worries about how much data I am transferring here. It probably indeed does make a bit more sense if you are charged by data transferred. > per ISO, this saves about 650M of downloaded traffic. for a distro like > redhat, that can be 3G. for freebsd, less so. nod.. I was reading the way he meant to use loopback as eliminating files being stored twice, not to save data transfer. > heh.. sorry, just a pine-ism. everyone seems to do it. If everyone was jumping off a bridge.. ;) It is just rather annoying to get dupes (don't have a dupe filter in my procmail atm ;/). -b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message