Date: Wed, 22 Dec 1999 07:39:11 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: tsikora@powerusersbbs.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SOFTUPDATES Message-ID: <99Dec22.073027est.40333@border.alcanet.com.au> In-Reply-To: <385FD807.72FC177D@home.com>; from tsikora@home.com on Wed, Dec 22, 1999 at 06:41:59AM %2B1100 References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> <385FD807.72FC177D@home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Dec-22 06:41:59 +1100, Ted Sikora <tsikora@home.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Dec22.073027est.40333>