Re: Viability of 5.X line for production use
On Mon, Jan 05, 2004 at 09:43:26AM -0800, John Fox wrote: Hello, We're planning some new mail servers, and until now I've been assuming that they would run under FreeBSD 4.X. But it occurred to me this morning that the 4.X line is going to go away relatively soon, and that perhaps I'd be better off going with 5.X for these new boxen, as it would probably simplify the upgrade (keeping up with releases and bug fixes) process. So I'm wondering -- do the experts here judge 5.X as ready for use in a production environment, or would that be asking for trouble? Wait for 5.2-R to come out, then wait a month or more for any undetected serious bugs to get fixed in the release branch. Then try it on one machine and see how it fares. Kris pgp0.pgp Description: PGP signature
RE: Viability of 5.X line for production use
How long can you wait for the 5.x stable release? The 5.x stable release is scheduled for May or June 2004. Then 1 or 2 months burn in by public users to verify it is really stable and you are pushing September. 4.9 is production now and has passed the public burn in period with flying colors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kris Kennaway Sent: Tuesday, January 06, 2004 11:18 AM To: John Fox Cc: [EMAIL PROTECTED] Subject: Re: Viability of 5.X line for production use On Mon, Jan 05, 2004 at 09:43:26AM -0800, John Fox wrote: Hello, We're planning some new mail servers, and until now I've been assuming that they would run under FreeBSD 4.X. But it occurred to me this morning that the 4.X line is going to go away relatively soon, and that perhaps I'd be better off going with 5.X for these new boxen, as it would probably simplify the upgrade (keeping up with releases and bug fixes) process. So I'm wondering -- do the experts here judge 5.X as ready for use in a production environment, or would that be asking for trouble? Wait for 5.2-R to come out, then wait a month or more for any undetected serious bugs to get fixed in the release branch. Then try it on one machine and see how it fares. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Viability of 5.X line for production use
Hello, We're planning some new mail servers, and until now I've been assuming that they would run under FreeBSD 4.X. But it occurred to me this morning that the 4.X line is going to go away relatively soon, and that perhaps I'd be better off going with 5.X for these new boxen, as it would probably simplify the upgrade (keeping up with releases and bug fixes) process. So I'm wondering -- do the experts here judge 5.X as ready for use in a production environment, or would that be asking for trouble? Any thoughts appreciated, John -- +---+ | John Fox [EMAIL PROTECTED] | System Administrator | InfoStructure | +---+ |Gideon: I thought you said don't hold a grudge.| | Galen: I don't. I have no surviving enemies...at all. | | -- Crusdade, _Racing the Night_ | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Viability of 5.X line for production use
In the last episode (Jan 05), John Fox said: We're planning some new mail servers, and until now I've been assuming that they would run under FreeBSD 4.X. But it occurred to me this morning that the 4.X line is going to go away relatively soon, and that perhaps I'd be better off going with 5.X for these new boxen, as it would probably simplify the upgrade (keeping up with releases and bug fixes) process. So I'm wondering -- do the experts here judge 5.X as ready for use in a production environment, or would that be asking for trouble? I think as long as you're not using the features that are causing other people problems (SATA, some acpi stuff, etc), 5.x is just fine. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
