Date: Sun, 22 Dec 2002 17:21:26 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Mike Makonnen <mtm@identd.net> Cc: jake@locore.ca, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc rc.diskless1 Message-ID: <200212230121.gBN1LQiE033921@apollo.backplane.com> References: <20021222134047.51723c7c.mtm@identd.net> <200212222226.gBMMQQSu033211@apollo.backplane.com> <20021223005643.GA34206@matrix.identd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
:Right. : :I also forgot to mention that you will still get leakage from the :server rc.conf because it is pulled in before the rc.d loop to :figure out whether it should use rcNG or not. But this is only :temporary, untill the old rc scripts are killed. : :Cheers. :--=20 :Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc Hmm. I think that could simply be run in a subshell as a test_rc_ng procedure. I'll come up with a patch for that. The only reason I missed it in testing was because I removed /etc/ipfw.conf and that obscured the fact that my diskless box was still using the server's rc.conf(!). What is this for? # Diskless setups have to depend on a different mechanism since # their config files haven't been retargeted yet. # [ -e /.rcng_yes ] && rc_ng="YES" Can that be removed? It looks like some kind of debugging thing. If it is specific to diskless configurations we can remove it because even a diskless configuration needs to use whatever rc mechanism has been installed on the server. If the server has RCNG support then rc_ng will be "YES" anyway due to /etc/defaults/rc.conf. -Matt 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?200212230121.gBN1LQiE033921>