Ok, but is there a date when RC3 could be expected? If it's close, then probably it would be better for me to wait a couple of days than to put in production the older version.
Thank you, Roberto Holger Bauer wrote: > There have been some hundred codechanges form RC2 to the recent snaps ( see > http://cvstrac.pfsense.com/timeline ). RC2 actually is several weeks old now > and we are very close to RC3 (RC2 is dated in CVS 1st of august). As we only > fix bugs in the releng_1 codetree you can consider every new snapshot more > stable or including less bugs then a previous version. If you are > encountering problems of some sort you always should try to reproduce them > with the latest snapshot as they might be fixed already and why should we > look into problems just to find out "ah, that was fixed several weeks ago or > was related to a bug that was fixed weeks ago". > > Holger > > -----Original Message----- > From: Roberto Greiner [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 27, 2006 2:09 PM > To: [email protected] > Subject: Re: [pfSense Support] kernel panic on 1.0RC2 > > > Sorry to get into this post, but there is something bugging me here. > > I'm about to put into production a new server running the latest version of > pfSense available at the page, which is rc2. Now, I'm seeing that if that > version gives problems it won't be supported because it's old, and I'm > supposed to use a daily snapshot instead????? > > Roberto > > > Holger Bauer wrote: > Please upgrade to a most recent version: > http://pfsense.com/~sullrich/1.0-SNAPSHOT-09-26-06/ > We won't check for errors if they are not reported using the latest version. > RC2 is quite old. > > Holger > > > -----Original Message----- > From: Rob Evers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 27, 2006 9:37 AM > To: [email protected] > Subject: [pfSense Support] kernel panic on 1.0RC2 > > > Hi All, > > I have a strange problem on my firewall cluster, when I remove a carp > address the firewall node locks up (repeatable), the machine is left > with a panic message on the console, and can only be brought back to > life with a reboot. After the reboot everything seems fine > and the CARP > address is removed. I have no idea how to debug this so can any of you > give me pointers ? > > Attached is the output of the last dmesg > The network card where the CARP address was configured is > using the ste > driver and is a 4-port D-link network adapter. > The machines used are Dell PE2850 single processor HTT enabled. > > More information can be provided if necessary. > > TIA! > Rob Evers > > -- ------------------------------------------------------------------- | Marcos Roberto Greiner | | | | Os otimistas acham que estamos no melhor dos mundos | | Os pessimistas tem medo de que isto seja verdade | | Murphy | ------------------------------------------------------------------- | [EMAIL PROTECTED] | ------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
