From owner-freebsd-questions@FreeBSD.ORG Sun May 31 09:15:33 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2933A1065672 for ; Sun, 31 May 2009 09:15:33 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 47A2C8FC1D for ; Sun, 31 May 2009 09:15:31 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n4V9FMQ6023533; Sun, 31 May 2009 11:15:22 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n4V9FJiv023530; Sun, 31 May 2009 11:15:21 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 31 May 2009 11:15:19 +0200 (CEST) From: Wojciech Puchar To: Matthew Seaman In-Reply-To: <4A2248AB.3060907@infracaninophile.co.uk> Message-ID: References: <20090530213535.f117d3a3.freebsd@edvax.de> <4ad871310905301555k68cb3acekb488852142bd02aa@mail.gmail.com> <20090531012203.ac9e5f67.freebsd@edvax.de> <4A2248AB.3060907@infracaninophile.co.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Glen Barber , Polytropon , "freebsd-questions@freebsd.org" Subject: Re: Deinstall software X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 09:15:33 -0000 > In fact, given that FreeBSD doesn't seem to have a native convention on > how exported filesystems are laid out (no mention in hier(7), no default > /etc/exports file), it would make sense to adopt the Solaris/Linux style > where > feasible. it's best not to adopt any style, but do whatever is optimal in certain case. You propose just another example of "blind repeated rule". Your idea won't hurt in single-disk, single-partition case, but this case is prohibited by other "blind repeat" rule of making lots of partitions. What if i want export things from multiple disks? just make one another separete partition on each disk for /export/something just to make system config look "nice" or "professional" because it's good to have NFS exported things to stay in /export Such practices gives only illusion or cleanliness and order, actually giving exactly opposite. Actually one ZFS adventage grown on this - it allows you to make millions of "partitions" without actually creating them, because it's all still stored in one pool. But those who feel configuration with a lots of partitions "cleanness and order" are happy now. I see this as just a pure mess, not an order.