Date: Sat, 29 Apr 2006 01:49:16 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-arch@freebsd.org, Ceri Davies <ceri@submonkey.net>, freebsd-current@freebsd.org Subject: Re: [HEADS UP] upcoming /etc/services updating Message-ID: <20060428224916.GA10513@gothmog.pc> In-Reply-To: <445298AD.7030400@freebsd.org> References: <002401c66b0a$44c230e0$01655050@jersey> <44529510.6030704@freebsd.org> <20060428222627.GI51777@submonkey.net> <445298AD.7030400@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-04-28 15:35, Colin Percival <cperciva@freebsd.org> wrote: > Ceri Davies wrote: > > Would it be wise to wait until cached is enabled by default? > > My (perhaps mistaken) impression was that cached was going to > be enabled by default soon in HEAD, and at very least long > before 7.0-RELEASE. I wasn't planning on MFCing the > /etc/services update until cached was enabled by default in > RELENG_6. > > If there's a significant reason why people running HEAD would > not want to turn cached on, I'll certainly reconsider my plans > here. I think turning it on by default will give it more visibility and testing on HEAD, so it's probably good to do so. Running CURRENT and having new features shouldn't be a very big surprise for most people I guess :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060428224916.GA10513>