Yeah it snuck back in during testing.  I've removed it and started a new batch of snapshot builds.

BTW your diagram on the BSD boot process is very useful! Scott's reply probably solves your probelm. You are right that some of the CHS boot parameters are very confusing. In addition you may find this useful.  My problem was setting up a 4 partiton BSD dev system and using an image utility to transfer between partitons. The``` bsdlabel -R ad0s1 savedlabel using the * options in fields where new values have to be calculated worked very well for me. It recalculates all of the correct parameters and re-writes to "savelabel". I cannot supply you an example because all of the label were re-witten without my knowledge.

It's not that developers ONLY work for bounties. If a developer is interested in something he probably will start working on it without a bounty. However all developers have other projects already or might personally have no need for the desired feature. A bounty is a way to raise interested or speed up developement on something specific. To quote scott "time doesn't grow on trees". There is just too much to do or to work on. On the other hand a project like pfSense needs some funding too to get testhardware, or to have some cash for hackathons. Appreciations go to all the people who have helped with this in the past.

No packages do not work on LiveCD's. Post this message on the snort forums.

HEAD is not stable. Use RELENG_1 . That will get you current snapshots.

@Nick: Is this functionality going to be incorporated into the next release of pfSense? No.  -HEAD is 2.0 with no release date set.

Hmm got an older developers iso to work (1.0-RELEASE) so I guess all is good.

I also had thos error… try http://pfsense.trendchiller.com/DISTRIBUTION/1.0.1-SNAPSHOT-01-24-2007/pfSense-Full-Update-1.0.1-SNAPSHOT-01-24-2007.tgz to fix this problem… It works  ;)

wow! what a prompt answer! thanks.

How about posting what you have and let others work on it when they can ?

Have a look at http://wiki.pfsense.com/wikka.php?wakka=pfSenseHome (developers related section at the bottom)

@k3rmit: Hi!! Thanks for the link, i did found it anyway shortly afterwards having posted here on the forum, it should be published but blame on me for not having searched thoroughly. I downloaded the last snapshot and installed it successfully. The good new is that bfe driver works, the bad that it isn't still perfect: here is the log output while bringing up the interface: bfe0: link state changed to DOWN bfe0: BUG!  Timeout waiting for bit 00000001 of register 41c to set. bfe0: link state changed to UP Now the question is: can i trust this connection?? I will obviously do the necessary tests, but i'm wondering what's the scale of the problem with this driver and how much can i risk on it. Thanks for the support!! If you still have issues you may want to post to freebsd-stable@freebsd.org mailing list for assistance.

Its been 3 days of running the dev_bootstrap.sh …. cvsup does a lot of downloading and then I get some panic and "kdb> " on the console. Is it ok to just restart the PC?  because that seems to restart the process but I dont know if I am making any progress. Any tips for a dev newbie? I have had power interruptions and isp messing up quite a lot so that is disrupting the process. The cpu is a VIA C3, 900MHz, 256 MB Ram, 40 GB hard disk. the iso I m trying right now is developers/pfSense.iso  dated   12-Jan-2007 10:53 Previously I tried using older verions of this iso. Would it be better for me to use pfSense-Developers-1.0-LiveCD-Installer.iso.gz ?

Please search. There are multiple threads covering this already.

ok, thx for the answer.

The needed code is only in the head-version (developement version of the next major version). It's not in the 1.x-series.

This won't appear in before the next MAJOR Version.

The developer iso will do all this automatically once you install and boot it up in the background.  Be patient, it takes a while.

the complete comand will be: diff -rub oldfile newfile > file.diff old file is the file u have downloaded from the pfsense cvs http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/ or from the pfsense package cvs if it is a package http://pfsense.com/cgi-bin/cvsweb.cgi/tools/packages/ new file is the oldfile + you chances file.diff is a file with in it only the chances you have made to the oldfile taken from the newfile this is the one pfsense core team want's