From owner-freebsd-questions@FreeBSD.ORG Tue Sep 21 16:36:12 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8EB016A4CE for ; Tue, 21 Sep 2004 16:36:12 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9F5443D39 for ; Tue, 21 Sep 2004 16:36:12 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 18475 invoked from network); 21 Sep 2004 16:36:12 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.no-ip.com) ([66.92.78.145]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Sep 2004 16:36:11 -0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 8AC8FE; Tue, 21 Sep 2004 12:36:11 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Jerry McAllister References: <200409211506.i8LF67c05158@clunix.cl.msu.edu> From: Lowell Gilbert Date: 21 Sep 2004 12:36:11 -0400 In-Reply-To: <200409211506.i8LF67c05158@clunix.cl.msu.edu> Message-ID: <44d60f4m10.fsf@be-well.ilk.org> Lines: 12 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: SCSI Shock Advice ! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 16:36:13 -0000 Jerry McAllister writes: > By the way, I notice that in the FAQ on moving to a "huge disk" > it uses the 'x' switch on the restore and I think it is more > appropriate to use 'r'. So, 'restore rf -' as I indicate in > my post instead of 'restore xf -' as in the faq. > Actually, it might work either way, but I think 'r' is more correct. It will, indeed, work either way, but the "r" flag will do a newfs. Because the example had already done a newfs, this is redundant (and wipees out any special parameters you may have used in the original newfs invocation).