How to re-launch menuconf

Discuss the technical details of Gargoyle and ongoing development

Moderator: Moderators

Post Reply
User avatar
ericwong
Posts: 430
Joined: Sat Aug 25, 2012 6:15 am
Location: Melbourne, Australia
Contact:

How to re-launch menuconf

Post by ericwong »

Hi,

For OpenWRT, after something is manually added, to re-generate menuconfig, I figured out after many tests that I need to use

Code: Select all

make dirclean
However, I can't do the same on gargoyle. If I do it under the custom-src folder, it will cause build all sorts of errors.

Does anyone knows how I can re-launch menuconfig to change configurations? or force the system to regenerate the menuconfig?

Right now, gargoyle will launch menuconfig after command

Code: Select all

make custom
is issued..

However, if I want to rebuild the ROM and change the configurations, e.g. to add new packages or even change the target using menuconfig. Seems like it is not possible to do so, other than manually modifying the .config file in both gargoyle/target/custom/profile/config as well as gargoyle/custom-src/.config

Is there an existing command for this because I don't see anything on this in the developer documentation either?

Currently, the only work around method I have is to go to /custom-src and then type make menuconf, save the changes and then copy this config file to both gargoyle/target/custom/profile/config as well as gargoyle/custom-src/.config. Then, relaunch the build process using make custom. Or manually modify the config file directly.

