From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 01:33:27 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65901DA5 for ; Sat, 17 Jan 2015 01:33:27 +0000 (UTC) Received: from hosting.weyantenterprises.com (hosting.weyantenterprises.com [50.28.102.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42A25DE6 for ; Sat, 17 Jan 2015 01:33:26 +0000 (UTC) Received: from [178.219.244.143] (port=49697 helo=a-1electricinc.com) by hosting.weyantenterprises.com with esmtpa (Exim 4.84) (envelope-from ) id 1YCIGT-00009t-5g; Fri, 16 Jan 2015 17:33:25 -0800 Message-ID: From: "Joe Nosay" To: "freebsd current" , "neurotic be still" , "vps freebsd" Subject: =?ISO-8859-1?Q?1=2F17=2F2015_2=3A33=3A23_AM?= Date: Fri, 17 Jan 2015 02:33:23 +0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3522.110 X-MIMEOLE: Produced By Microsoft MimeOLE V16.4.3522.110 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hosting.weyantenterprises.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gmail.com X-Get-Message-Sender-Via: hosting.weyantenterprises.com: authenticated_id: manuel@a-1electricinc.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 01:33:27 -0000 http://bestsolutionroofing.com/mz/yxeakxokrkexzjpivfejou.wmmrrtknexcesb Joe Nosay 1/17/2015 2:33:23 AM From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 12:06:38 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EB900761 for ; Sat, 17 Jan 2015 12:06:38 +0000 (UTC) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A705AF12 for ; Sat, 17 Jan 2015 12:06:38 +0000 (UTC) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1YCS9C-0001Ru-1W for current@freebsd.org; Sat, 17 Jan 2015 13:06:34 +0100 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1YCS9C-0006qm-17 for current@freebsd.org; Sat, 17 Jan 2015 13:06:34 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); for ; Sat, 17 Jan 2015 12:06:34 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "current" Subject: "make distribution," but more than one filesystem at destination? Date: Sat, 17 Jan 2015 04:06:34 -0800 (PST) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 12:06:39 -0000 UPDATING from what I have read does not go into detail in the case that the= destination has separate /var etc partitions. A variable to set, or procedure, or one should rsync the c= ontents onto the filesystems after install? Experiences welcomed. Also maybe into the UPDATING file(s) [ usual one; v1= 1 one...] ... unless it is not recommended.=