From owner-freebsd-stable Tue Dec 21 12:39:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9421114FF2 for ; Tue, 21 Dec 1999 12:39:28 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40333>; Wed, 22 Dec 1999 07:30:27 +1100 Content-return: prohibited Date: Wed, 22 Dec 1999 07:39:11 +1100 From: Peter Jeremy Subject: Re: SOFTUPDATES In-reply-to: <385FD807.72FC177D@home.com>; from tsikora@home.com on Wed, Dec 22, 1999 at 06:41:59AM +1100 To: tsikora@powerusersbbs.com Cc: freebsd-stable@FreeBSD.ORG Message-Id: <99Dec22.073027est.40333@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> <385FD807.72FC177D@home.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-22 06:41:59 +1100, Ted Sikora wrote: > So from what I read softupdates on /tmp will also speed things >up quite a bit and / is not really necassary. Yes. >How about linking /tmp to /usr or /var for my current setup? Linking /tmp into /var is probably more reasonable than /usr (/ and /usr should both be `write-rarely' filesystems). Note that some Unices have exploits which rely on hard-links to system files, so it is good general practice not to allow world-writable directories in / or /usr. If you do this, it is probably a good idea to create the same directory in the root filesystem - so you have an accessible /tmp with only the root FS mounted (the extra directory will be hidden when /var is mounted). If you have sufficient RAM or swap, MFS is another option for /tmp. (And if /tmp is in a partition by itself, you should get marginally better performance by making it async instead of using softupdates). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message