From owner-freebsd-ports@FreeBSD.ORG  Wed Jul 14 06:53:04 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7AE0716A4CE; Wed, 14 Jul 2004 06:53:04 +0000 (GMT)
Received: from viefep14-int.chello.at (viefep14-int.chello.at [213.46.255.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E747F43D49; Wed, 14 Jul 2004 06:53:02 +0000 (GMT)
	(envelope-from christoph.bodner@chello.at)
Received: from [192.168.0.7] (really [80.109.142.98])
          by viefep14-int.chello.at
          (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP
          id <20040714065301.ZMNQ2514.viefep14-int.chello.at@[192.168.0.7]>;
          Wed, 14 Jul 2004 08:53:01 +0200
Mime-Version: 1.0 (Apple Message framework v618)
To: ale@FreeBSD.org
Message-Id: <71A4E938-D562-11D8-83F0-000A958EC5D6@chello.at>
From: Christoph Bodner <christoph.bodner@chello.at>
Date: Wed, 14 Jul 2004 08:52:59 +0200
X-Mailer: Apple Mail (2.618)
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
cc: ports@FreeBSD.org
Subject: FreeBSD Port: mysql-server-4.0.20
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2004 06:53:04 -0000

Dear package-maintainers of the MySQL-server!

I would like to inform you of a potential problem when using 
"/var/db/mysql" as the data folder. Usually in a standard installation, 
during slicing and partitioning the disk layout, "/var" belongs to 
partition "e", which is, e.g.,  only 256 MB large as opposed to 
partition "g" which can hold  many GigaBytes. The folllowing listing is 
a "df" output of my server:

Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ar0s1a    128990    47748    70924    40%    /
/dev/ar0s1f    257998        8   237352     0%    /tmp
/dev/ar0s1g  77123102 27117646 43835608    38%    /usr
/dev/ar0s1e    257998     1034   236326     0%    /var
procfs              4        4        0   100%    /proc

Therefore, I am forced to reconfigure this for a real-world-mission 
where MySQL tables require much more space than reservered for 
partition "e". Maybe, "/usr/home/mysql" or "/usr/local/mysql" would be 
a better location for the data dictionary of MySQL.

Kind regards,

Christoph Bodner
Innsbruck (Austria)