Date: Fri, 3 Aug 2001 00:10:54 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Robert Watson <rwatson@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall config.c menus.c sysinstall.h Message-ID: <20010803001054.B3285@nagual.pp.ru> In-Reply-To: <Pine.NEB.3.96L.1010802144705.73113A-100000@fledge.watson.org> References: <20010802202230.A706@nagual.pp.ru> <Pine.NEB.3.96L.1010802144705.73113A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 02, 2001 at 14:48:37 -0400, Robert Watson wrote: > Out of curiosity, what is the rational for postponing the changes to > /etc/ttys done during console configuration? Most other parts of > sysinstall that modify files other than rc.conf (such as /etc/exports, > password file, etc) apply their changes immediately. If all options > committed changes immediately, then there would be no cache coherency > problem possible, as the user of the editor would always see the most > recent version. This is what I meant above by always applying changes. I mean console configuration section, there are all changes postponed because they are rc.conf variables. So, if they are postponed, they are remembered, so user can change them several times without real write each time. Unnecessary write action on each very small issue like menu choice is superflous and on floppy based sysinstall is even big time waste. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010803001054.B3285>