Date: Thu, 01 Feb 1996 19:32:20 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: "Karl Denninger, MCSNet" <karl@mcs.com> Cc: hackers@FreeBSD.org Subject: Re: And the winner is! Message-ID: <700.823231940@time.cdrom.com> In-Reply-To: Your message of "Thu, 01 Feb 1996 18:27:33 CST." <m0ti9Li-000IDUC@venus.mcs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 To be honest, I'd probably start supping the CVS tree to some local location on your site and just check a -stable tree out of it for your builds. This gives you the highest degree of flexibility should something pop up in -current which turns out to be the answer to some prayer and you need to do a little mucking around with CVS in order to merge it across into your -stable tree. > b) How to handle replication? I know how to do this on BSDI, > but on FreeBSD it has always eluded me. Presume that there You want to be able to stamp out multiple machines from one build, or..? I'm afraid that "replication" is a little ambiguous in this context. Due to a number of historical bogons in our build process, I still recommend that each and every machine have its own copy of /usr/src, the problems with shared obj links otherwise becoming a real pain. > c) Has the "I need to load 'package y' without wiping the box", You can load packages and distributions fairly painlessly post-install, if that's what you mean. > 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 That's still kind of rough, yes. > 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)? Stability in general is good. PCI ethernet drivers good. PCI disk drivers, getting better. NFS stability problems are bad. Most people trying to seriously beat up on NFS find that it beats back. A lack of NFS experts with spare time is a big problem for us right now or we'd fix it. > 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 One thing I might suggest is hiring in some local talent who finds the idea of hacking on free software cool, for god knows whatever reason, and can provide you with at least one source of immediate recourse in case of failure. It all depends on whether or not the numbers add up for you, of course. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?700.823231940>