From owner-freebsd-stable Fri Sep 29 7:29:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from diskfarm.firehouse.net (rdu25-12-043.nc.rr.com [24.25.12.43]) by hub.freebsd.org (Postfix) with ESMTP id 4599637B423 for ; Fri, 29 Sep 2000 07:29:48 -0700 (PDT) Received: (from abc@localhost) by diskfarm.firehouse.net (8.9.3/8.9.3) id KAA18311; Fri, 29 Sep 2000 10:30:49 -0400 (EDT) (envelope-from abc) Date: Fri, 29 Sep 2000 10:30:49 -0400 From: Alan Clegg To: Michel Talon Cc: stable@FreeBSD.ORG Subject: Re: Space Message-ID: <20000929103049.D16250@diskfarm.firehouse.net> References: <200009281759.e8SHx2573258@voyager.bxscience.edu> <20000929095501.A474@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000929095501.A474@lpthe.jussieu.fr>; from michel@lpthe.jussieu.fr on Fri, Sep 29, 2000 at 09:55:01AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless the network is lying to me again, Michel Talon said: > This points once more that > partionning / is a bad decision for a lot of people. I have never encountered > any problem with a big flat /. On the machine with its own /tmp /var etc. > i am continuously bothered with file system fulls. Sorry, but no. This points to a system administrator that does not understand what type of disk space is going to be required by the system that he is running. Creating a monolithic slash filesystem is insane for any number of reasons, none of which I'll go into at this point. AlanC {been at this *WAY* too long to even consider a "big flat /"} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message