From owner-freebsd-stable Wed Dec 22 1:42:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3345B15474 for ; Wed, 22 Dec 1999 01:42:33 -0800 (PST) (envelope-from brad@shub-internet.org) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA07367; Wed, 22 Dec 1999 10:42:24 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <385FD807.72FC177D@home.com> References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> <385FD807.72FC177D@home.com> Date: Wed, 22 Dec 1999 10:08:42 +0100 To: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" From: Brad Knowles Subject: Re: SOFTUPDATES Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:41 PM -0500 1999/12/21, Ted Sikora wrote: > Problem is my > /tmp is on / so in the future it may be wise to make a /tmp directory. > How about linking /tmp to /usr or /var for my current setup? I wouldn't suggest that. You can't guarantee that /usr will be mounted at boot when you might need to write to /tmp, unless you put /usr on / as well. Much better would be to make /tmp a separate filesystem, either softupdates or mfs. At least that way, you could write to the /tmp mount point before /tmp is mounted, and although you'd have to be careful to clean out the mount point periodically (otherwise / could mysteriously run short on space), you'd at least be able to ensure that /tmp would be writable early in the boot process. -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message