Date: Thu, 1 Feb 1996 18:27:33 -0600 (CST) From: "Karl Denninger, MCSNet" <karl@mcs.com> To: hackers@freebsd.org Subject: And the winner is! Message-ID: <m0ti9Li-000IDUC@venus.mcs.com>
next in thread | raw e-mail | index | archive | help
Hi folks! Question for 'ya: If you were setting up a "code server", and wanted to start trying to automate an update process for FreeBSD to be used in a production web environment (yes, I'm serious): a) What code base would you use? Pointers to supfiles please; I have the one for -STABLE, but I bet its out of date. I know the "our philosphy is that STABLE is..." stuff; I want to know from the people using FreeBSD now what is the *best* code base you have. Future changes via SUP are fine, assume I'm not stupid and know how to use things like compilers :-) b) How to handle replication? I know how to do this on BSDI, but on FreeBSD it has always eluded me. Presume that there is a spare machine that I can "burn" to have a code base loaded on (that can be replicated FROM), but that there may be differences in the hardware (ie: ethernet cards, disk capacities, etc) c) Has the "I need to load 'package y' without wiping the box", and the companion "I want to add a disk and not do a disktab by hand -- since I have a ZBR disk and don't KNOW the right values!" problem that has plagued FreeBSD been solved? It is TRIVIAL to get BSDI to set up a new disk (disksetup does it all). Last time I looked closely FreeBSD was a bitch. Still true? d) How about stability in general? PCI Ethernet card drivers? PCI disk drivers? NFS stability problems (we used to have those up the wazoo). Support for >64M without kludges? Any surprises I should expect (and benefits of current .vs. stable, etc)? Why these questions? I've had it -- again -- with BSDI. So we're back out plowing around in the other alternatives looking for the diamond in the rough. To be fair, we have a couple of FreeBSD machines running now -- including a VERY busy news server -- which work just fine, even under heavy punishment. The 2742 EISA disk drive is still rough around the edges; I hope the Adaptec PCI driver works..... :-) If I'm going to have an unsupported OS, damnit, then I'm going to KNOW its unsupported and not pay for support! I don't mind doing my own qualification for use, but when I can't get support in a reasonable timeframe on what is supposed to be a commercial product, I'm done. Thanks in advance! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity Modem: [+1 312 248-0900] | T1 from $600 monthly; speeds to DS-3 available Voice: [+1 312 803-MCS1] | 21 Chicagoland POPs, ISDN, 28.8, much more Fax: [+1 312 248-9865] | Email to "info@mcs.net" WWW: http://www.mcs.net/ ISDN - Get it here TODAY! | Home of Chicago's only FULL Clarinet feed!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0ti9Li-000IDUC>