Date: Wed, 14 Sep 2005 04:57:03 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/conf kern.post.mk Message-ID: <20050913185703.GA40237@cirb503493.alcatel.com.au> In-Reply-To: <20050913125820.GA10663@FreeBSD.org> References: <20050911002229.51F4916A471@hub.freebsd.org> <432382BC.5080105@root.org> <200509110310.36423@harrymail> <43255152.3000609@freebsd.org> <20050912165518.GA94181@dragon.NUXI.org> <20050913125820.GA10663@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2005-Sep-13 12:58:20 +0000, Alexey Dokuchaev wrote: >AFAIK, we still do not turn softupdates on /, but do on other >partitions. With your proposed idea, softupdates should be on on /. >How safe is this today? Quite safe. When running softupdates, freed disk space is not returned to the free list for 30-60 seconds. Since install(1) deletes the existing target files rather than over-writing them, this means that a larger pool of free space is required when doing installworld with a softupdates target. With the old 128MB (or less) root partition, there may not have been sufficient free space so softupdates was disabled by default. With the new 512MB root or the proposed multi-GB /+/usr+/var there is unlikely to be a shortage of free space so it would be quite safe to enable softupdates. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050913185703.GA40237>