From make menuconfig Base-System>Busybox>Configuration>Networking Utilities I disabled httpd. When I ran make, it errors out because etc/init.d/httpd could not be removed (since my config of busybox did not have it.)
To Resolve I:
1. mkdir -p kamikaze-8.09-src/files/etc/init.d
2. touch kamikaze-8.09-src/files/etc/init.d/httpd
Router WL500W
Did not use full-build-809.sh, instead manually ran the netfilter patch scripts.
base config file used was from targets-8.09/brcm-2.4/
If I had used targets-8.09/custom/.config as my base config file it may not have given the error.
Suggestion in the config files instead of removing etc/init.d/httpd would it be better to simply disable busybox's httpd and if the user wants to enable it set busybox.conf to use port 81
etc/init.d/httpd not found
Moderator: Moderators
Re: etc/init.d/httpd not found
Err.. that's what the build configuration does already. Right now my scripts don't remove the default busybox httpd but just disable it.
-
- Posts: 8
- Joined: Fri Jul 10, 2009 9:00 pm
Re: etc/init.d/httpd not found
I'm Not sure I understand.
If it is the latter do all of them do that or all but custom?
Thats what the Default openwrt build configuration does, or thats what Gargoyle's default build config files do?Eric wrote:Err.. that's what the build configuration does already. Right now my scripts don't remove the default busybox httpd but just disable it.
If it is the latter do all of them do that or all but custom?
Re: etc/init.d/httpd not found
OpenWrt scripts, by default leave busybox httpd active. All Gargoyle builds, including custom, disable the default busybox httpd but do not delete it. The assumption is that if you're building Gargoyle you want to use httpd_gargoyle, even if you customize the configuration. It's easy to re-enable busybox httpd later if you want to though.