Re: Current in Production
Do you own a Harley? Do the Mosh Pit? You definitely like riding the edge of insanity... -current is always in a state of flux... I say you lucked out... FreeBSD is killer stuff, but, I personally wouldn't risk a job on the odds of getting a stable -current when I needed one... Chris Knight wrote: Howdy, I'd just like to thank the FreeBSD team for an outstanding job. I've got a FreeBSD-current system in production running an Intranet that has just exceeded one year's uptime. Admittedly, the snapshot I built was 30/10/2000, but it does go to show that current can indeed be used for production systems. The system only ever had one reboot and that was when the installation was migrated to a new box. For those that are interested, the Intranet uses Apache, PHP, Firebird and OpenLDAP for various Web-based management applications/tasks. Again, thanks to everyone responsible for providing a reliable and dependable distribution, even when it's considered unstable and for development purposes only. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - Religious fundamentalism is the biggest threat to international security that exists today. United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Current in Production
Howdy, I would have lucked out if it wasn't reliable :-) If you do all the right things, such as follow the commit logs and test, test, test, you can get a snapshot of current that will prove reliable for a certain number of tasks. It had three months of testing before going into production, so I didn't get any rude shocks, nor was I risking my job. Everyone was aware of the potential for instability and the fallback was to run the apps on a 4.x release or stable. I needed proof by example that FreeBSD development code was just as capable - if not more - as commercial OS releases. I have that well and truly now :-) I liked riding the edge of insanity years ago. I've fallen over the edge since then :-) Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: Jim Bryant [mailto:[EMAIL PROTECTED]] Sent: Thursday, 11 April 2002 14:35 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Current in Production Do you own a Harley? Do the Mosh Pit? You definitely like riding the edge of insanity... -current is always in a state of flux... I say you lucked out... FreeBSD is killer stuff, but, I personally wouldn't risk a job on the odds of getting a stable -current when I needed one... Chris Knight wrote: [snip] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current for production?
I'd like to reinforce this: I'm not a hacker, but have a -current box so I can write about it. (It's difficult to write a book targeting 5.1-release and time it for 5.1-R, when you don't have 5-current. This is one definite advantage Greg Lehey has over the rest of us authorial sorts.) With five years fairly hardcore FreeBSD experience, tracking -current is a *pain*. At any given point in time, 90% of the system works. The 10% that doesn't changes almost daily. If you want to invest your time in finding a particular date of -current that meets your needs, and you make a management decision that you will never, never, *never* upgrade without going through the same audit, go for it. Plus, I've made a management decision to never whine about what's broken, just live with it. (Okay, I do report broken buildworlds, but that's it.) My Pilot software locks the machine up; the web browser has been known to hang forever; the web server occasionally screams obscenities; other miscellanous ports just puke. Heck, I'm waiting for this laptop to phone the police and report me as a kiddie porn devotee, then anonymously transfer my bank balance to the Linux Foundation. It'll be for a technically sound reason, I know, but that still makes it a pain. I would run unionfs on a 3-stable production box before running -current in production right now. ==ml PS: You could also make a management decision to hire a kernel hacker to work on the part of -current that you need. :) On Tue, Mar 27, 2001 at 10:21:47AM -0800, John Baldwin wrote: On 27-Mar-01 Gabriel Ambuehl wrote: While I'm writing this: what is the general opinion about having CURRENT on production servers (I'd really love to deploy the ACLs ASAP)? I don't plan to use SMP and can wait for snapshots til the RELEASE comes... Don't. ACL's are still not production quality yet, and the SMP work breaks UP kernels just as bad as SMP kernels when it breaks. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current for production?
On 20 Dec 1999, Fritz Heinrichmeyer wrote: as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want on my private box anyway. I think you'd have better luck asking people what their experiences with the software have been, rather than asking for a recommendation. No one is likely to want to take the responsibility of recommending -current for a production site, but they'll be happy to share their own experiences and let you come to your own conclusion. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current for production?
I'm inclined to agree. I have had great luck in production boxes with FreeBSD-CURRENT, but it's not reccomended to use -CURRENT for production just because sometimes things break. :-) = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Mon, 20 Dec 1999, Ben Rosengart wrote: On 20 Dec 1999, Fritz Heinrichmeyer wrote: as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want on my private box anyway. I think you'd have better luck asking people what their experiences with the software have been, rather than asking for a recommendation. No one is likely to want to take the responsibility of recommending -current for a production site, but they'll be happy to share their own experiences and let you come to your own conclusion. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
