From owner-freebsd-questions Sun Jul 27 16:57:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA28815 for questions-outgoing; Sun, 27 Jul 1997 16:57:50 -0700 (PDT) Received: from mackay01.cqit.qld.edu.au (root@cqit.qld.edu.au [203.22.80.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28809 for ; Sun, 27 Jul 1997 16:57:45 -0700 (PDT) Received: from carbon.chalmers.com.au (carbon.cqit.qld.edu.au [203.22.80.5]) by mackay01.cqit.qld.edu.au (8.7.3/8.6.9) with ESMTP id JAA15406 for ; Mon, 28 Jul 1997 09:54:00 +1000 (EST) Message-ID: <33DBDFBC.CDE8BD1E@chalmers.com.au> Date: Mon, 28 Jul 1997 09:54:37 +1000 From: Robert Chalmers Reply-To: robert@chalmers.com.au Organization: chalmers.com.au X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-questions Subject: There seem to be lots of problems with the new releases? X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have tried running up 3-SNAP, and get the now well reported timeout on the ethernet interface. This is not the only problem. The one about no root group, the one about the sys.conf file being missing, and others too numerous to mention. The thing I notice is that the same problems, and others are cropping up on releases including 2.2.1, release and stable it seems. Now this seems a contradiction in terms, caling something stable, or release(ready) when it is obviously not. It concerns me that FreeBSD is perhaps being rushed to release. Things linke the sysconf file, and root groups are so simple that they should have been caught well before release! I watched another *nix O/S die because the releases were rushed onto the market without full and complete checking. At least the installation process should allow users to get a basic system up and running, without having to do a course in Unix. I mean, do I need to do a course in fluid dynamics to put fuel in my car? An aweful lot of people come to FreeBSD as a first time exercise, and to get bitten with a system that is apparently getting more holes in it as it goes along will do nothing but deter people from using what up to now has been an excellent system. I know that FreeBSD is largely a group exercise, but I would hope that there is some project control being applied. Up to 2.2-SNAP, things seemed to be holding together, but the fulurry of simple problems since, and more serious problems, like ethernet cards timing out, would seem to indicate that control is being dropped somewhere. This message is probably out of line, and I'm not FreeBSD bashing. I use it, and have done so for years now. My operational system is in fact 2.2-SNAP, and it runs without fault. In fact both servers do, and have done for ages. I must confess though that I am loath to update to anything later than the 2.2-snap. I'm not inviting a flame war, just wondering where FreeBSD is headed? cheers, Robert -- http://www.chalmers.com.au Books-New & Secondhand Support Whirled Peas. Agents for CIBTC. Associate of Amazon.com, and Partner Program with iBS. Books about China, books from China. Sheng huo jiu shi dou zheng Business Links in Dalian, and Beijing. Building the China Trade