From owner-freebsd-stable Wed May 26 11: 5:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 88F3B1553A for ; Wed, 26 May 1999 11:05:34 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 85941 invoked by uid 100); 26 May 1999 18:05:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 May 1999 18:05:33 -0000 Date: Wed, 26 May 1999 11:05:33 -0700 (PDT) From: Mike Meyer To: freebsd-stable@FreeBSD.ORG Subject: Re: [Q] How stable is FreeBSD 3.X ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 May 1999, Troy Settle wrote: > On Wed, 26 May 1999, Mike Meyer wrote: > If Sun does a "patch this, patch that, patch the next thing" sort of game, > I'm glad I've never had to admin one. > > Sounds as bad as linux: > > Patch this, but only after you've upgraded that. Before that, > however, you need to reinstall foo, and of course bar which foo > depends on. etc. etc. etc. Well, I've never used a commercial Linux system, but Sun's isn't quite that bad. Patches seldom depend on other patches (though, as was pointed out elsewhere, they do sometimes collide). Products may depend on patches - but you just have one level things to deal with. The real win is the ports system. No longer "Get package X. Now go get Y, Z and W. Install Y and Z, then get M & N and install those. Now install W. Finally install X", but "cd /usr/ports/stuff/X; make install" (and sometimes curse because it's broken). This has been quite accurately describe as a sysadmins wet dream. Now, if only it had a hook to apply local patches, so I could put the Python & PostGreSQL modules in the apache build... > With FreeBSD: > > cd /usr/src > cvsup supfile > make buildworld && make installworld && reboot ... find machine dead, reboot from fixit disk, resup, ... :-) > > I'd expect installing a service pack to be a lot more painfull than > > installing a patch, much as installing an application on Windows 9x is > > a lot more painfull than doing so on a Unix box (Does WNT require a > > system reboot on every application install like Windows 9x?). > Windows is braindamaged beyond repair. You don't *need* to reboot after > sneezing, but it is reccomended. Which goes along with reinstalling to cure anything. But what about WNT? > All in all, it's a pretty nice development structure compared to what I > know of other vendors. It's different. Which is causes people to get confused about what to expect. > > Do any of the commercial FreeBSD support organizations run a seperate > > branch and bundle patches up for their customers? > > Like what Red Hat does for Linux? No Thank You. Just because you don't like it, doesn't mean it's not for everybody. I can see that a commercial ISP might prefer a system where they fed someone else money, and got 1) security patches, and 2) fixes for bugs they encountered. It certainly makes pointy-haired managers happy if they can spend money on something like that. My first reaction on dealing with a Unix that came without source was to compare it to castration. I'm glad the world has gotten back to the state where I can run a Unix with source without handing over an ungodly amount of money, my firstborn child, or both (Jordan, did you sign that thing Sun wanted us to sign to look at their sources?) My thanks to the good folks of CSRG (and others I probably don't know) for making that happen, and the FreeBSD developers for continuing to improve it.