I also noticed that the build will fail if I go directly into /custom-src and issue make command there. There will be an error about
gargoyle/custom-src/build_dir/linux-ramips_rt305x/linux-3.3.8/net/ipv4/netfilter/*weburl*.ko' is missing.

Code: Select all

WARNING: skipping kmod-ebtables-ipv4 -- package not selected
WARNING: skipping kmod-ebtables-watchers -- package not selected
mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/bin/ramips/packages /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/pkginfo
. /home/openwrt/openwrt/gargoyle-beta/custom-src/include/shell.sh; export modules=; add_module() { priority="$1"; mods="$2"; boot="$3"; shift 3; for mod in $mods; do if [ -e /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/lib/modules/3.3.8/$mod.ko ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules.d; echo "$mod" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules.d/$priority-nfnetlink; fi; done; if [ -e /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules.d/$priority-nfnetlink ]; then if [ "$boot" = "1" ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules-boot.d; ln -s ../modules.d/$priority-nfnetlink /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules-boot.d/; fi; modules="${modules:+$modules }$priority-nfnetlink"; fi; }; add_module "48" "nfnetlink" ""; if [ -n "$modules" ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/etc/modules.d; mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL; echo "#!/bin/sh" > /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/postinst; echo "[ -z \"\$IPKG_INSTROOT\" ] || exit 0" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/postinst; echo ". /etc/functions.sh" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/postinst; echo "load_modules $modules" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/postinst; chmod 0755 /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/postinst; fi
find /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink -name 'CVS' -o -name '.svn' -o -name '.#*' -o -name '*~'| xargs -r rm -rf
export CROSS="mipsel-openwrt-linux-uclibc-"  ; NM="mipsel-openwrt-linux-uclibc-nm" STRIP="/home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/host/bin/sstrip" STRIP_KMOD="/home/openwrt/openwrt/gargoyle-beta/custom-src/scripts/strip-kmod.sh" /home/openwrt/openwrt/gargoyle-beta/custom-src/scripts/rstrip.sh /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink
rstrip.sh: /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/lib/modules/3.3.8/nfnetlink.ko:relocatable
( echo "Package: kmod-nfnetlink"; echo "Version: 3.3.8-1"; DEPENDS='kernel (=3.3.8-1-92b7d63af023b47e9b000b7de1430143)'; for depend in kmod-ipt-core; do DEPENDS=${DEPENDS:+$DEPENDS, }${depend##+}; done; echo "Depends: $DEPENDS"; echo "Provides: "; echo "Source: package/kernel"; echo "Section: kernel"; echo "Status: unknown hold not-installed"; echo "Essential: no"; echo "Priority: optional"; echo "Maintainer: OpenWrt Developers Team <openwrt-devel@openwrt.org>"; echo "Architecture: ramips"; echo "Installed-Size: 0"; echo -n "Description: "; . /home/openwrt/openwrt/gargoyle-beta/custom-src/include/shell.sh; getvar V_Package_kmod_nfnetlink_description | sed -e 's,^[[:space:]]*, ,g'; ) > /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/control
chmod 644 /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL/control
. /home/openwrt/openwrt/gargoyle-beta/custom-src/include/shell.sh; (cd /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink/CONTROL;  )
ipkg-build -c -o 0 -g 0 /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink /home/openwrt/openwrt/gargoyle-beta/custom-src/bin/ramips/packages
Packaged contents of /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-nfnetlink into /home/openwrt/openwrt/gargoyle-beta/custom-src/bin/ramips/packages/kmod-nfnetlink_3.3.8-1_ramips.ipk
rm -rf /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink
mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/stamp /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink
. /home/openwrt/openwrt/gargoyle-beta/custom-src/include/shell.sh; export modules=; add_module() { priority="$1"; mods="$2"; boot="$3"; shift 3; for mod in $mods; do if [ -e /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/lib/modules/3.3.8/$mod.ko ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules.d; echo "$mod" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules.d/$priority-nfnetlink; fi; done; if [ -e /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules.d/$priority-nfnetlink ]; then if [ "$boot" = "1" ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules-boot.d; ln -s ../modules.d/$priority-nfnetlink /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules-boot.d/; fi; modules="${modules:+$modules }$priority-nfnetlink"; fi; }; add_module "48" "nfnetlink" ""; if [ -n "$modules" ]; then mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/etc/modules.d; mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL; echo "#!/bin/sh" > /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL/postinst; echo "[ -z \"\$IPKG_INSTROOT\" ] || exit 0" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL/postinst; echo ". /etc/functions.sh" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL/postinst; echo "load_modules $modules" >> /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL/postinst; chmod 0755 /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/CONTROL/postinst; fi
SHELL= /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/host/bin/flock /home/openwrt/openwrt/gargoyle-beta/custom-src/tmp/.root-copy.flock -c 'cp -fpR /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink/. /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/'
rm -rf /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/tmp-kmod-nfnetlink
touch /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/root-ramips/stamp/.kmod-nfnetlink_installed
mkdir -p /home/openwrt/openwrt/gargoyle-beta/custom-src/bin/ramips/packages /home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/packages/ipkg-ramips/kmod-ipt-weburl/CONTROL /home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/pkginfo
ERROR: module '/home/openwrt/openwrt/gargoyle-beta/custom-src/build_dir/linux-ramips_rt305x/linux-3.3.8/net/ipv4/netfilter/*weburl*.ko' is missing.
make[3]: *** [/home/openwrt/openwrt/gargoyle-beta/custom-src/bin/ramips/packages/kmod-ipt-weburl_3.3.8-1_ramips.ipk] Error 1
make[3]: Leaving directory `/home/openwrt/openwrt/gargoyle-beta/custom-src/package/kernel'
make[2]: *** [package/kernel/compile] Error 2
make[2]: Leaving directory `/home/openwrt/openwrt/gargoyle-beta/custom-src'
make[1]: *** [/home/openwrt/openwrt/gargoyle-beta/custom-src/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/openwrt/openwrt/gargoyle-beta/custom-src'
make: *** [world] Error 2
(took me almost a week and many build failure to figure these out... and still testing to see if this works properly)

Note: I am building on attitude_adjustment branch.

Thanks
Eric
Eric Wong

PM me if you need to buy Gargoyle router in Australia/NZ, willing to pay me to help you on your Gargoyle configurations or build custom configured ROM with pre-installed app or try to fix your bricked router. Yes, I am looking for job/work.

User avatar
ericwong
Posts: 430
Joined: Sat Aug 25, 2012 6:15 am
Location: Melbourne, Australia
Contact:

Re: How to re-launch menuconf

Post by ericwong »

Sigh... seems like there is not much help from the users/developers here...

Anyway, I finally figured out how to do this, after trying this for over a week.. In case any noob like me can't figure this out either. Do this..

Starting from scratch
1) After you have downloaded Gargoyle, issue "make custom" command.
2) After menuconfig appears, close the terminal. This makes Gargoyle download all the required sources for building.

To add/modify the OpenWRT sources
1) After Gargoyle have downloaded all the requires sources, the downloaded files are stored at /gargoyle/downloaded/
2) Make any modifications required on these files, e.g. add/remove/edit targets or packages

To relaunch the menuconfig
1) Delete the folder "custom-src"
2) Issue "make custom" again
3) Gargoyle will then copy all the sources from /gargoyle/downloaded/ to /custom-src and then launch the menuconfig
4) Select the target you want and all the Gargoyle related packages
5) Save configuration and building will start

Note: Make sure your computer is connected to the computer because there are additional files which will be downloaded from internet. If the computer is not connected to internet, you will likely see World 2 ERROR with no information on what the problem is... (Took me several builds to figured this out..)

Alternatively, if you can do some coding, instead of copying, you can let Gargoyle patch it against the downloaded Openwrt sources by putting your patch inside /gargoyle/patches-generic/
(Thanks Eric Bishop for pointing this part out via PM.)
Eric Wong

PM me if you need to buy Gargoyle router in Australia/NZ, willing to pay me to help you on your Gargoyle configurations or build custom configured ROM with pre-installed app or try to fix your bricked router. Yes, I am looking for job/work.

b4nd0ler0
Posts: 8
Joined: Tue Nov 22, 2011 8:26 am

Re: How to re-launch menuconf

Post by b4nd0ler0 »

Ericwong,

Thank you very much for documenting this. I was just going to post the same question. How about copy & paste it to a wiki page? (as we say overhere give 'em a hand a they'll take the arm ;) )

Now, two questions for you or anyone else kind enough to enlighten us, see if I can gather some more details.

I have already successfully build my first custom Gargoyle-AA image but now I find that some of the options I selected on menuconfig are not needed and also would like to modify some files so I want to rebuild ideally compiling only the changes.

Following you instructions I'd start in step 2.2 "Make any modifications required on these files" and put in my modified files, in my case in ./gargoyle/downloaded/attitude_adjustment-34210

Then onto step 3-"To relaunch the menuconfig", I'd delete custom-src, issue "make custom" and change selections in menuconfig --> will this keep my previous configuration or will I have to start from scratch?

Also, does the build script now recompile everything or only what has been changed?

Thank you.

User avatar
ericwong
Posts: 430
Joined: Sat Aug 25, 2012 6:15 am
Location: Melbourne, Australia
Contact:

Re: How to re-launch menuconf

Post by ericwong »

b4nd0ler0 wrote: Thank you very much for documenting this. I was just going to post the same question. How about copy & paste it to a wiki page? (as we say overhere give 'em a hand a they'll take the arm ;) )
Glad someone find it useful :)
Go ahead if you want to put it in the wiki.
I can't find the appropriate place to put this

Actually, there is some documentation in this page but it is not easy to read.. Very easy to miss the thing you are looking for..
http://www.gargoyle-router.com/wiki/dok ... umentation

Ideally, there should be better way to relaunch menuconfig than deleting custom-src but I don't know what the command is..
b4nd0ler0 wrote: I have already successfully build my first custom Gargoyle-AA image but now I find that some of the options I selected on menuconfig are not needed and also would like to modify some files so I want to rebuild ideally compiling only the changes.

.......

Then onto step 3-"To relaunch the menuconfig", I'd delete custom-src, issue "make custom" and change selections in menuconfig --> will this keep my previous configuration or will I have to start from scratch?
If you modify anything in menuconfig, use the "save" option and save it.. Then copy the file you saved somewhere...

If you want to relaunch menuconfig using the changes you have just made, you need to replace the gargoyle/target/custom/custom.config file.. Otherwise, it will launch menuconfig with the default configurations.

This should work but you should check it to make sure. In any case, after menuconfig is up, you can always use the load option to load the configuration you have saved earlier ;)
b4nd0ler0 wrote: Also, does the build script now recompile everything or only what has been changed?
It will recompile EVERYTHING.
That's why deleting custom-src is not the ideal method to do this because you can't do a quick recompile like what I can do with Openwrt... there must be a better way that I don't know..
Eric Wong

PM me if you need to buy Gargoyle router in Australia/NZ, willing to pay me to help you on your Gargoyle configurations or build custom configured ROM with pre-installed app or try to fix your bricked router. Yes, I am looking for job/work.

b4nd0ler0
Posts: 8
Joined: Tue Nov 22, 2011 8:26 am

Re: How to re-launch menuconf

Post by b4nd0ler0 »

It will recompile EVERYTHING.
That's why deleting custom-src is not the ideal method to do this because you can't do a quick recompile like what I can do with Openwrt... there must be a better way that I don't know..
Arrghg, that's such a pain in the proverbial, my Ubuntu virtual machine takes about 7 hours to compile Gargoyle from scratch. I suppose Gargoyle’s make script must pass some command somewhere to OpenWRT’s make indicating to force compile everything but that’s beyond my limited knowledge about the build process. Perphaps Gargoyle Eric can give a few pointers on how to approach the problem …

opav
Posts: 6
Joined: Sat Mar 02, 2013 8:47 am

Re: How to re-launch menuconf

Post by opav »

I am also quite green to compiling but instead of 'make custom', I did a 'make ar71xx.usb_no_tor' and it did build successfully.

Then I sort of follow the openwrt wiki and can now re-launch menuconfig and re-build in minutes, it complete so fast, that make me wonder if the image created will work. So maybe someone with more experience can see if these steps are ok.

So after the initial 'make ar71xx.usb_no_tor', here are the steps:

Code: Select all

cd ar71xx-src/
./scripts/feeds update
make package/symlinks
make menuconfig
make
I tried a few times just doing 'make menuconfig' + 'make' to add/remove pkgs and the build process was really fast. Next I got to build up some confidence to flash it my router.
TP-Link WR1043ND, Gargoyle 1.5.X

User avatar
ericwong
Posts: 430
Joined: Sat Aug 25, 2012 6:15 am
Location: Melbourne, Australia
Contact:

Re: How to re-launch menuconf

Post by ericwong »

opav wrote:I am also quite green to compiling but instead of 'make custom', I did a 'make ar71xx.usb_no_tor' and it did build successfully.

Then I sort of follow the openwrt wiki and can now re-launch menuconfig and re-build in minutes, it complete so fast, that make me wonder if the image created will work. So maybe someone with more experience can see if these steps are ok.

So after the initial 'make ar71xx.usb_no_tor', here are the steps:

Code: Select all

cd ar71xx-src/
./scripts/feeds update
make package/symlinks
make menuconfig
make
I tried a few times just doing 'make menuconfig' + 'make' to add/remove pkgs and the build process was really fast. Next I got to build up some confidence to flash it my router.
I tried this before, this method doesn't work correctly..
This only rebuilds the Openwrt portion but not the gargoyle portions...

Check the dates/time of your binary and you will see it didn't work.
Eric Wong

PM me if you need to buy Gargoyle router in Australia/NZ, willing to pay me to help you on your Gargoyle configurations or build custom configured ROM with pre-installed app or try to fix your bricked router. Yes, I am looking for job/work.

opav
Posts: 6
Joined: Sat Mar 02, 2013 8:47 am

Re: How to re-launch menuconf

Post by opav »

Oh I thought my first run of 'make ar71xx.usb_no_tor' would have already patched in the Gargoyle patches?

Then subsequently doing the steps I listed is enough to add/remove pkgs? Yes/no?

The bin files do get updated and binary compare do show difference between these 'fast' build.
TP-Link WR1043ND, Gargoyle 1.5.X

User avatar
ericwong
Posts: 430
Joined: Sat Aug 25, 2012 6:15 am
Location: Melbourne, Australia
Contact:

Re: How to re-launch menuconf

Post by ericwong »

opav wrote:Oh I thought my first run of 'make ar71xx.usb_no_tor' would have already patched in the Gargoyle patches?

Then subsequently doing the steps I listed is enough to add/remove pkgs? Yes/no?
NO
opav wrote: The bin files do get updated and binary compare do show difference between these 'fast' build.
You must be looking at the wrong bin folder...
There are TWO!!
One under gargoyle/ar71xx-src/bin which is NOT what you want because the gargoyle patches are not applied there.. and this is the only binary updated from your "rebuild" command.

The other is under gargoyle/bin which contains the gargoyle patches.
Eric Wong

PM me if you need to buy Gargoyle router in Australia/NZ, willing to pay me to help you on your Gargoyle configurations or build custom configured ROM with pre-installed app or try to fix your bricked router. Yes, I am looking for job/work.

opav
Posts: 6
Joined: Sat Mar 02, 2013 8:47 am

Re: How to re-launch menuconf

Post by opav »

Ok finally muster up the courage and flashed it to the router and it works!

The privoxy pkg I added is there in the usr/sbin and works. The changed ATH_USER_REGD setting also works by allowing more channels. Only the banner remain the same, still show the original date/time when I first built it with 'make ar71xx.usb_no_tor'.

But thinking of what Eric said, we probably have to take care not to change stuff that Gargoyle patches when using this fast method of building....took only 7min to add privoxy!
TP-Link WR1043ND, Gargoyle 1.5.X

Post Reply