fast rate of major FreeBSD releases to STABLE

[Chris]

On 19/05/07, Marc G. Fournier <freebsd at hub.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> - --On Saturday, May 19, 2007 01:22:40 -0700 KAYVEN RIESE <kayve at sfsu.edu> wrote:
>
> >
> >
> > On Thu, 17 May 2007, linimon at lonesome.com (Mark Linimon) wrote:
> >
> >> On Thu, May 17, 2007 at 01:35:10PM -0500, Craig Boston wrote:
> >>
> >> The alternative would have been to commit what we had and _then_ found
> >> out all the bugs in the upgrade process (note: you won't be able to just
> >> blindly use portupgrade -af; you will need to read the UPDATING file for
> >> the proper procedure.  This is the unusual case of being such a sweeping
> >> change that the port management tools are not completely up to the task.)
> >
> > okay could this freeze an explanation for the fact that my x is totally
> > hosed?  i know any random joe can't necessarily answer that.. but assuming
> > it is true..
>
> Not sure how ... since the freeze started, I haven't seen any commits to the X
> system go through, or anything else for that matter (sorry, except for one port
> that I can't recall its name) ... I know in my case, I'm looking forward to the
> freeze being lifted since there was a recent release of new versions of PHP ...
> :)
>
> > how long is this freeze going to last then?
>
> Not 100% certain, but Kris just posted a note about the X stuff bbeing
> committed, so I'm guessing RSN ...
>
> - ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy at hub.org                              MSN . scrappy at hub.org
> Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (FreeBSD)
>
> iD8DBQFGTxzN4QvfyHIvDvMRAkIqAKDAV3YQkNPIS8+XXtM13dpA7CQybgCbBhUK
> rxDqsrCVzL9DFQ+lLpCrSRs=
> =ur1s
> -----END PGP SIGNATURE-----
>
>
Hi thanks for all the time spent on responses and it been civil.

I have checked and I think my comments about the times of STABLE major
releases is inaccurate and based on percieved memory rather then facts
I apologise for that, I do hope tho ports will continue to work on 6.x
a while after 7.x released.

regarding network bugs in 6.x, generally its stable, the nfs problems
were mainly fixed in 6.2 the issue comes under circumstances where the
network load is higher then the typical situation ie. a DDOS attack.
I would expect under a hevay attack for the server to go offline which
is fine, but I wouldnt expect the server to deadlock and need a reboot
as a result of a DDOS attack especially a small/medium attack, on 4.x
and even 5.x to a limited extenct the machine could cope with a fairly
high pps but on 6.x with same hardware it can handle much less, I have
no idea why but thats what happens.  I friend of mine runs FreeBSD
routers in a large network and had to downgrade back to 4.x because of
this.

With the ports freeze I wonder in situations when a full freeze is
needed it is better to do so on a seperate testing branch so it allows
security commits etc. to carry on as normal and then remerge again
after testing is complete.  Or is this simply not possible to do?

Sysinstaller I do agree it does the job but thats it, its not good
enough for people not familiar with freebsd I feel and is a major
reason for adoptivity to freebsd.

Good news on the dynamic tcp stuff :)

Thanks

Chris