Date: Thu, 2 Aug 2001 14:48:37 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: "Andrey A. Chernov" <ache@nagual.pp.ru> 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: <Pine.NEB.3.96L.1010802144705.73113A-100000@fledge.watson.org> In-Reply-To: <20010802202230.A706@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Aug 2001, Andrey A. Chernov wrote: > On Thu, Aug 02, 2001 at 09:24:14 -0400, Robert Watson wrote: > > ttys, it is true. It's not clear to me what the best way to account for > > this is--perhaps to apply ttys changes immediately during console > > configuration, > > I don't think it will be good - all other configuration options postponed > and applied only on exit, so better not be different here. > > > or perhaps simply to note in the dialog that pops up before > > editing /etc/ttys that some changes will be applied later as part of > > console configuration. > > Instead of popup box my configTtys() can be called in yet another place > and do the changes _before_ starting editor on /etc/ttys. 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. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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?Pine.NEB.3.96L.1010802144705.73113A-100000>