Date: Wed, 29 Mar 2000 03:41:45 -0500 (EST) From: Mike Nowlin <mike@argos.org> To: Didier Derny <didier@omnix.net> Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG Subject: Re: Let 3.x die ASAP? Message-ID: <Pine.LNX.4.05.10003290328060.28083-100000@jason.argos.org> In-Reply-To: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm about to buy a smp machine but I see so many horror stories on > the mailling lists that I'm not sure at all that I should use a smp > machine (or install linux instead of FreeBSD)... Trust me - Linux isn't without it's share of problems with SMP... I have a Dual-CPU P2-333 sitting here running Linux 2.2.12 (Intel DK440LX board) which never fails to create one new brainache after another... Today, it's Extace (sound "viewing" program). Works great when SMP isn't running, seg faults when both processors are kicking along. A big chunk of what I like about FreeBSD compared to Linux is that there's more accountability for specific parts of the system. Linus takes care of the Linux kernel, but who knows who does the rest -- depending on what release, by what distributor (Slackware, Redhat, etc.), finding library X to update library Y to fix program Z can be a real pain... With FreeBSD, you can easily find out who is responsible for various chunks of the system. Even if he/she doesn't have a solution for your particular problem, he'll generally have a good idea where to send you, or be willing to fix the problem in the tree. (Don't get me wrong - I love Linux, but FreeBSD is better for a lot of things... My "play toy" is a Linux SMP machine, but for reliability at both of the IT shops I'm in charge of, I'll pick FreeBSD every time...) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.05.10003290328060.28083-100000>