On Fri, 2004-05-28 at 16:18 -0700, Joshua Kwan wrote: > Ah, okay. Yes, my WC has some changes that copy the dhclient.conf file > into /target for the prebaseconfig script. > > Actually the reason why that hasn't been committed is because I removed > all the silly di_system_prebaseconfig_append calls and created a static > prebaseconfig script that just goes: > > for file in /etc/network/interfaces /etc/hostname .... /etc/dhclient.conf; do > rm -f /target/$file > cp $file /target/$file > done > > I don't see the sense of generating it on the fly. Can anyone tell me > why we've been doing it that way for ages now?
It seems to me that the most flexible thing to do would be to generate confiles like these from templates filled in with the debconf variable values. What if a local admin could supply custom templates for some of that stuff? It could potentially be very powerful... Especially if the debconf data came from a central server and could contain keys defined locally, and then the templates could contain references to those keys, and your script would obligingly fill them in along with the just-asked parts. -- Karl Hegbloom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
