Update Pfsense DevWiki in conformance to pfsense 2.1

Hi
I like Pfsense because it's easy to customize. But pfSense Developers Wiki is very old and doesn't conform to pfsense 2.1 . for example CoreGUI2 last edited on 2007 and ReportWidgetExample link doesn't work.
do you have any plan to update it? Ordinary users cannot do this job.

jimp

If you have a list of specific things that need attention we can look at them.

Most things on there are very infrequently accessed so they tend to get forgotten as things change/progress.

Thank you jimp.
specific things that need attention:

1- ReportWidgetExample: http://devwiki.pfsense.org/CoreGUI2
2- Screenshot: http://devwiki.pfsense.org/CoreGUI
3- UsingEclipseWithpfSense: http://devwiki.pfsense.org/UsingEclipseWithpfSense
4- I highly recommend adding "How to install new packages on developer iso" to DevelopersBootStrapAndDevIso: http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso

5- BuildTimeOptions: http://devwiki.pfsense.org/BuildTimeOptions
6- Why pfSense Sucks: http://devwiki.pfsense.org/WhypfSenseSucks

zenny

I second this proposal from amirkabir.

There needs to be a dev documentation for kernel level changes specific to pfSense 2.1 and the package compilation and deployment in pfSense 2.1.

It would be nice to have a TROUBLESHOOTING page for developers when someone gets a loop of error message during compilation of pfSense 2.1 like I discussed here: http://forum.pfsense.org/index.php/topic,61074.msg354373.html#msg354373 (still unresolved).

Thanks!

jimp

@amirkabir:

1- ReportWidgetExample: http://devwiki.pfsense.org/CoreGUI2

I don't think CoreGUI2 even exists. Nothing was in that example, nothing to update. The files referenced on the CoreGUI2 stuff don't exist, and the whole section could probably be removed. Not my area though, so I won't touch it (someone else might)

@amirkabir:

2- Screenshot: http://devwiki.pfsense.org/CoreGUI

Fixed

@amirkabir:

3- UsingEclipseWithpfSense: http://devwiki.pfsense.org/UsingEclipseWithpfSense

As the page says, it's obsolete. We don't have any specific instructions for that now. Added a link to http://devwiki.pfsense.org/PfsenseEclipseXdebugSetup instead.

@amirkabir:

4- I highly recommend adding "How to install new packages on developer iso" to DevelopersBootStrapAndDevIso: http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso

Adding packages to an ISO is not currently supported. You can build in FreeBSD binaries, but not the GUI parts. It's something that needs work in the tools repo (and packages, too). Options to do that would really be a better fit for the page below (#5)

@amirkabir:

5- BuildTimeOptions: http://devwiki.pfsense.org/BuildTimeOptions

That one could use some work, but it'll take time to do.

@amirkabir:

6- Why pfSense Sucks: http://devwiki.pfsense.org/WhypfSenseSucks

Not sure what to do about that one. It's already noted that most of the things have been fixed in 2.x on the page. And the build scripts aren't much better now, so it really is fairly accurate. It's apparently also locked so only cmb can edit it.

jimp

@zenny:

It would be nice to have a TROUBLESHOOTING page for developers when someone gets a loop of error message during compilation of pfSense 2.1 like I discussed here: http://forum.pfsense.org/index.php/topic,61074.msg354373.html#msg354373 (still unresolved).

There is already a troubleshooting section right there on that page. At the bottom.

jimp

Updated http://devwiki.pfsense.org/BuildTimeOptions with a bunch of stuff.

Thanks Jim

Hi Jim
I have new recommendations for updating PFSenseDevWiki : DevelopersBootStrapAndDevIso:

1- the CVSup service was phased out as of February 28, 2013. in stage 4 , use this command:
svn checkout svn://svn.freebsd.org/base/releng/8.3 /usr/src
in stage 2 : cd /usr/ports/devel/subversion && make depends install

2- in stage 0-a, this error occurs: s3_cbc.c: No such file , use this command first to solve the problem:
mkdir -p /usr/src/crypto/openssl/ssl

jimp

1- Yes, we're aware, but it's not phased out for RELENG_8_*. We have some code for svn already (you can export USE_SVNUP=yes in pfsense-build.conf). That won't change until we are building FreeBSD 10.x based images. No need to change yet.

2- I added that to the page

"export USE_SVNUP=yes" doesn't work….. these errors occur:

>>> Applying patches from /home/pfsense/tools/builder_scripts/../builder_scripts/conf/patchlist/patches.RELENG_8_3 please wait...No file to patch.  Skipping...
1 out of 1 hunks ignored--saving rejects to sys/contrib/altq/altq/altq_cbq.h.rej
No file to patch.  Skipping...
1 out of 1 hunks ignored--saving rejects to sys/contrib/altq/altq/altq_hfsc.h.rej
failed to apply altq_max_queues.diff
No file to patch.  Skipping...
11 out of 11 hunks ignored--saving rejects to parse.y.rej
No file to patch.  Skipping...

How SVN host can be defined?

jimp

SVN may only work with 10.x builds. I haven't looked at nor touched that code. Just use cvsup for 8.3.

eri--

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.