From owner-freebsd-ports  Tue Oct 28 18:22:57 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA11113
          for ports-outgoing; Tue, 28 Oct 1997 18:22:57 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from silvia.HIP.Berkeley.EDU (wck-ca6-01.ix.netcom.com [199.35.213.193])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11098
          for <ports@FreeBSD.ORG>; Tue, 28 Oct 1997 18:22:49 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id SAA03017; Tue, 28 Oct 1997 18:22:42 -0800 (PST)
Date: Tue, 28 Oct 1997 18:22:42 -0800 (PST)
Message-Id: <199710290222.SAA03017@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: ports@FreeBSD.ORG
In-reply-to: <22097.878091185@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: /compat -> /usr/local/compat
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Just don't forget that sysinstall has already been creating and
 * linking it in as /usr/compat since 2.2.2 at least. :-)

/usr/compat?  Eek.  That may fill up some people's /usr's pretty quick
(it's over 15MB now, and with new versions coming out every couple of
months...).

I guess we can stick in a check to linux_lib to warn the user.  Or
even move it over if /usr/compat already exists and is populated.

Satoshi