You can't use php-fpm like that, as there is no way to post fcgi requests to the php-fpm management process without a fcgi client. And the php-fpm worker processes aren't going todo much if the management process isn't sending them jobs. And writing a php server app which pushing request handling into threads is really a bad idea considering I wouldn't trust the php-interpreter to be properly threadsafe never mind any extensions that may need to be used.

Very good idea

Just been having the same issue with lcdproc-dev. Worked fine until I tried to restart is, which makes me think it's the services menu that's messing it up. I removed the dos line endings, and from the command line the script worked, but then tried to restart the service from the GUI and the script got corrupted again. Having uninstalled and re-installed the package afresh I now find this behaviour is cured. One of those bugs that vanish when you stare at it long enough!!! Steve

In some places it may use the NIC's name to ensure it is compatible with other subsystems such as traffic shaping, VLANs, and so on. We designed it so that you do not need to know or care what the actual NIC names are post-install. What you're trying to do, as I said, will most likely break more than you believe it will help. Just leave it as it was.

You can also use the following in the theme's all.css: .ra1, .ra2, .ra3, .ra4 { background-color:#e2e2e2 !important; } and have it only change the border for that specific theme.

is it possible to pre-compile the packages to the iso?

Actually that needs to be fixed for 2.1 ++ since it was used with the old version of the ports tree.

If you create a cvsup server and a git repository on your server(s) than you can run it offline.

export PFSENSETAG=HEAD That will get you master, not RELENG_2_1 It appears that the script is wrong for that tag, though it hasn't been changed in a while. If you change PFSENSETAG from HEAD to RELENG_2_1 it will do what you want.

You need to define the cvsup host as well when you define USE_SVNUP basically it gives the host to use to svnup. From experience its not he most reliant software but works most of the time.

Since I do not use any display managers like gdm/kdm/xdm etc., that is not in my case. I directly boot into xserver using startx command. No display managers are active. I use i3 as desktop environment (i3-wm.org) with free OSes, fyi.

UPDATE: Running './build_pfPorts.sh b43-fwcutter' solved the problem. However this ./build_iso.sh failed to build iso (just memstick images were built) and the memstick image has the same kernel panic as stated in my above posts. :-( ) Now, I am getting the following error during ./build_pfPorts.sh File not found b43-fwcutter /usr/ports/sysutils/b43-fwcutter /usr/local/bin/b43-fwcutter - /usr/local/bin/b43-fwcutter Building athstats…main.c: In function 'getfmt': main.c:73: warning: implicit declaration of function 'strcasecmp' Done! Building tools/crytpo...Done! I checked with whether b43-fwcutter is available and it is there: dev# ls -lah /usr/ports/sysutils/b43-fwcutter/ total 32 drwxr-xr-x    3 root  wheel  512B Aug 22 19:01 . drwxr-xr-x  1078 root  wheel    21k Aug 22 19:04 .. -rw-r–r--    1 root  wheel  428B Aug 22 19:01 Makefile -rw-r--r--    1 root  wheel  141B Aug 22 19:01 distinfo drwxr-xr-x    2 root  wheel  512B Aug 22 19:01 files -rw-r--r--    1 root  wheel  113B Aug 22 19:01 pkg-descr Did anyone encouter something like this?

It cleans up old remnants of patches (e.g. .orig, .rej files) and similar things. You can build an iso right after, though I normally run this first: ./update_git_repos.sh && ./clean_build.sh && ./apply_kernel_patches.sh

It is safest to make a stock image first, test it, and make sure you have everything working. Then make changes. Otherwise you don't know if something went wrong because of your changes, or because of the builder in general. There was just a recent thread where I explained the various ways to tweak the kernel options (e.g. EXTRA_OPTIONS in pfsense-build.conf) and I updated the doc here: http://devwiki.pfsense.org/BuildTimeOptions What you want to do can be accomplished by just adding one line to your pfsense-build.conf once you have made a good ISO. I mentioned the path to the resulting kernels in a previous post in this thread already.

RELENG_8_3 is an errata branch, which can get updates from time to time. It must always check to make sure they are completely current and stock before starting. So it doesn't matter if you already have them, it will still check for updates and revert any local alterations to that tree before it starts so it's back to a stock FreeBSD base, ready for our patches to apply.

No. I wouldn't expect a fix until closer to 2.2, if then.

Build? Maybe. Work? Probably not. The work on 9.x was abandoned. Even if it built, the patches would be old/out of date, mostly left in case we decided to pick it up again. The work on 10.x is still in progress. I don't believe it builds/works yet. That probably won't be good/stable until a lot farther into the 2.2 development cycle.

The code is updated from git on every builder run, nothing to manually do there. Not sure why they weren't showing before as the code was there/in place… shrug It works now, not going to worry about it. :-)

They haven't been touched by anyone in a long time, they likely do not work with 2.1