I'm a beginner at this so please go easy on me...
After running "make menuconfig" where is the list of packages to be included stored? I noticed every package got downloaded and built, even ones I did not select in "make menuconfig". ImageBuilder uses the files under target/linux/imagebuilder/lists but I do not want to use ImageBuilder. Does a completely custom build use another file somewhere? I want to build firmware without dhcp. Later I want to include dnsmasq and after that I might want to try another dns package. Is there a file that I can easily modify to pick up these package changes when I do a custom build? If I re-run "make menuconfig" and de-select dnsmasq would that be enough? FWIW I do not like "make menuconfig". Never have, even for just building regular Linux kernels. I find it confusing. That doesn't mean I won't use it when necessary.
After running "make" I see .bin files for openwrt-wa840g, we800g, wr850g, wrt54g, wrt54gs, wrt54g3g, wrt54gs_v4 and wrtsl54gs. Squashfs and jffs2. I am only interested in building a squashfs flavor firmware for the wrt54gs. Is there a makefile target or config file somewhere that will turn off generation of all the other binaries?
Dropbear. I will always have dropbear. Always. What is the best way to preserve dropbear_rsa_host_key, dropbear_dsa_host_key and the public keys for my other boxes, authorized_keys on the target filesystem? The /etc/dropbear directory is not in the skeleton fs at packages/base-files/default. Can I just add a dropbear subdir there, put the files in it and have them get picked up for ever more?
Thanks in advance.
(Last edited by Craven on 12 Mar 2006, 03:07)