Alberto Bursi <alberto.bu...@outlook.it> wrote: > > > On 10/03/2016 03:26 PM, Karl Palsson wrote: > > What's the "new" way of doing this? In the past, in OpenWrt CC > > and before, a package could install files like /etc/banner and > > /etc/inittab that were provided by the base-files package. It was > > always listed as "unreliable" as apparently you couldn't rely on > > the order. In practice it actually worked just fine. > > > > What's the currently accepted mechanism for including replacement > > files in a custom build? > > > > Sincerely, > > Karl Palsson > > > > What I've found so far for my own project is that a script in > /files/etc/uci-defaults folder in source folder should work. > Anyway scripts in /etc/uci-defaults (from any source) are > called on first boot and apply configuration changes on device, > just look at the ones you have already there in the rootfs. >
You're absolutely correct, that way _works_ but it's pointlessly redundant to ship files just so that I can make the bootup process take longer while it "finishes" replacing files that I knew from the outset I never wanted. It also means that until _my_ uci-defaults file runs, (depends on everyone else) I still have the old original files in place. uci-defaults is a great mechanism for many things, but i really don't feel it's appropriate for everything. Sincerely, Karl Palsson
signature.asc
Description: OpenPGP Digital Signature
_______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
