From owner-freebsd-current@FreeBSD.ORG  Mon Jul  5 21:51:06 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 93DDE16A4DA
	for <freebsd-current@FreeBSD.org>;
	Mon,  5 Jul 2004 21:51:06 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6742843D41
	for <freebsd-current@FreeBSD.org>;
	Mon,  5 Jul 2004 21:51:06 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i65LouOV002134;
	Mon, 5 Jul 2004 14:51:01 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200407052151.i65LouOV002134@gw.catspoiler.org>
Date: Mon, 5 Jul 2004 14:50:56 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: damaker@fillibach.de
In-Reply-To: <opsaoo8tqydvpa9u@auth.smtp.kundenserver.de>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: moving /usr to another partition
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jul 2004 21:51:06 -0000

On  5 Jul, Konstantin 'Kosta' Welke wrote:
> Hi!
> 
> Diskspace is running low, so I'd like to move my /usr to another
> disk. I was told that cp -Rv is not a good idea and i should use
> dump instead. The problem is: That disk is big and half-full and
> I don't want to empty it. Is it possible  to let restore work to
> a directory instead of a disk? Im not sure after reading the man
> page, google doesnt know either and I dont want to find out "the
> hard way". So i guessed it couldn't hurt to ask...
> 
> If you have any hints or alternatives, please let me know!

I'm pretty sure that "restore -r" will do the right thing and just
unpack the dump archive into the current working directory.  I'm pretty
sure that I've done this in the past.

I don't understand the warnings in the man page:

     -r      Restore (rebuild a file system).  The target file system should
             be made pristine with newfs(8), mounted and the user cd'd into
             the pristine file system before starting the restoration of the
             initial level 0 backup.
             [snip]
             The -r flag precludes an interac-
             tive file extraction and can be detrimental to one's health if
             not used carefully (not to mention the disk)

Restoring into a directory that already contains stuff is likely to be
harmful to the contents, but I think restoring into an empty directory
should be fine.

Anyone else care to comment?