Date: Fri, 2 Dec 2011 10:44:11 +0100 From: Joel Dahl <joel@FreeBSD.org> To: Ken Smith <kensmith@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r228192 - head/usr.sbin/bsdinstall/scripts Message-ID: <20111202094411.GJ23987@goofy01.vnodelab.local> In-Reply-To: <201112020038.pB20cmt6068628@svn.freebsd.org> References: <201112020038.pB20cmt6068628@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02-12-2011 0:38, Ken Smith wrote: > Author: kensmith > Date: Fri Dec 2 00:38:47 2011 > New Revision: 228192 > URL: http://svn.freebsd.org/changeset/base/228192 > > Log: > Add a screen that asks if the user would like to enable crash dumps, > giving them a very brief description of the trade-offs. Whether the > user opts in or out add an entry to what will become /etc/rc.conf > explaining what dumpdev is and how to turn on/off crash dumps. The folks > who handle interacting with users submitting PRs have asked for this. Hmm. Two things I'd like to bring up: * Not specifically aimed at this commit, but my recommendation would be that we keep bsdinstall as simple as possible: installing FreeBSD should require a minimum amount of keystrokes. I realise this is just one more screen, but I hope we don't turn bsdinstall into a configuration utility where you can disable/enable just about anything in rc.conf. * Mentioning future system crashes during installation feels awkward. Is that really what we want? I understand the problem and how this helps us with debugging, but this is like saying to users that what they are installing is unstable and that it'll eventuelly crash and die. I know we discussed ways of making crash dumps smarter in order to not fill up /var, which in turn would allow us to always have it on. Maybe that is the right path? -- Joel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111202094411.GJ23987>