From owner-freebsd-hackers  Wed Jul 19 11:34:29 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id LAA05629
          for hackers-outgoing; Wed, 19 Jul 1995 11:34:29 -0700
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA05623
          ; Wed, 19 Jul 1995 11:34:24 -0700
Received: from localhost.v-site.net (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.6.11/8.6.9) with SMTP id LAA03531; Wed, 19 Jul 1995 11:33:38 -0700
Message-Id: <199507191833.LAA03531@rah.star-gate.com>
X-Authentication-Warning: rah.star-gate.com: Host localhost.v-site.net didn't use HELO protocol
X-Mailer: exmh version 1.6.1 5/23/95
To: "Karl Denninger, MCSNet" <karl@mcs.com>
cc: terry@cs.weber.edu (Terry Lambert), hsu@cs.hut.fi,
        jmacd@freefall.cdrom.com, freebsd-hackers@freefall.cdrom.com
Subject: Re: What people are doing with FBSD 
In-reply-to: Your message of "Wed, 19 Jul 1995 13:09:05 CDT."
             <m0sYdYQ-000IDWC@venus.mcs.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Jul 1995 11:33:37 -0700
From: "Amancio Hasty Jr." <hasty@rah.star-gate.com>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>>> "Karl Denninger, MCSNet" said:
 > > > There are other more subtle reasons, but those are far enough.
 > > 
 > > I'd like to hear the subtle ones 8^).  I think the only one of merit
 > > that I've seen above is stability, and that's only tangential to
 > > installation.
 > > 
 > > > We currently use about 15 PC's running FreeBSD as routers and servers, b
     ut
 > > > the user workstations and personnel's home machines are Linux.  The main
 > > > reasons for using FreeBSD here is Linux networking code (sigh) and
 > > > non-existant source management, and probably some history.  FreeBSD gets
 > > > hurt badly by unstability, not much change to "sell" FreeBSD to anyone a
     s
 > > > long as the longest uptimes are weeks.
 > > 
 > > Clearly, the BSD folks are more than willing to try to resolve *ANY*
 > > stability issue you might have; the biggest problem is that they remain
 > > unreported, and you can't fix a bug you aren't told about.
 > > 
 > > 
 > > 					Regards,
 > > 					Terry Lambert
 > 
 > Ours don't remain unreported :-)
 > 
 > On the other hand, I have to second what Terry says.  I've received a number
 > of suggestions, things to try, and even guesses in the wind about the
 > problems I've reported.
 > 
 > Yes, I still have some problems with stability.  But we *are* getting closer
 > and making progress, and the list of exceptions at present with FreeBSD is
 > down to *TWO*.
 > 
 > Considering that BSDI has a longer list than that, some of which have
 > remained open for a long time, and Linux is the patch-of-the-hour club IMHO,
 > there is no way these compare.
 > 
 > I happen to personally HATE the installer that FreeBSD uses, as adding disks
 > to an existing system is a real bitch of a job the way they do things.  The
 > nice (and it IS nice) installer that you get when you boot disk #1 is not
 > available once you have it up, and that's really too bad -- if FreeBSD had a
 > nice, clean disk partitioning and labelling tool I'd be in hog heaven right
 > now.
 > 
 > --
 >
I have to sencod that for a little while ago my second disk drive corrupted
itself real bad. So I had to reformat it and I am still having problems
with the disks. Now it was just like the good old days of 386bsd to
install a disk label :(

Others have mentioned it  and I will stated also sysintall needs to be
able to run on a normal system to label disks, install packages, etc..

Amancio